Geolocation MicroMVD
The following MicroMVD vocabulary can be used to ensure geolocation information is set.
Feature: Geolocation
In order to query data in real world coordinates
As a recipient expecting to integrate BIM and GIS datasets
Geolocation data must be stored correctly in received files
Scenario: Geometry is georeferenced to a coordinate reference system
* There must be at least one "IfcSite" element
* The project must have coordinate reference system data
* The name of the CRS must be "{coordinate_reference_name}"
* The description of the CRS must be "{value}"
* The geodetic datum must be "{coordinate_reference_name}"
* The vertical datum must be "{coordinate_reference_name}"
* The map projection must be "{coordinate_reference_name}"
* The map zone must be "{coordinate_reference_name}"
* The map unit must be "{unit}"
Scenario: Local coordinate systems are specified relative to a global system
* The project must have coordinate transformations to convert from local to global coordinates
* The eastings of the model must be offset by "{number}" to derive its global coordinates
* The northings of the model must be offset by "{number}" to derive its global coordinates
* The height of the model must be offset by "{number}" to derive its global coordinates
* The model must be rotated clockwise by "{number}" to derive its global coordinates
* The model must be scaled along the horizontal axis by "{number}" to derive its global coordinates
Scenario: A true north rotation of the project origin is provided for convenient reference
* The model must be rotated clockwise by "{number}" for true north to point up
Scenario: Global coordinates of the site origins are provided for convenient reference
* The site "{guid}" has a longitude of "{longlat}"
* The site "{guid}" has a latitude of "{longlat}"
* The site "{guid}" has an elevation of "{number}"
* The site "{guid}" must be coincident with the project origin
You can fill out the variables using the guide below.
| Variable | Example | Description |
|---|---|---|
{value} | Anything | Any arbitrary value if it adds meaning required by the project. |
{coordinate_reference_name} | EPSG:7856 | If this exists in the EPSG registry, the EPSG identifier must be provided. If not, it may be arbitrarily specified as a custom text name. |
{unit} | Metre | This case insensitive text value may contain an optional prefix followed by an SI unit or an converted unit |
{number} | 42.12 | Any numerical value you expect for a particular attribute or property. |
{longlat} | 42.12 | Either a longitude or latitude expressed in a decimal degrees. |
{guid} | 28q3AgmxP5cepIweO5Of$o | This is a 22 character GlobalId for a particular IFC element. |
Software guides
| Icon | Software | Certified Version | Notes | Guides | Import | Export |
|---|---|---|---|---|---|---|
 | ArchiCAD | ArchiCAD 23 | ArchiCAD 23 | You cannot export a unit for the coordinate reference system. Also, when exporting to IFC, it may apply the true north rotation, but retain the rotation in the geolocation properties, thus effectively defining the rotation twice. This leads to an incorrectly geolocated model which needs to be patched. Upon importing such a file with a doubly defined rotation, the map conversion seems to be ignored. This can cause problems with correctly geolocated files coming from other software. | ArchiCAD geolocation describes how to set these attributes | |
 | Bonsai | v0.0.200829 | v0.0.200829 | |||
 | FreeCAD | 0.19pre | 0.19pre | When exporting, the true north rotation is incorrectly rotated by 90 degrees. When importing, the units of the site reference elevation may be incorrectly converted. | ||
 | Revit | Revit 2020.2 IFC 8/5/2020 | Revit 2020.2 IFC 8/5/2020 | During import, all geolocation information is lost. During export, workarounds are required using external patching tools to achieve the desired outcome. | Revit geolocation describes how to set these attributes | |
 | Tekla |