MicroMVDs for exchange requirements/Geolocation MicroMVD

This page is about MVD - Model View Definitions. Full documentation is available at the buildingSMART site. All articles in the OSArch wiki related to Model View Definitions (MVD) can be seen in the Model View Definitions (MVD) Category

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: Receiving a file
 * The IFC file "{file}" must be provided
 * IFC data must use the {schema} schema

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: Global coordinates of the project origin 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}

You can fill out the variables using the guide below.

Variable	Example	Description
{file}	project.ifc	The filename or path to any IFC file.
{schema}	IFC4	The schema version. At the moment, these are likely to be either IFC4 or IFC2X3.
{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
	BlenderBIM Add-on	v0.0.200829	v0.0.200829
	FreeCAD
	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