Home » railML newsgroups » railML.infrastructure » [railML3] Proposing new @epsgCode for <geometricPositioningSystem>
Re: [railml3] Proposing new @epsgCode for <geometricPositioningSystem> [message #3914 is a reply to message #3913] Thu, 26 February 2026 00:36 Go to previous messageGo to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 174
Registered: February 2025
Location: Brussels
Senior Member
Hi Milan,

Yes you are correct and I needed to be more clear.

This is written in the W3C & OGC standard GeoSPARQL specification https://docs.ogc.org/is/22-047r1/22-047r1.html:
Quote:
The OGC maintains a set of SRS IRIs under the http://www.opengis.net/def/crs/ namespace and IRIs from this set are recommended for use. However others may also be used, as long as they are valid IRIs.
So while I would allow the use of ANY URI in railml for the crs, it will be up to the software supplier to be very clear in which CRS that he will support. And by listing these as OGC managed SRS IRI's, it becomes very very clear what is meant. Furthermore, conversion between OGC managed CRS is trivial with libraries such as betterknown https://github.com/placemark/betterknown and proj4

Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML3.3] xs:choice between linearCoordinate and geometricCoordinate
Next Topic: [railML3] Restricting aggregation of RailTopoModel
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 11 20:10:42 GMT+2 2026