Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dev:technology:core:crs [2024/02/21 10:13] jeroen [Horizontal CRS Definitions] |
dev:technology:core:crs [2024/04/04 18:27] (current) glen |
||
---|---|---|---|
Line 9: | Line 9: | ||
Use of CRS units foot (ft) or US survey foot (USft) required special attention. | Use of CRS units foot (ft) or US survey foot (USft) required special attention. | ||
- | ===== Horizontal CRS Definitions ===== | + | ===== Horizontal CRS Definitions ===== |
==== EPSG registry ==== | ==== EPSG registry ==== | ||
Line 45: | Line 45: | ||
* EPSG 2039, {{: | * EPSG 2039, {{: | ||
* EPSG 2100, {{: | * EPSG 2100, {{: | ||
- | * EPSG 9300, {{: | + | * EPSG 9320, {{: |
- | * EPSG 9320, {{: | + | * EPSG 9321, {{: |
- | * EPSG 9321, {{: | + | |
- | * EPSG 9301, {{: | + | |
* EPSG 9322, {{: | * EPSG 9322, {{: | ||
+ | * EPSG 9300, {{: | ||
+ | * EPSG 9301, {{: | ||
* EPSG 9366, {{: | * EPSG 9366, {{: | ||
* EPSG 9370, {{: | * EPSG 9370, {{: | ||
Line 97: | Line 97: | ||
The Custom Horizontal CRS will be available via the Orbit CRS Window by entering a) the projection name as stated in the prj content, b) its number as used in the prj file name, or c) via the CRS By Country list under Undefined Area. | The Custom Horizontal CRS will be available via the Orbit CRS Window by entering a) the projection name as stated in the prj content, b) its number as used in the prj file name, or c) via the CRS By Country list under Undefined Area. | ||
- | ==== Custom | + | ==== Data Transformation ==== |
+ | |||
+ | Orbit embeds the latest set of TOWGS84 transformation parameters known by the EPSG library. | ||
- | Orbit embeds the latest set of TOWGS84 transformation parameters known by the EPSG library. \\ | ||
Customization for the Geodetic CRS can be set via ''< | Customization for the Geodetic CRS can be set via ''< | ||
* Note: Strict data input is required within the.ini file. Data must imported Tab separated(reference transformations_to_4326.ini) | * Note: Strict data input is required within the.ini file. Data must imported Tab separated(reference transformations_to_4326.ini) | ||
Line 114: | Line 115: | ||
The Grid Shift Binary (GSB) defines the raster to interpolate a correction for each global lat/lon coordinate(WGS84/ | The Grid Shift Binary (GSB) defines the raster to interpolate a correction for each global lat/lon coordinate(WGS84/ | ||
Next, a custom horizontal projection is applied to obtain cartesian coordinates from the geographic coordinates. | Next, a custom horizontal projection is applied to obtain cartesian coordinates from the geographic coordinates. | ||
+ | |||
+ | ==== Inverted CRS definitions ==== | ||
+ | |||
+ | Orbit follows CRS specifications, | ||
+ | |||
+ | Unfortunately, | ||
+ | To consume user data provided as Easting-Northing, | ||
+ | The inverted CRS are in the range of 3 million. E.g ESPG 3001 (NE) and 3003001 (EN). | ||
+ | |||
+ | All CRS defined by EPSG to be Northing-Easing are pre-added to the list of Inverted CRS, and any EPSG code can be added to this list: <Install Dir>/ | ||
+ | |||
+ | |||
===== Vertical CRS Definitions ===== | ===== Vertical CRS Definitions ===== | ||
- | ==== Global and Local Vertical CRS Definitions | + | ==== Global and Local Vertical CRS ==== |
Orbit supports Global and Local Geoid references for the combined use of WGS84 Ellipsoidal and Orthometric height. \\ | Orbit supports Global and Local Geoid references for the combined use of WGS84 Ellipsoidal and Orthometric height. \\ | ||
Line 166: | Line 179: | ||
- Restart Orbit. | - Restart Orbit. | ||
- | ==== Custom Vertical CRS Definitions | + | ==== Custom Vertical CRS ==== |
Orbit supports Custom Vertical CRS via a Geoid Height Raster definition. | Orbit supports Custom Vertical CRS via a Geoid Height Raster definition. | ||
Line 176: | Line 189: | ||
* XYZ ascii file space, comma or semicolon separated. | * XYZ ascii file space, comma or semicolon separated. | ||
- | + | ==== Custom Vertical CRS via Offset or Scaling | |
- | === Custom Vertical CRS via Offset or Scaling === | + | |
Scaled and offset vertical CRS definitions. Custom Vertical CRS relies on already existing EPSG codes.\\ | Scaled and offset vertical CRS definitions. Custom Vertical CRS relies on already existing EPSG codes.\\ | ||
Line 190: | Line 202: | ||
Restart Orbit to acknowledge in the software the new custom CRS. | Restart Orbit to acknowledge in the software the new custom CRS. | ||
- | ===== Inverted CRS definitions ===== | + | ==== Datum Transformation ==== |
- | + | ||
- | Orbit follows CRS specifications, | + | |
- | + | ||
- | Unfortunately, | + | |
- | To consume user data provided as Easting-Northing, | + | |
- | The inverted CRS are in the range of 3 million. E.g ESPG 3001 (NE) and 3003001 (EN). | + | |
- | + | ||
- | All CRS defined by EPSG to be Northing-Easing are pre-added to the list of Inverted CRS, and any EPSG code can be added to this list: <Install Dir>/ | + | |
- | + | ||
- | + | ||
- | ===== Datum Transformation | + | |
- | Datum transformations are applied as defined by EPSG on XY coordinates. Z values are conserved as is, no transformation is applied. \\ | + | Datum transformations are applied as defined by EPSG on XY coordinates. Z values are conserved as is, and no transformation is applied. \\ |
Datum transformation on Z values can be enabled e.g. to combine multiple 3D data resources with different ellipsoid height definitions. | Datum transformation on Z values can be enabled e.g. to combine multiple 3D data resources with different ellipsoid height definitions. | ||
See [[dev: | See [[dev: | ||
- | ===== International | + | ===== Imperial CRS, International |
Projected CRS using International feet (ft) or US survey feet (ftUS) units require special attention. | Projected CRS using International feet (ft) or US survey feet (ftUS) units require special attention. | ||
Line 214: | Line 215: | ||
The Orbit Core and Map Components support Projected CRS using ft and ftUS. Orbit uses https:// | The Orbit Core and Map Components support Projected CRS using ft and ftUS. Orbit uses https:// | ||
- | ==== Map CRS ==== | + | Some Extensions expect data to be stored as meters or degrees to operate properly. \\ |
+ | When converting ft or ftUS Projected | ||
- | The Map CRS can be set to any CRS supported by Orbit - feet or metric. However, for optimal rendering performance, | + | ===== Orbit CRS Settings ===== |
- | Absolute measurements (2D and 3D Coordinates) use the MapCanvas | + | === Map CRS === |
- | ==== Resource | + | All visible Datasets are re-projected on-the-fly into the Map CRS, if the Dataset CRS differs from the Map CRS. Orbit supports imagery to be reprojected. |
- | A resource | + | The Map CRS can be set to any supported |
- | * Some Orbit Extensions expect data to be stored | + | For optimal rendering performance, |
- | * For Oblique, UAS, and Mobile Mapping | + | If no Datasets are visible in the workspace, then the first visible Dataset CRS will set the Map CRS. |
- | * All resources of a run or project should have the same CRS. | + | |
- | When using these converted resources, display and exports | + | The Map CRS can be set via [[dev: |
+ | The Map CRS is stored | ||
+ | The Start-Up Map CRS can be set and locked via [[dev: | ||
- | ==== Units of Measurements ==== | + | === Dataset CRS === |
- | see [[dev: | + | Orbit applies a CRS for every Dataset. If no Dataset CRS is set, Orbit assumes the Dataset CRS to be the same as the Map CRS. \\ |
+ | When combining Datasets with the different CRS, it is advised to define the CRS for every Dataset. \\ | ||
- | ===== Orbit Dataset CRS ===== | + | The Dataset CRS must be set correctly to any supported geocentric, geographic, or projected |
+ | * For ft and ftUS datasets it is advised to convert at import to the equivalent Metric Projected CRS (see note about Imperial CRS above). | ||
+ | * For Mapping Resources it is advised to convert at import all included Datasets into the same Dataset CRS. | ||
- | Every single resource has a CRS. \\ | + | The Dataset |
- | If no Orbit dataset | + | The Dataset |
- | There are two ways to set the CRS of a dataset in Orbit : | + | === Measurement Units === |
- | * [[dev: | + | |
- | * [[dev: | + | |
- | The dataset | + | Absolute measurements (2D and 3D Coordinates) use the MapCanvas CRS. In case the vertical MapCanvas |
- | * [[dev: | + | |
- | ===== Orbit Map CRS ====== | + | see [[dev: |
- | + | ||
- | All visible datasets are re-projected on the fly, if the Dataset CRS differs from the Map CRS, to be rendered in the Map CRS. | + | |
- | + | ||
- | <note tip> | + | |
- | The Map Display CRS has an impact on the map rendering performance. | + | |
- | </ | + | |
- | + | ||
- | === Optimize Performance === | + | |
- | + | ||
- | Re-projecting datasets from their source Dataset CRS into another target Map CRS requires processing time. Consequently, | + | |
- | + | ||
- | === Deformations === | + | |
- | + | ||
- | Re-projecting means deforming. To retain shape, angles, and presentation it's again advised to use the Dataset CRS as Map CRS. | + | |
- | + | ||
- | === Define Map CRS === | + | |
- | + | ||
- | The Map CRS can be set via the Map Status Bar. . \\ | + | |
- | Open the " | + | |
- | + | ||
- | The Map CRS on start-up is defined in the Orbit Workspace and can be controlled via the Map View Preferences. \\ | + | |
- | See [[dev: | + | |
- | + | ||
- | === Default behavior and preferences === | + | |
- | + | ||
- | If no datasets are visible in the current workspace then the first visible dataset CRS will be used as Map CRS. | + | |
Last modified:: 2024/02/21 10:13