Knowledge Base
Recent Changes

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
dev:technology:core:crs [2019/10/01 09:02]
paulien [International feet and US survey feet] 		dev:technology:core:crs [2019/12/17 13:21]
thijs [Vertical CRS Definitions]
Line 109: Line 109:
     * EPSG 6644, GUVD04 height, Guam Vertical Datum of 2004.     * EPSG 6644, GUVD04 height, Guam Vertical Datum of 2004.
   * EPSG 5709, NAP height, Netherlands. \\ This Vertical CRS is included in the corresponding Local Horizontal CRS definition, see above.   * EPSG 5709, NAP height, Netherlands. \\ This Vertical CRS is included in the corresponding Local Horizontal CRS definition, see above.
 +  * EPSG 5720, {{ :dev:technology:core:vertical_5720.nfg_height.zip |NGF-IGN69 height}}, France.
 +  * EPSG 5941,{{:dev:technology:core:vertical_5941.geoidnn2000_height_.zip|NN2000 height}}, Norway.\\ 
   * EPSG 5710, {{:dev:technology:coordinate_systems:vertical_5710.geoid.ostend_height.zip|Ostend height}}, Belgium.   * EPSG 5710, {{:dev:technology:coordinate_systems:vertical_5710.geoid.ostend_height.zip|Ostend height}}, Belgium.
   * EPSG 5731, Malin Head height, Ireland. \\ This Vertical CRS is included in the corresponding Local Horizontal CRS definition, see above.   * EPSG 5731, Malin Head height, Ireland. \\ This Vertical CRS is included in the corresponding Local Horizontal CRS definition, see above.
   * EPSG 5732, Belfast height, Northern Ireland. \\ This Vertical CRS is included in the corresponding Local Horizontal CRS definition, see above.   * EPSG 5732, Belfast height, Northern Ireland. \\ This Vertical CRS is included in the corresponding Local Horizontal CRS definition, see above.
-  * EPSG 5941,{{:dev:technology:core:vertical_5941.geoidnn2000_height_.zip|NN2000 height}}, Norway.\\ +
  
 Vertical CRS definitions are not available by default. \\ Vertical CRS definitions are not available by default. \\
Line 138: Line 140:
 For any coordinate system, Orbit follows the order of axes as defined by the EPSG library. As a result, Orbit expects data to also respect the order as defined by EPSG definition.  For any coordinate system, Orbit follows the order of axes as defined by the EPSG library. As a result, Orbit expects data to also respect the order as defined by EPSG definition. 
  
-In practice, from various motifs, like changes in the CRS definitions by local mapping authorities, or different order of axes implementations in other software, data may be stored using a different order.  +In practice, for various reasons like changes in the CRS definitions by local mapping authorities or different order of axes implementations in other software, data may be stored using a different order.  
-For this cases, in the Orbit CRS Lybrary, you will find listed for some coordinate systems both the original crs and the inverted one. +Because of this, you will find that some coordinate systems are listed as both the original crs and the inverted one in the Orbit CRS Library.
  
 To define the projection of any resource, the original CRS should be used if the data is stored according to the EPSG order axes definition, and the inverted CRS should be used for data in which the order is reversed.  To define the projection of any resource, the original CRS should be used if the data is stored according to the EPSG order axes definition, and the inverted CRS should be used for data in which the order is reversed. 
 
Last modified:: 2024/04/04 18:27