Home » railML newsgroups » railML.infrastructure » [railML3] Proposing new @epsgCode for <geometricPositioningSystem>
Re: [railml3] Proposing new @epsgCode for <geometricPositioningSystem> [message #3916 is a reply to message #3915] Sat, 28 February 2026 00:51 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,

No, I would allow all URI's for CRS in railML. And then it's up to the software vendor to specify which URI CRS's he supports. And he could say that he supports all http://www.opengis.net/def/crs/ URI's for example. Or only WGS84 or UTM32.

I would definitely also allow custom URI's so that railML providers can use their own coordinate system URI and request software vendors to support them by providing them with the required information to do so.

I haven't had any issues with conversions between coordinate systems (for OGC defined ones), but I might not understand what coordinate systems that you are referring to. For my yasgui fork, it happens on the fly from any coordinate system: https://shorter.matdata.eu/w


Mathias Vanden Auweele
Railway data freelancer
https://matdata.eu
Brussels, Belgium
 
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:
  


Current Time: Sun Oct 11 20:22:45 GMT+2 2026