Orbit has the objective to support coordinate systems as they are described in the EPSG database by the OGP (International Association of Oil and Gas Producers).
Up to now Orbit supports any combination Geographic, Geocentric and Metric projected coordinate systems.
If it is your wish to use Feet projected coordinate system, please let us know. It is on our wishlist for a future update.
More information :
Orbit supports any combination of mobile mapping data and any coordinate system on import. But be wise :
The coordinate systems of all runs in a project must be the same. Convert CRS on import run if required, see above.
More information, see Orbit Mapping Resource
Point measurements (XYZ coordinates) are expressed in the Map Coordinate System, see Coordinate Reference Systems.
Distance, Length, Area or Volume measurements are expressed in metric units.
More information, see Measure.
When saving 3D measurements as features to a Dataset or Inventory Theme, measured coordinates will be converted respecting the Dataset CRS and Coordinate Type (2D, 3D). Attribute Rules using a relative measure result (e.g. length, height difference, clearance, … ) will be saved as calculated, see above.
To review and modify Dataset Coordinate Type, see Dataset Structure.
The Theme CRS is set on creation.
At import or export Theme coordinate transformation and/or re-projection are supported, see Manage Asset Inventory Themes
Working with multiple coordinate systems requires special attention.
Some simple rules to avoid issues on doing feature extracting from mobile mapping resources :
Orbit advises to do your data production in the same coordinate system as your mobile mapping data. If required theme can be exported to any coordinate system. This workflow avoids coordinate transformation at time of production
If you would have any coordinate system related question, contact the Orbit Support team (support at orbitgt dot com).