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:41] jeroen [Orbit CRS Settings] |
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 209: | 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 219: | 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, we do advise using the CRS of the resources that are currently viewed. \\ | + | All visible Datasets are re-projected on-the-fly into the Map CRS, if the Dataset |
- | Orbit supports imagery to be reprojected | + | |
- | === Dataset CRS === | + | The Map CRS can be set to any supported geographic or projected (Metric, Imperial) CRS. \\ |
+ | For optimal rendering performance, | ||
+ | If no Datasets are visible in the workspace, then the first visible Dataset CRS will set the Map CRS. | ||
- | Orbit sets a Dataset CRS for every loaded Resource. | + | The Map CRS can be set via [[dev: |
- | If no Dataset CRS is set, Orbit assumes the Dataset CRS to be the same as the Map CRS. \\ | + | The Map CRS is stored in [[dev: |
- | When combining resources with the different coordinate systems it is advised to define the coordinate system for every resource. \\ | + | The Start-Up Map CRS can be set and locked via [[dev: |
- | A resource can have any CRS supported by Orbit - feet or metric. But be careful with the following: | + | === Dataset |
- | * 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 can still be set to ft or ftUS to get exactly | + | 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 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. | ||
- | There are two ways to set the CRS of a dataset in Orbit : | + | The Dataset CRS can be set via [[dev: |
- | * [[dev: | + | The Dataset CRS is stored |
- | * [[dev: | + | |
- | + | ||
- | The dataset | + | |
- | * [[dev: | + | |
=== Measurement Units === | === Measurement Units === | ||
Line 248: | Line 249: | ||
see [[dev: | see [[dev: | ||
- | |||
- | |||
- | ===== Orbit Map CRS ====== | ||
- | |||
- | 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:41