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 88: | Line 88: | ||
| 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]] |