| Re: [railml3] Proposing new @epsgCode for <geometricPositioningSystem> [message #4129 is a reply to message #4128] |
Thu, 27 August 2026 16:13   |
Mathias Vanden Auweele
Messages: 174
Registered: February 2025
Location: Brussels
|
Senior Member |
|
|
Thank you Thomas, that sounds like music to my ears!
Could you also add a note on axis ordering to the wiki? What you write in your previous post already explains it:
Quote:
- The data consumer does *not* have to assume the axis ordering of an EPSG CRS. It is given in the CRS definition that is as uniquely identified with an int as with an opengis URI. OGC:CRS84 is not the same CRS as EPSG:4326, because the axes are switched, and their definitions are therefore not the same.
A small note saying that OGC:CRS84 assumes that x = longitude and for EPSG:4326 x = latitude should already go a long way in solving any issues.
Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
|
|
|
|
Search
Help
Members
Login
Home
