Progress report on a review of IFG - ISO... · Progress report on a review of IFG DIBK AEC3...
Transcript of Progress report on a review of IFG - ISO... · Progress report on a review of IFG DIBK AEC3...
Progress report on a review of IFG
DIBK AEC3 Mariboes gate 13 High Wycombe
0183 OSLO HP15 6HP
IFG – IFC for GIS 2004-2006
Overview
• IFG fed into IFC4 with a 10 year interval• buildingSMART Model Setup MVD
currently meeting• Can we encourage implementation ?
Terms of reference1. Refresh the knowledge from the IFG project. Recovery and
identification of IFG 2005 primary material. Review and prepare the background studies for publication.
2. Check the proposed changes are in IFC4 Review of entities, property sets and classification. Review the use of library references to link to feature catalogues.
3. Review of IFG Use cases and exchange requirements. Ensure they support mapping as a context for design engineering.
4. Guidelines for implementers. How to use the georeferencingcapability. How to use the new entities. Use of library references for feature catalogues. Expected and recommended attributes.
5. Evaluate the method used for IFG integration• . Current project integration methods• Role of mvd and mvdXML.• Role of bsDD and local dictionaries, • EU INSPIRE directives and GEMINI.• Impact of point clouds and LIDAR type data. • Communication of accuracy and suitability.
IFGGe
opsp
atia
l
Geog
raph
ic F
eatu
res
Obj
ectif
icat
ion
Back
grou
nd k
now
ledg
e
Exte
nsio
n pr
ojec
ts
Dict
iona
ries
Suita
bilit
y
Accu
racy
Relia
bilit
y
Extension projects
Aspect Before IFG IFG Aquarium Currently
Scope Extension topic Whole domain Single use case Whole domain
Scenarios Whole domainGIS-BIM interface Single scenario Aspects of domain
Overview Domain Selected transactions Single transaction Selected transactions
Participants Two chapters One sponsor Several users Multiple sponsors
SupportTwo application developers Optional Several developers Optional
Diagram IDEF0 (now SBP) Four parties None BPMN
Transaction Output->Input Use cases Singular Exchange requirement
Documentation Reports Progress report Report IfcDoc
Implementation New sub-schemas Use case Functional part ConceptActions arising Change requests Change requests n/a Change requests
Deliverables n/a Usage notes Usage notes Documentation
Objectification
Geospatial / Geo location
Project
Product Representation Shape Representation
Projected CRSMap Conversion
Rel Aggregates
Site
Geometric Representation Context
Block
Eastings: 0Northing: 0
OrthogonalHeight: 0XAxisAbscissa: 0XAxisOrdinate: 0
Scale: 1
Name: EPSG:25832Description: ETRS89 /
UTM zone 32NGeodeticDatum:
ETRS89VerticalDatum:
Hamburg HarbourMapProjection: zzz
MapZone: yyyMapUnit: kilometre
TrueNorth: (WGS84)
RefLat: (WGS84)RefLong (WGS84) RefElev: (WGS84)
n
n
IFC4 Geolocation
n n
Key
• Dark blue ifc2x3 and ifc4• Light blue ifc4 additions• Upright: mandatory attributes• Italic: optional attributes• Full arrow: mandatory relationship• Dotted arrow: optional relationship
SummaryIFCPROJECT
Has a list of many IFCGEOMETRICCONTEXTSHas an IFCAGGREGATES with many IFCSITEs
IFCGEOMETRICREPRESENTATIONHas an optional WGS84 north orientationIs pointed to by an IFCMAPCONVERSIONPoints to an IFCPROJECTEDCRSIs pointed to by IFCSHAPEREPRESENTATATIONs
IFCSHAPEREPRESENTATION Contains an IFCBLOCK Is contained in an IFCPRODUCTRERESENTATION which is pointed to by
each IFCSITEIFCSITE
Has optional WGS84 latitude, longitude, elevationIFCMAPCONVERSION
Has six measurementsIFCPROJECTEDCRS
Has six string attributes
IFC4
• IfcExternalSpatialElementTypeEnum• IfcGeographicElementTypeEnum• IfcExternalSpatialElement• IfcInternalOrExternalEnum• EXTERNAL_EARTH• EXTERNAL_WATER• EXTERNAL_FIRE• IfcSpaceTypeEnum• SPACE• PARKING• GFA• INTERNAL• EXTERNAL• IfcGeographicElement• IfcGeographicElementType• IfcCoordinateReferenceSystem• IfcMapConversion• IfcProductRepresentation• IfcProjectedCRS
IFC4Property Sets
• Pset_AnnotationContourLine• Pset_AnnotationLineOfSight• Pset_AnnotationSurveyArea• Pset_LandRegistration• Pset_PropertyAgreement• Pset_SpaceParking
Topography and TINs
Use cases / Scenario
• Backgrounding– Also linked open data for weather and services and geo-naming
• Analysis– Control – and constraints– Planning volumes and areas, setbacks
• Proposal– Set-up (new)– set-out
• Update – Update of map and community data
Topics
• General– Also linked open data for weather and services and geo-naming
• Area– Control – and constraints– Planning volumes and areas, setbacks
• Distribution– Set-up (new)– set-out
• Construction– Update of map and community data
•
Dictionary
IfcAnnotation (IFC)o contour (en-GB)o Hoydekurve (no-NO)
IfcGeographicElement (IFC)o curve (en-GB)o kurve (no-NO)
IfcGeographicElement (IFC)o road (en-GB)o Vei (no-NO)o vei (no-NO)
IfcBuilding (IFC)o building (en-GB)o Bygning (no-NO)o bygg (no-NO)
IfcSite (IFC)o District (en-GB)o Kommune (no-NO)
IfcGeographicElement (IFC)o tree (en-GB)o tre (no-NO)o Tre (no-NO)
RevisionDate (IFC)o Revision Date (en-GB)o dato (no-NO)
Kommune 219
Report 3: Whittlesey Washes
Chainage origin• CH 0• 1.001
• TF 39775 02968• 539775.42mE• 302967.59mN
By gradientSloping: blue Flat: turquoise
landXML mapped _fromLandXML to IFCrendered by Tekla BimSight
landXML mapped _fromLandXML to IFCrendered by Tekla BimSight
By facing direction South: yellow Flat: turquoise
• BH06• 3rd strata• Embankment fill• 0.100m
Borehole Spreadsheet enhanced to BS5930:1999Mapped _fromSpreadsheet to IFCRendered in UNN Xbim Xplorer
39 !
Air frost values summed to an answer of: 39 days
Figure 4 Executed Query Results on Dataset
KIT – Universität des Landes Baden-Württemberg undnationales Forschungszentrum in der Helmholtz-Gemeinschaft
Institut für Angewandte Informatik
www.kit.edu
IFC4 – Implementation Guidancefor Georeferencing
Institut für Angewandte Informatik25
IFC4 Entities required
use IFC4-Add1 due to some minor corrections also in scope of geo-referencinghttp://www.buildingsmart-tech.org/ifc/review/IFC4Add1/beta/html/
(ABS) IfcCoordinateReferenceSystem URL└ IfcProjectedCRS URL
(ABS) IfcCoordinateOperation URL└ IfcMapConversion URL
(ABS) IfcRepresentationContext URL└ IfcGeometricRepresentationContext URL
IfcProject URL
Andreas Geiger, Karl-Heinz Häfele19.08.2014
Institut für Angewandte Informatik26
IfcProjectedCRSENTITY IfcCoordinateReferenceSystem
ABSTRACT SUPERTYPE OF(IfcProjectedCRS);Name : IfcLabel;Description : OPTIONAL IfcText;GeodeticDatum : OPTIONAL IfcIdentifier;VerticalDatum : OPTIONAL IfcIdentifier;
END_ENTITY;
ENTITY IfcProjectedCRSSUBTYPE OF IfcCoordinateReferenceSystem;
MapProjection : OPTIONAL IfcIdentifier;MapZone : OPTIONAL IfcIdentifier;MapUnit : OPTIONAL IfcNamedUnit;
WHEREIsLengthUnit : NOT(EXISTS(MapUnit)) OR (MapUnit.UnitType = IfcUnitEnum.LENGTHUNIT);
END_ENTITY;
Examples:#1= IFCPROJECTEDCRS ('EPSG:25832','ETRS89 / UTM zone 32N','ETRS89',$,$,$,$);#2= IFCPROJECTEDCRS ('EPSG:31467','DHDN / Gauss-Kruger zone 3 (Bessel)',$,$,$,$,$);
Andreas Geiger, Karl-Heinz Häfele19.08.2014
Institut für Angewandte Informatik27
IfcCoordinateReferenceSystem
Name: Name by which the coordinate reference system is identified.NOTE The name shall be taken from the list recognized bythe European Petroleum Survey Group EPSG. It should then bequalified by the EPSG name space, for example as 'EPSG:5555'.
Description: Informal description of this coordinate reference system.GeodeticDatum: Name by which this datum is identified. The geodetic datum is
associated with the coordinate reference system and indicates theshape and size of the rotation ellipsoid and this ellipsoid's connection and orientation to the actual globe/earth. It needs to be provided, if theName identifier does not unambiguously define the geodetic datum as well.Examples for geodetic datum include:- ED50- EUREF89- WSG84
VerticalDatum: Name by which the vertical datum is identified. The vertical datum is associated with the height axis of the coordinate reference system and indicates the reference plane and fundamental point defining the origin of a height system. It needs to be provided, if the Name identifier does notunambiguously define the vertical datum as well and if the coordinate referencesystem is a 3D reference system.Examples for vertical datum include:- DHHN92 the German 'Haupthöhennetz'- EVRS2007 the European Vertical Reference System
Andreas Geiger, Karl-Heinz Häfele19.08.2014
Institut für Angewandte Informatik28
IfcMapConversionENTITY IfcCoordinateOperation
ABSTRACT SUPERTYPE OF(IfcMapConversion);SourceCRS : IfcCoordinateReferenceSystemSelect;TargetCRS : IfcCoordinateReferenceSystem;
END_ENTITY;
ENTITY IfcMapConversionSUBTYPE OF (IfcCoordinateOperation);
Eastings : IfcLengthMeasure;Northings : IfcLengthMeasure;OrthogonalHeight : IfcLengthMeasure;XAxisAbscissa : OPTIONAL IfcReal;XAxisOrdinate : OPTIONAL IfcReal;Scale : OPTIONAL IfcReal;
END_ENTITY;
Examples:10= IFCMAPCONVERSION(ref1,ref2,458658.,5438232.,113.7,0.270600445976,0.962691746426,$);11= IFCMAPCONVERSION(ref1,ref2, 458718.,5439970.,113.7,0.270600445976,0.962691746426,$);
ref1 – reference to the IfcGeometricRepresentationContext (not using cascading mapping of another IfcProjectedCRS)ref2 – reference to the IfcProjectedCRS (only subtype of ABS IfcCoordinateReferenceSystem)
Andreas Geiger, Karl-Heinz Häfele19.08.2014
Institut für Angewandte Informatik29
IfcMapConversion
Easting: Specifies the location along the easting of the coordinate system of the target map coordinate reference system.NOTE for right-handed Cartesian coordinate systems this would establish the location along the x axis.
Northing: Specifies the location along the northing of the coordinate system of the target map coordinate reference system.NOTE for right-handed Cartesian coordinate systems this would establish the location along the y axis
OrthogonalHeight: Orthogonal height relative to the vertical datum specified.NOTE for right-handed Cartesian coordinate systems this would establish the location along the z axis
XAxisAbscissa: Specifies the value along the easing axis of the end point of a vector indicating theposition of the local x axis of the engineering coordinate reference system.NOTE 1 for right-handed Cartesian coordinate systems this would establish the location along the x axis (also referred to as the Easting in map coordinate systems) NOTE 2 together with the XAxisOrdinate it provides the direction of the local x axis within the horizontal plane of the map coordinate system
XAxisOrdinate: Specifies the value along the northing axis of the end point of a vector indicating the position of the local x axis of the engineering coordinate reference system. NOTE 1 for right-handed Cartesian coordinate systems this would establish the location along the y axis (also referred to as the Nothing in map coordinate systems) NOTE 2 together with the XAxisAbscissa it provides the direction of the local x axis within the horizontal plane of the map coordinate system.
Scale: Scale to be used, when the units of the CRS are not identical to the units of the engineering coordinate system. If omitted, the value of 1.0 is assumed.
Andreas Geiger, Karl-Heinz Häfele19.08.2014
Institut für Angewandte Informatik30
Examples for CRS Identifiers
OGC Example:urn:ogc:def:crs,crs:EPSG::25832,crs:EPSG::5783urn:ogc:def:crs,crs:EPSG::5555
ADV Example (German National Working Group):urn:adv:crs:ETRS89_UTM32*DE_DHHN92_NH
IFC Example:EPSG::25832EPSG::25832,EPSG::5783EPSG::5555
NOTE The IFC syntax above is proposed if not already a CRS identifier is given
Andreas Geiger, Karl-Heinz Häfele19.08.2014
Institut für Angewandte Informatik31
Orientation Example
Andreas Geiger, Karl-Heinz Häfele, Nick Nisbet19.08.2014
IfcGeometricRepresentationContextIfcMapConversionXAxisAbscisa [0.270600445976] XAxisOrdinate [0.962691746426]
TrueNorth [0.962691746426, 0.270600445976]
IfcMapConversionuses the angle between the global east direction and the local x-axis
IfcGeometricRepresentationContextuses the angle between the local y-axis and the global north direction
Institut für Angewandte Informatik32
IFC Snippet
#1= IFCPROJECT('0xScRe4drECQ4DMSqUjd6d',#110,‘geo-referencing',$,$,$,$,(#43),#2);#2= IFCUNITASSIGNMENT((#3));#3= IFCSIUNIT(*,.LENGTHUNIT.,$,.METRE.);
#20= IFCPROJECTEDCRS('EPSG:25832','UTM in band 32','ETRS89',$,'UTM','UTM32',#3);#21= IFCMAPCONVERSION(#43,#20,458658.78,5438232.79,113.7,0.270600445976,0.962691746426,$);
#34= IFCDIRECTION((1.,0.,0.));#36= IFCDIRECTION((0.,0.,1.));#38= IFCCARTESIANPOINT((0.,0.,0.));#40= IFCAXIS2PLACEMENT3D(#38,#36,#34);#41= IFCDIRECTION((0.962691746426,0.270600445976));#43= IFCGEOMETRICREPRESENTATIONCONTEXT($,'Model',3,1.00000000000E-5,#40,#41);
Andreas Geiger, Karl-Heinz Häfele19.08.2014