Database: update to EPSG v12.055#4764
Conversation
- does *not* address ETRS89 issues - rename JGD2011 to JGD2024... sigh - adds gllat_2025 and glmsl_2025 (CC @kbevers) Besides that, tune import script to not import ISO geodetic registry codes as name aliases.
|
Regarding Japan, for JGD2024 (geographic) to "JGD2024 (vertical) height" (what used to be JGD2011 to JGD2024 vertical), the recommended way (new concatenated operation 11441) is to apply :
rather than applying jp_gsi_jpgeo2024.tif which we have... EPSG:11441 "This concatenated operation is the path recommended by GSI for deriving JGD2024 (vertical) height from GNSS-derived ellipsoidal height in accordance with Survey Act requirements, as using the JPGEO2024 geoid separation model directly (JGD2024 to JGD2024 (vertical) height (1), CT code 11334) is not aligned with Survey Act requirements for coordinates to be at epoch 2011.395." Japanese grid (& license) hunters, the floor is yours... (CC @tohka @hernando @jjimenezshaw ) |
Apparently it is in https://www.gsi.go.jp/sokuchikijun/sokuchikijun41012.html We would need somebody with more knowledge about the PatchJGD format and the license of the file. There is a program to open PatchJGD files. I cannot open it, as it is only Windows. And I will not understand the Japanese menus. |
😮 🤦 "On adoption of JGD2024 (vertical) with effect from 1st April 2025, the name of this geodetic CRS was changed from JGD2011 to JGD2024; there is no change of definition or of coordinate values" |
Besides that, tune import script to not import ISO geodetic registry codes as name aliases.