Editing MicroMVDs for exchange requirements/Geolocation MicroMVD
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | |||
The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. | The following [[Using MicroMVDs for exchange requirements|MicroMVD]] vocabulary can be used to ensure geolocation information is set. | ||
Line 8: | 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 | Scenario: Geometry is georeferenced to a coordinate reference system | ||
− | * There must be at least one | + | * 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 "{name}" |
− | + | * The geodetic datum must be "{name}" | |
− | * The geodetic datum must be "{ | + | * The vertical datum must be "{name}" |
− | * The vertical datum must be "{ | + | * The map projection must be "{name}" |
− | * The map projection must be "{ | + | * The map zone must be "{name}" |
− | * The map zone must be "{ | ||
* The map unit must be "{unit}" | * The map unit must be "{unit}" | ||
Line 27: | Line 29: | ||
* The model must be rotated clockwise 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 | * The model must be scaled along the horizontal axis by "{number}" to derive its global coordinates | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</pre> | </pre> | ||
Line 45: | Line 38: | ||
! Description | ! Description | ||
|- | |- | ||
− | | <code>{ | + | | <code>{file}</code> |
− | | | + | | project.ifc |
− | | | + | | The filename or path to any IFC file. |
|- | |- | ||
− | | <code>{ | + | | <code>{schema}</code> |
+ | | IFC4 | ||
+ | | The schema version. At the moment, these are likely to be either IFC4 or IFC2X3. | ||
+ | |- | ||
+ | | <code>{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. | ||
Line 60: | Line 57: | ||
| 42.12 | | 42.12 | ||
| Any numerical value you expect for a particular attribute or property. | | Any numerical value you expect for a particular attribute or property. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− |