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:44] 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 | + | |
- | The Map CRS can be set via | + | 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. | ||
+ | |||
+ | The Map CRS can be set via [[dev: | ||
+ | The Map CRS is stored in [[dev: | ||
+ | The Start-Up Map CRS can be set and locked via [[dev: | ||
=== Dataset CRS === | === Dataset CRS === | ||
- | Orbit sets a Dataset | + | Orbit applies |
- | If no Dataset CRS is set, Orbit assumes the Dataset CRS to be the same as the Map CRS. \\ | + | When combining |
- | When combining | + | |
- | A resource can have any CRS supported | + | The Dataset CRS must be set correctly to any supported |
- | * Some Orbit Extensions expect data to be stored as meters or degrees | + | * For ft and ftUS datasets it is advised |
- | * For Oblique, UAS, and Mobile | + | * For Mapping |
- | * 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 the expected results. A user won't notice the data is stored using the parent metric CRS. | + | The Dataset CRS can be set via [[dev: |
- | + | The Dataset | |
- | The Dataset CRS can be est via [[dev: | + | |
- | The dataset | + | |
=== Measurement Units === | === Measurement Units === | ||
Line 245: | 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:44