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 8: | Line 8: | ||
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 {coordinate_reference_name} |
| − | * The description of the CRS must be | + | * The description of the CRS must be {value} |
| − | * 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: | + | 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} | |
| − | * The site | ||
| − | * The site | ||
| − | * The site | ||
| − | |||
</pre> | </pre> | ||
| Line 44: | Line 44: | ||
! Example | ! Example | ||
! Description | ! Description | ||
| + | |- | ||
| + | | <code>{file}</code> | ||
| + | | project.ifc | ||
| + | | The filename or path to any IFC file. | ||
| + | |- | ||
| + | | <code>{schema}</code> | ||
| + | | IFC4 | ||
| + | | The schema version. At the moment, these are likely to be either IFC4 or IFC2X3. | ||
|- | |- | ||
| <code>{value}</code> | | <code>{value}</code> | ||
| Line 88: | Line 96: | ||
| style="background-color: #ffd37f;" | ArchiCAD 23 | | style="background-color: #ffd37f;" | 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. | | 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. | ||
| − | | | + | | |
|- | |- | ||
| [[File:BlenderBIM_Addon_logo.png|64x64px]] | | [[File:BlenderBIM_Addon_logo.png|64x64px]] | ||
| Line 99: | Line 107: | ||
| [[File:icon_FreeCAD.png]] | | [[File:icon_FreeCAD.png]] | ||
| [[FreeCAD]] | | [[FreeCAD]] | ||
| − | | | + | | |
| − | | | + | | |
| − | | | + | | |
| | | | ||
|- | |- | ||
| Line 118: | Line 126: | ||
| | | | ||
|} | |} | ||
| − | |||
| − | |||
[[Category:Model View Definitions (MVD)]] [[Category:BIMTester]] [[Category:MicroMVD]] | [[Category:Model View Definitions (MVD)]] [[Category:BIMTester]] [[Category:MicroMVD]] | ||
