Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
dev:technology:core:crs [2019/09/12 14:58] thijs [Horizontal CRS Definitions] |
dev:technology:core:crs [2020/06/22 16:36] thijs |
||
---|---|---|---|
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, {{ : | ||
+ | * EPSG 5941, | ||
* EPSG 5710, {{: | * EPSG 5710, {{: | ||
* 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, | + | * EPSG 9988, {{ : |
Vertical CRS definitions are not available by default. \\ | Vertical CRS definitions are not available by default. \\ | ||
Line 138: | Line 141: | ||
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, | + | In practice, |
- | 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 |
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. | ||
Line 160: | Line 163: | ||
A resource can have any CRS supported by Orbit - feet or metric. But be careful with the following: | A resource can have any CRS supported by Orbit - feet or metric. But be careful with the following: | ||
* Some Orbit Extensions expect data to be stored as meters or degrees to operate. | * Some Orbit Extensions expect data to be stored as meters or degrees to operate. | ||
- | * For Oblique, UAS and Mobile Mapping resources, we do advise to convert the CRS to the parent metric definition when importing the original resource files into the optimized Orbit Runs. | + | * For Oblique, UAS and Mobile Mapping resources |
* All resources of a run or project should have the same CRS. | * All resources of a run or project should have the same CRS. | ||
Last modified:: 2024/04/04 18:27