Difference between revisions of "MicroMVDs for exchange requirements/Geolocation MicroMVD"
From Wiki.OSArch
Line 15: | Line 15: | ||
* There must be at least one IfcSite element | * There must be at least one IfcSite element | ||
* The project must have coordinate reference system data | * The project must have coordinate reference system data | ||
− | * The name of the CRS must be | + | * The name of the CRS must be {coordinate_reference_name} |
− | * The geodetic datum must be | + | * The geodetic datum must be {coordinate_reference_name} |
− | * The vertical datum must be | + | * The vertical datum must be {coordinate_reference_name} |
− | * The map projection must be | + | * The map projection must be {coordinate_reference_name} |
− | * The map zone must be | + | * The map zone must be {coordinate_reference_name} |
− | * The map unit must be | + | * The map unit must be {unit} |
Scenario: Local coordinate systems are specified relative to a global system | 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 project must have coordinate transformations to convert from local to global coordinates | ||
− | * The eastings of the model must be offset by | + | * The eastings of the model must be offset by {number} to derive its global coordinates |
− | * The northings of the model must be offset by | + | * The northings of the model must be offset by {number} to derive its global coordinates |
− | * The height of the model must be offset by | + | * The height of the model must be offset by {number} to derive its global coordinates |
− | * The model must be rotated clockwise by | + | * The model must be rotated clockwise by {number} to derive its global coordinates |
− | * The model must be scaled along the horizontal axis by | + | * 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 {number} | ||
+ | * The site {guid} has a latitude of {number} | ||
+ | * The site {guid} has an elevation of {number} | ||
</pre> | </pre> | ||
Line 46: | Line 51: | ||
| The schema version. At the moment, these are likely to be either IFC4 or IFC2X3. | | The schema version. At the moment, these are likely to be either IFC4 or IFC2X3. | ||
|- | |- | ||
− | | <code>{ | + | | <code>{coordinate_reference_name}</code> |
| EPSG:7856 | | 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. | | 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. |
Revision as of 01:43, 21 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 {coordinate_reference_name} * 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 {number} * The site {guid} has a latitude of {number} * 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. |
{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. |