Difference between revisions of "MicroMVDs for exchange requirements/Geolocation MicroMVD"

From Wiki.OSArch
(Created page with "The following MicroMVD vocabulary can be used to ensure geolocation information is set. <pre> Feature: Geolocation In order to...")
 
Line 7: Line 7:
 
As a recipient expecting to integrate BIM and GIS datasets
 
As a recipient expecting to integrate BIM and GIS datasets
 
Geolocation data must be stored correctly in received files
 
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 "{name}"
 +
* The geodetic datum must be "{name}"
 +
* The vertical datum must be "{name}"
 +
* The map projection must be "{name}"
 +
* The map zone must be "{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
 
</pre>
 
</pre>
  
−
TODO.
+
You can fill out the variables using the guide below.
  
 
{| class="wikitable"
 
{| class="wikitable"
−
! Test definition
+
! Variable
−
! Justification
+
! Example
 +
! Description
 
|-
 
|-
−
| <code>Then the project should have geolocation data</code>
+
| <code>{file}</code>
−
| This checks for geolocation according to the buildingSMART recommendation in IFC2X3 and the native elements in IFC4.
+
| project.ifc
 +
| The filename or path to any IFC file.
 
|-
 
|-
−
| <code>Given there is at least one IfcSite element</code>
+
| <code>{schema}</code>
−
| Most projects have a site.
+
| IFC4
 +
| The schema version. At the moment, these are likely to be either IFC4 or IFC2X3.
 
|-
 
|-
−
| <code>Then there is an IfcSite element with a Name attribute with a value of "{value}"</code>
+
| <code>{name}</code>
−
| If a site exists, it typically has a 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.
 
|-
 
|-
−
| <code>Given there is at least one IfcBuilding element</code>
+
| <code>{unit}</code>
−
| Most projects have a building.
+
| Metre
 +
| This case insensitive text value may contain an optional [https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/link/ifcsiprefix.htm prefix] followed by an [https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/link/ifcsiunitname.htm SI unit] or an [https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC1/HTML/link/ifcconversionbasedunit.htm converted unit]
 
|-
 
|-
−
| <code>Then there is an IfcBuilding element with a Name attribute with a value of "{value}"</code>
+
| <code>{number}</code>
−
| If a building exists, it typically has a name.
+
| 42.12
 +
| Any numerical value you expect for a particular attribute or property.
 
|}
 
|}

Revision as of 23:28, 20 July 2020

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 "{name}"
 * The geodetic datum must be "{name}"
 * The vertical datum must be "{name}"
 * The map projection must be "{name}"
 * The map zone must be "{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

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.
{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.
Retrieved from "https://wiki.osarch.org/index.php?title=MicroMVDs_for_exchange_requirements/Geolocation_MicroMVD&oldid=506"