Home » railML newsgroups » railML.infrastructure » [railML3] Use of geometricPositioningSystem/@crsDefinition (Make geometricPositioningSystem/@crsDefinition mandatory)
[railML3] Use of geometricPositioningSystem/@crsDefinition [message #4001] Fri, 08 May 2026 19:01 Go to next message
Larissa Zhuchyi is currently offline  Larissa Zhuchyi
Messages: 104
Registered: November 2022
Senior Member
Dear all

During yet another review of railML 3.3 XSD we noticed that in RailTopoModel the attribute geometricPositioningSystem/@crsDefinition is optional. geometricPositioningSystem however seems to be meaningless without @crsDefinition.

It is planned to make @crsDefinition mandatory in railML 3.4 (consequently in RTM 1.6) in case there are no situations reported where geometricPositioningSystem/@crsDefinition is unknown.

Please let us know if at some points you cannot fulfil the demand to provide geometricPositioningSystem/@crsDefinition.

Sincerely,

Larissa Zhuchyi – Ontology Researcher
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

[Updated on: Fri, 08 May 2026 19:07]

Report message to a moderator

Re: [railML3] Use of geometricPositioningSystem/@crsDefinition [message #4002 is a reply to message #4001] Fri, 08 May 2026 21:50 Go to previous message
Mathias Vanden Auweele is currently offline  Mathias Vanden Auweele
Messages: 129
Registered: February 2025
Location: Brussels
Senior Member
Hello Larissa, this is OK for me

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

Report message to a moderator

Previous Topic: [railML3] New semantic constraint restricting RTM:level, IS:netElement and IS:netRelation
Next Topic: [railML3] Stopping places with several lengths
Goto Forum:
  

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

Current Time: Wed Jun 17 05:38:25 CEST 2026