Recent Changes

Differences

This shows you the differences between two versions of the page.

--- dev:technology:core:crs [2024/02/21 10:56]
jeroen [Orbit CRS Settings]
+++ dev:technology:core:crs [2024/04/04 18:27] (current)
glen
@@ Line 45: / Line 45: @@
   * EPSG 2039, {{:technology:core:1002039_israel_-_israeli_tm_grid.zip|Israel 1993 / Israeli TM Grid}}, Israel
   * EPSG 2100, {{:technology:core:projection_grid_2100_hepos.zip|HEPOS Transformation}}, Greece
-  * EPSG 9300, {{:technology:core:projection_grid_9320.SnakeGrid_XRail02.zip|XRail09-2002 (SnakeGrid)}}
+  * EPSG 9320, {{:technology:core:projection_grid_9320.SnakeGrid_XRail02.zip|XRail09-2002 (SnakeGrid)}}
-  * EPSG 9320, {{:technology:core:projection_grid_9321.SnakeGrid_XRail15.zip|XRail09-2015 (SnakeGrid)}}
+  * EPSG 9321, {{:technology:core:projection_grid_9321.SnakeGrid_XRail15.zip|XRail09-2015 (SnakeGrid)}}
-  * EPSG 9321, {{:technology:core:projection_grid_9322.snakegrid_ecml14.zip|ECML14-NB (SnakeGrid)}}
-  * EPSG 9301, {{:technology:core:projection_grid_9301.snakegrid_hs202.zip|HS2 Survey Grid 02 (SnakeGrid)}}
   * EPSG 9322, {{:technology:core:projection_grid_9322.snakegrid_ecml14.zip|ECML14-NB (SnakeGrid)}}
+  * EPSG 9300, {{:technology:core:crs_9300_snakegrid_hs2_15.zip|HS2 Survey Grid 15 (SnakeGrid)}}
+  * EPSG 9301, {{:technology:core:projection_grid_9301.snakegrid_hs202.zip|HS2 Survey Grid 02 (SnakeGrid)}}
   * EPSG 9366, {{:technology:core:projection_grid_9366_snakegrid_tpen11.zip|TPEN11 Trans Pennine Systen (SnakeGrid)}}
   * EPSG 9370, {{:technology:core:projection_grid_9370.snakegrid_mml07.zip|MML07 Grid (SnakeGrid)}}
@@ Line 209: / Line 209: @@
 See [[dev:desktop:workspace:configurations|]] > Datum Transformation on Z coordinate
-===== International feet and US survey feet =====
+===== Imperial CRS, International Feet and US Survey Feet =====
 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://www.epsg-registry.org/ as the reference database. In the United States, the Federal definition of the CRS is metric at all times, but State law defines the CRS in International feet or US survey feet.
+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 =====
@@ Line 219: / Line 222: @@
 === 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 CRS differs from the Map CRS. Orbit supports imagery to be reprojected.
-Orbit supports imagery to be reprojected on the fly.
+The Map CRS can be set to any supported geographic or projected (Metric, Imperial) CRS. \\
+For optimal rendering performance, it is advised to set the Map CRS to be the same as the Dataset CRS of the visible Datasets to avoid on-the-fly reprojection. When having multiple Dataset CRS, set the Dataset CRS of the Dataset with the most vertices as Map CRS. ((Re-projecting datasets from their source Dataset CRS into another target Map CRS requires processing time. Consequently, large vector or point cloud resources will take more time to load and will slow down map rendering. It is advised to avoid on-the-fly re-projection by setting the Map CRS to be the same as the Dataset CRS.)). \\
+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:desktop:map:statusbar|]]. \\
 The Map CRS is stored in [[dev:technology:supported_formats:other:ogw|]]. \\
-The Start-Up Map CRS can be set via [[dev:desktop:preferences:mapcanvas|]].
+The Start-Up Map CRS can be set and locked via [[dev:desktop:preferences:mapcanvas|]].
-=== Define Map CRS ===
-The Map CRS can be set via the Map Status Bar. . \\
-Open the "Coordinate Reference System selection" window via a single click on the current Map Display CRS, see .
 === Dataset CRS ===
-Orbit sets a Dataset CRS for every loaded Resource. \\
+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. \\
-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. \\
-When combining resources with the different coordinate systems it is advised to define the coordinate system for every resource. \\
-A resource can have any CRS supported by Orbit - feet or metric. But be careful with the following:
+The Dataset CRS must be set correctly to any supported geocentric, geographic, or projected  CRS. \\
-  * Some Orbit Extensions expect data to be stored as meters or degrees to operate.
+  * 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 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.
+  * For Mapping Resources it is advised to convert at import all included Datasets into the same Dataset CRS.
-  * 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:desktop:dataset:index|Context Menu]] > [[dev:desktop:dataset:general|]]. \\
@@ Line 252: / Line 249: @@
 see [[dev:desktop:preferences:mapcanvas|]]
-===== 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.
-</note>
-=== Optimize Performance ===
-Re-projecting datasets from their source Dataset CRS into another target Map CRS requires processing time. Consequently, large vector or point cloud resources will take more time to load and will slow down map rendering. It is advised to avoid on the fly re-projection by using the Dataset CRS as Map CRS. When using multiple resources having different Dataset CRS, it is advised to use the Dataset CRS of the resources having most vertices as Map CRS.
-=== Deformations ===
-Re-projecting means deforming. To retain shape, angles, and presentation it's again advised to use the Dataset CRS as Map CRS.
-=== 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:56