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:19] jeroen |
dev:technology:core:crs [2024/04/04 18:27] (current) glen |
||
---|---|---|---|
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 188: | Line 201: | ||
- Add the value of the offset. \\ For example: < | - Add the value of the offset. \\ For example: < | ||
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 ===== | ||
- | |||
- | 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 Transformation ==== | ||
Line 206: | Line 209: | ||
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. | ||
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:// | ||
+ | |||
+ | Some Extensions expect data to be stored as meters or degrees to operate properly. \\ | ||
+ | When converting ft or ftUS Projected CRS into the equivalent Metric Projected CRS, display units can still be set to Imperial values. Display differs from storage. | ||
===== Orbit CRS Settings ===== | ===== Orbit CRS Settings ===== | ||
Line 216: | Line 222: | ||
=== Map CRS === | === Map CRS === | ||
- | The Map CRS can be set to any CRS supported by Orbit - feet or metric. However, for optimal rendering performance, | + | All visible Datasets are re-projected on-the-fly into the Map CRS, if the Dataset |
- | Absolute measurements | + | The Map CRS can be set to any supported geographic or projected |
+ | For optimal rendering performance, | ||
+ | If no Datasets are visible | ||
- | === Resource | + | The Map CRS can be set via [[dev:desktop: |
- | + | The Map CRS is stored in [[dev: | |
- | A resource | + | The Start-Up Map CRS can be set and locked via [[dev: |
- | * Some Orbit Extensions expect data to be stored as meters or degrees to operate. | + | |
- | * For Oblique, UAS, and Mobile Mapping resources and Vector Datasets, we do advise converting the CRS to the parent metric definition when importing the original resource files into the optimized Orbit Runs. | + | |
- | * All resources of a run or project should have the same CRS. | + | |
- | + | ||
- | When using these converted resources, display and exports | + | |
- | + | ||
- | === Units of Measurements === | + | |
- | + | ||
- | see [[dev: | + | |
=== Dataset CRS === | === Dataset CRS === | ||
- | Every single resource has a CRS. \\ | + | Orbit applies |
- | If no Orbit dataset | + | When combining |
- | There are two ways to set the CRS of a dataset in Orbit : | + | The Dataset CRS must be set correctly to any supported geocentric, geographic, or projected |
- | * [[dev: | + | * For ft and ftUS datasets it is advised to convert at import to the equivalent Metric Projected CRS (see note about Imperial CRS above). |
- | * [[dev: | + | * For Mapping Resources it is advised to convert at import all included Datasets into the same Dataset CRS. |
- | The dataset CRS is saved in the Orbit Resource Descriptor file : | + | The Dataset CRS can be set via [[dev: |
- | * [[dev: | + | The Dataset |
- | ===== Orbit Map CRS ====== | + | === Measurement Units === |
- | All visible datasets are re-projected on the fly, if the Dataset | + | Absolute measurements (2D and 3D Coordinates) use the MapCanvas |
- | <note tip> | + | see [[dev: |
- | 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:19