Get documents about "Exchange Requirements
Document Sample
Basic HandOver to FM official view definition
Exchange Requirements (ER) for Georeferencing and Creation of Site Local Geometric Representation Mapping to IFC Definitions
MySupport
Object Type comments
Export
Import
Attribute Groups MVD MVD (K) Expand to see IFC representation
Property Definitions and notes Examples and further explanations Comments IFC Model Representation Comments generic binding General (P) Expand to see comments by person
Exchange Purpose: The purpose of this exchange is to provide correct georeferencing of a site in a project. The data exchanged will map the site's local origo (Multiple IfcSites allowed There is no limitations by a specific MDV. The ER's mandatory and optional data must be read and
in on project/IFC file? => IMpl agreements = >TH/TL) correctly to the earths surface and correctly give the deviation of the site's local Y axis from True North. (See IFC 2x4 specification interpreted correctly by the receiving applications. Other data can (should?/must?) be ignored by the
for IfcSite.) The file may optionally contain map or terrain representation of the site. This representation must be in the site's local coordinate system, not in a map coordinate system. receiving application but must not cause the application to fail. The minimum IFC version is 2x3. Where
(See IFC 2x4 specification for IfcSite.). 2x3 has shortcomings to 2x4, the workaround for 2x3 is documented.
Process outline: Advanced map and terrain handling is outside the scope of the current IFC Model. In projects these data are proveded on other formats defined by the GIS
community. Deciding the site's local origo must be done in a GIS system with IFC export capabilities or in a BIM system with GIS capabilites. This application must have an user
interface (UI) that allows the user to pick the site's local origo on the map and give the direction of the site's local Y axis relative to True North. Elevation for the site origo must be
obtained. How the UI obtains these data is entirely up to the designers of the application as long as the data obtained are correct. When this application wants to export the
georeferencing data to a BIM application these Exchange Requirements must be met. Any geometric representation of the site must be transformed to local site coordinates by the
application during the IFC export. See process map: ________________
NOTE: Deciding the origo of the site does not lock the posisition of the building(s). The local origo and orientation of the building can be set later relative to the site coordinate system.
Placing the building relative to the site coordinate system does not require a GIS system once the site has been properly georeferenced. NOTE2: Applications certified for IFC 2x3
coordination view should by definition be able to readan IFC which follows these ERs? How about the lack of a building?
NOTE: Any BIM application that imports an IFC with georeferencing must store all site related information in this ER. When the site is re-exported the original georeferencing data
must be kept without any loss of precision etc.
NOTE: If a BIM application has created a project and a dummy site, then it must be able to update the site information from the imported IFC file with georeferencing data and site
geometry.
Meta data
Exchange file HEADER section
Exchange purpose Designation of the exchange file to be No view limitation. Mark the file to M file_description(('ViewDefinition [CoordinationView, GeoreferencingER/MDV]'), to be done automatically by the
"Georeferencing" comply to ER for Georeferencing. -- '2;1' => Spør TH); application
system to assign the standard view
definition name
Author Name of the creator of the user setting - application need to provide M file_name with field author The UI of sending application shall
Georeferencing data UI enable the user to fill in the data
Company Company name of the Author user setting - application need to provide M file_name with field organization The UI of sending application shall
UI enable the user to fill in the data
Originating application Name of the software application that system setting by software vendor, shall M file_name with field originating_system The version and/or build number should
created the data set be specific, i.e. including version be as specific as possible.
information
Date of creation Time stamp of the creation time 2008-04-12T15:27:46 M file_name with field time_stamp to be done automatically by the
application
Project there has to be exactly one project object IfcProject GSC-239
in the exchange file
Project Attributes VBL-296
Software unique id Object identifier (formated as GUID or 70ce2f2b-a5f8-4ab7-bc7f- M IfcProject.GlobalId 70ce2f2b-a5f8-4ab7-bc7f-6a838a353f25 VBL-170
UUID) to uniquely identify the software 6a838a353f25, has to be maintained by is exchanged using compression
object the application (e.g. for re-export) 1mpYyhfVXAjxn$QeEADJyb
Number (or ID) User assigned (short) name or number delivery contracts may demand a certain NOTE: Is this the Project unique ID for exchanges or the project GUID? Or use M IfcProject.Name GSC-241
naming convention "seed" empty project distributed to all partisipants?
Name User assigned name (full name) for informational purposes only M IfcProject.LongName GSC-242
Description OPTIONAL User assigned optional not required for export [General]: Optional, not checked O Optional, not checked
description
Phase OPTIONAL Design stage conceptual design, detailed design, …, O IfcProject.Phase
for informational purposes only
Project units VBL-359
Length unit Default length unit for all length [m], [mm], [inch], [feet] Does it matter? What is prefererred in GIS? M IfcProject.UnitsInContext (IfcUnitAssignment) with IfcSIUnit.Name = METRE GSC-246
measures in the data set
Area unit Default area unit for all length measures [m²], [square feet] M IfcProject.UnitsInContext (IfcUnitAssignment) with IfcSIUnit.Name = GSC-245
in the data set SQUARE_METRE
Volume unit Default volume unit for all length [m³], [cubic feet] M IfcProject.UnitsInContext (IfcUnitAssignment) with IfcSIUnit.Name = CUBIC_METRE GSC-247
measures in the data set
Project decomposition GSC-240
Site contained in Project Link to the top-level node of the spatial Must be present. M IfcRelAggregates GSC-041
structure, being a site
Building contained in Project Link to the top-level node of the spatial Not allowed. - IfcRelAggregates NOTE in the ArchitecturalHandOver it is GSC-083 has to be given, if there is no site
structure, being a building restricted to one site object in the IFC file
only
Site There must be exactly one site in the IfcSite GSC-031
project
Site Attributes (GSC-033)
Software unique id Object identifier (formated as GUID or 70ce2f2b-a5f8-4ab7-bc7f- M VBL-170
UUID) to uniquely identify the software 6a838a353f25, has to be maintained by
object the application (e.g. for re-export)
Number (or ID) User assigned unique number or key of NOTE: Is this the Site unique ID for exchanges or the Site GUID? M IfcSite.Name VBL-025 GSC-034 different to the software key
the site (short name). (GUID)
Name User assigned name (long name) M IfcSite.LongName BSA-507 BSA-508
Description User assigned optional description not required for export O ifcSite.Description GSA-008 GSC-035
Site Georeferencing Attributes (GSC-033)
Longitude Geo location geographic longitude in geodetic system Resolution is millionth-second. Redundant in 2x4, but must still be given. M IfcSite.Longitude See 2x4 IfcSite documentation VBL-312
WGS84, e.g. Chicago Harbor Light -
87.35.40 ("-" = W)
Latitude Geo location geographic latitude in geodetic system Resolution is millionth-second. Redundant in 2x4, but must still be given. M IfcSite.Latitude See 2x4 IfcSite documentation VBL-313
WGS84, e.g. Chicago Harbor Light
41.53.30 ("+" = N)
Elevation Site height datum elevation above the height datum IFC 2x3: Given according to the height datum used at this location (implicit). M IfcSite.RefElevation See 2x4 IfcSite and VBL-314
IFC 2x4: Defined in IfcCoordinateReferenceSystem.VerticalDatum. Redundant in IfcCoordinateReferenceSystem
2x4, but must still be given. documentation. IFC 2x3: Given
according to the height datum used at
this location (implicit).
True North True North Orientation of site coordinate system 2x3: It is given by a 2 dimensional direction within the xy-plane of the project M IfcProject.RepresentationContexts.IfcGeometricRepresentationContext.TrueNorth See 2x4 IfcSite and
relative to True North coordinate system. If not resent, it defaults to [0.,1.] - i.e. the positive Y axis of the IfcGeometricRepresentationContext
project coordinate system equals the geographic northing direction. Redundant in documentation
2x4 (XAcisAbscissa/Ordinate)), but must still be given.
Geodetic Coordinate Reference System Identification of datum used Information not present in 2x3. Information must be exchanged outside the IFC M
2x3 Model. Manually? Non-standard PSET in 2x3?
Name Name of coordinate reference system EUREF89-UTM-32, 32632 (EPSG), ... O IfcMapConversion.IfcCoordinateReferenceSystem.Name Not present in 2x3
Description Description O IfcCoordinateReferenceSystem.Description Not present in 2x3
Geodetic Datum Name by which this datum is identified. EUREF89, ED50, WSG84, ... M IfcCoordinateReferenceSystem.Description Not present in 2x3
Vertical Datum Name by which the vertical datum is NGVD 29, NAVD 88 (North America), M IfcCoordinateReferenceSystem.Name Not present in 2x3
identified NN1954 (Norway), ...
Map Projection Identification of Map Projection Used Information needed for transformation from local site coordinates to map M
coordinates. (NOTE: Not map to geodetic coordinate reference system).
Information not present in 2x3. Information must be exchanged outside the IFC
2x3 Model. Manually? Maintained in GIS system? Non-standard PSET in 2x3?
MapProjection Name of map projection UTM, NTM, .... O IfcProjectedCRS.MapProjection Not present in 2x3
MapZone Name of sone within map projection UTM Sone 32 woulde be: "32" O IfcProjectedCRS.MapZone Not present in 2x3
MapUnit Length unit for map coordinates [m], [mm], [inch], [feet] M IfcProjectedCRS.MapUnit Not present in 2x3
buildingSMART International: FM Aquarium Project page 1 Editor: Thomas Liebich
Basic HandOver to FM official view definition
Exchange Requirements (ER) for Georeferencing and Creation of Site Local Geometric Representation Mapping to IFC Definitions
MySupport
Object Type comments
Export
Import
Attribute Groups MVD MVD (K) Expand to see IFC representation
Property Definitions and notes Examples and further explanations Comments IFC Model Representation Comments generic binding General (P) Expand to see comments by person
Exchange Purpose: The purpose of this exchange is to provide correct georeferencing of a site in a project. The data exchanged will map the site's local origo (Multiple IfcSites allowed There is no limitations by a specific MDV. The ER's mandatory and optional data must be read and
in on project/IFC file? => IMpl agreements = >TH/TL) correctly to the earths surface and correctly give the deviation of the site's local Y axis from True North. (See IFC 2x4 specification interpreted correctly by the receiving applications. Other data can (should?/must?) be ignored by the
for IfcSite.) The file may optionally contain map or terrain representation of the site. This representation must be in the site's local coordinate system, not in a map coordinate system. receiving application but must not cause the application to fail. The minimum IFC version is 2x3. Where
(See IFC 2x4 specification for IfcSite.). 2x3 has shortcomings to 2x4, the workaround for 2x3 is documented.
Process outline: Advanced map and terrain handling is outside the scope of the current IFC Model. In projects these data are proveded on other formats defined by the GIS
community. Deciding the site's local origo must be done in a GIS system with IFC export capabilities or in a BIM system with GIS capabilites. This application must have an user
interface (UI) that allows the user to pick the site's local origo on the map and give the direction of the site's local Y axis relative to True North. Elevation for the site origo must be
obtained. How the UI obtains these data is entirely up to the designers of the application as long as the data obtained are correct. When this application wants to export the
georeferencing data to a BIM application these Exchange Requirements must be met. Any geometric representation of the site must be transformed to local site coordinates by the
application during the IFC export. See process map: ________________
NOTE: Deciding the origo of the site does not lock the posisition of the building(s). The local origo and orientation of the building can be set later relative to the site coordinate system.
Placing the building relative to the site coordinate system does not require a GIS system once the site has been properly georeferenced. NOTE2: Applications certified for IFC 2x3
coordination view should by definition be able to readan IFC which follows these ERs? How about the lack of a building?
NOTE: Any BIM application that imports an IFC with georeferencing must store all site related information in this ER. When the site is re-exported the original georeferencing data
must be kept without any loss of precision etc.
NOTE: If a BIM application has created a project and a dummy site, then it must be able to update the site information from the imported IFC file with georeferencing data and site
geometry.
Site to Map Conversion Site to map conversion parameters Information needed for transformation from local site coordinates to map M
coordinates. (NOTE: Not map to geodetic coordinate reference system).
Information not present in 2x3. Information must be exchanged outside the IFC
2x3 Model. Manually? Maintained in GIS system? Non-standard PSET in 2x3?
Eastings O IfcMapConversion.Eastings Not present in 2x3
Northings O IfcMapConversion.Northings Not present in 2x3
OrthogonalHeight Orthogonal height relativ to the vertical M IfcMapConversion.OrthogonalHeight Not present in 2x3
datum
XAxisAbscissa M IfcMapConversion.XAxisAbscissa Not present in 2x3
XAxisOrdinate M IfcMapConversion.XAxisOrdinate Not present in 2x3
Scale Scale to be used when site length unit Not present in 2x3, assumed 1.0. M IfcMapConversion.Scale Not present in 2x3
are different from map length unit
Coordinate Operation Relationship between local site Information needed for transformation from local site coordinates to map M
coordinate system and map coordinate coordinates. (NOTE: Not map to geodetic coordinate reference system).
system (Conversions and Information not present in 2x3. Information must be exchanged outside the IFC
Transformations) 2x3 Model. Manually? Maintained in GIS-system? Non-standard PSET in 2x3?
SourceCRS Coordinate system of site M IfcCoordinateOperation.SourceCRS='IfcGeometricRepresentationContext' Not present in 2x3
TargetCRS Coordinate system of map projection M IfcCoordinateOperation.TargetCRS is a IfcProjectedCRS Not present in 2x3
Site Geometry Representation OPTIONAL See 2x4 IfcSite documentation GSC-032
Foot Print Representation Geometric Representation Lines and curves. Purpose is what? See also Geographic Element below. O IfcSite.IfcProductDefinitionShape.IfcShapeRepresentation.RepresentationIdentifier See 2x4 IfcSite documentation
Footprint of what: Site, building outline? = 'FootPrint'
IfcSite.IfcProductDefinitionShape.IfcShapeRepresentation.RepresentationT
ype = 'GeometricCurveSet', or 'Annotation2D'
Survey Point Representation Geometric Representation Survey points and breaklines. Can be O IfcSite.IfcProductDefinitionShape.IfcShapeRepresentation.RepresentationIdentifier See 2x4 IfcSite documentation. Is
used for what? Triangularisation???? ='SurveyPoints' unambigously defined how
IfcSite.IfcProductDefinitionShape.IfcShapeRepresentation.RepresentationT triangularisation can be done from
ype = 'GeometricSet' survey points?
Body Representation Geometric Representation Surface or volume representation O IfcSite.IfcProductDefinitionShape.IfcShapeRepresentation.RepresentationIdentifier See 2x4 IfcSite documentation
= 'FootPrint'
IfcSite.IfcProductDefinitionShape.IfcShapeRepresentation.RepresentationT
ype = 'GeometricCurveSet', or 'Annotation2D'
Site Address REQUIRED M GSC-032
Address Address lines depending on local usage, street M/O IfcSite.SiteAddress.AddressLines (incl.) to be used as default (i.e. if there
number, street name, etc. are no specific building address
data)
City Town or city name M/O IfcSite.SiteAddress.Town (incl.)
State State, Region, or "Länder" optional in many countries M/O IfcSite.SiteAddress.Region (incl.)
Zip Postal code M/O IfcSite.SiteAddress.PostalCode (incl.)
Land Title Number GSC-032
Land Title Number What is this? Purpose? - IfcSite.LandTitleNumber (incl.) to be used as default (i.e. if there
are no specific building address
data)
Site Classification
Classification Site Classification (Nasjonal) Standard(Klassifikasjonssystem som er brukt for begrepene rundt - IfcClassificationReference (through relationship IfcRelAssociatesClassification) GSC-036
IfcSite.
Classification Item Key Key of classification item within the - IfcClassificationReference.ItemReference (incl.)
classification system
Classification Item Name Clear name of the classification item - IfcClassificationReference.Name (incl.)
Classification System Name Name of the classification system - IfcClassification.Name (through IfcClassificationReference.ReferencedSource) (incl.)
Classification System ID Identifyer of the classification system - IfcClassification.Source (through IfcClassificationReference.ReferencedSource) In IFC2x3 there is an implementer
agreement to store the unique Id
(encoding name, edition, version, etc.) in
Source field
Site Base Quantities IfcElementQuantity (through relationship IfcRelDefinedByProperties) (BSA-438)
Site Perimeter Total perimeter of the side - IfcQuantityLength.Name="GrossPerimeter" BSA-248
Site Gross Land Area Total area of the building site, as - IfcQuantityArea.Name="GrossArea" BSA-250
projected to the horizontal plane.
Site Properties IfcPropertySet (through relationship IfcRelDefinedByProperties) GSC-038
Site Common Properties Properties that are specified in the - IfcPropertySet with Name = "Pset_SiteCommon" GSC-039
standard property definitions (or a
relevant subset of) as defined in IFC site
common properties
Site Catalogue properties Property that is specified by an external - IfcPropertySet with Name = /* to be decided in local context */ and locally defined In IFC2x3 there is an implementer GSC-040
catalogue. Names are valid in the local properties agreement to store the link to the
context (e.g. by country, jurisdiction, catalogue as this functionality is not
building owner), only applicable in local defined in the IFC documentation (on the
context by additional agreements basis of existing attributes).
e.g. "tatsächliche GRZ" "Grundflächenzahl" Ratio between the - IfcPropertySingleValue (incl.)
buildable area and the total area of a .Name="tatsächliche GRZ", .Description="D_Merkmalkatalog_BFR ||
site ZL008.11.2.102"
.Value=0.65
Spatial Decomposition GSC-042
Site contained in Project "backlink" to the project as highest node [General]: one project object allowed M IfcRelAggregates with RelatingObject = IfcProject GSC-041 one project object allowed
in the project structure
Building contained in Site Reference to all buildings that are M IfcRelAggregates with RelatedObject = IfcBuilding VBL-504
situated on this site.
Site contained in Site NOT ALLOWED Needed in case a site is Not allowed? [General]: used for project structures, where a site has partial sites, not included N IfcRelAggregates with RelatedObject = IfcSite Allowed GSC-043 used for project structures, where
split into smaller parts. a site has partial sites, not
included
buildingSMART International: FM Aquarium Project page 2 Editor: Thomas Liebich
Basic HandOver to FM official view definition
Exchange Requirements (ER) for Georeferencing and Creation of Site Local Geometric Representation Mapping to IFC Definitions
MySupport
Object Type comments
Export
Import
Attribute Groups MVD MVD (K) Expand to see IFC representation
Property Definitions and notes Examples and further explanations Comments IFC Model Representation Comments generic binding General (P) Expand to see comments by person
Exchange Purpose: The purpose of this exchange is to provide correct georeferencing of a site in a project. The data exchanged will map the site's local origo (Multiple IfcSites allowed There is no limitations by a specific MDV. The ER's mandatory and optional data must be read and
in on project/IFC file? => IMpl agreements = >TH/TL) correctly to the earths surface and correctly give the deviation of the site's local Y axis from True North. (See IFC 2x4 specification interpreted correctly by the receiving applications. Other data can (should?/must?) be ignored by the
for IfcSite.) The file may optionally contain map or terrain representation of the site. This representation must be in the site's local coordinate system, not in a map coordinate system. receiving application but must not cause the application to fail. The minimum IFC version is 2x3. Where
(See IFC 2x4 specification for IfcSite.). 2x3 has shortcomings to 2x4, the workaround for 2x3 is documented.
Process outline: Advanced map and terrain handling is outside the scope of the current IFC Model. In projects these data are proveded on other formats defined by the GIS
community. Deciding the site's local origo must be done in a GIS system with IFC export capabilities or in a BIM system with GIS capabilites. This application must have an user
interface (UI) that allows the user to pick the site's local origo on the map and give the direction of the site's local Y axis relative to True North. Elevation for the site origo must be
obtained. How the UI obtains these data is entirely up to the designers of the application as long as the data obtained are correct. When this application wants to export the
georeferencing data to a BIM application these Exchange Requirements must be met. Any geometric representation of the site must be transformed to local site coordinates by the
application during the IFC export. See process map: ________________
NOTE: Deciding the origo of the site does not lock the posisition of the building(s). The local origo and orientation of the building can be set later relative to the site coordinate system.
Placing the building relative to the site coordinate system does not require a GIS system once the site has been properly georeferenced. NOTE2: Applications certified for IFC 2x3
coordination view should by definition be able to readan IFC which follows these ERs? How about the lack of a building?
NOTE: Any BIM application that imports an IFC with georeferencing must store all site related information in this ER. When the site is re-exported the original georeferencing data
must be kept without any loss of precision etc.
NOTE: If a BIM application has created a project and a dummy site, then it must be able to update the site information from the imported IFC file with georeferencing data and site
geometry.
Geographic Element Geographic objects from the GIS system Objects representing trees, roads, pipes, Note; the position, scaling and orientation of these objects must be converted to O Ifc2x4: IfcGeographicElement and IfcGeographicElementType Ifc2x3: IfcProxy and Owned by IfcSite through GSC-031
that are relevant to show on the site in a infrastructure, etc. fit the local site coordinate system. IfcProxy.Name (for element type) and IfcProxy.Tag (for element ID/position- IfcSite.ContainsElements
BIM system. number/instance identification). See Ifc2x4 documentation.
buildingSMART International: FM Aquarium Project page 3 Editor: Thomas Liebich
Related docs
