Home » railML newsgroups » railML.infrastructure » [railML3] Positioning approach (How to define unambiguous positions with railML 3.x)
Re: [railML3] Positioning approach [message #3159 is a reply to message #3156] Mon, 06 November 2023 19:31 Go to previous messageGo to previous message
Thomas Nygreen is currently offline  Thomas Nygreen
Messages: 75
Registered: March 2008
Member
Dear Christian,

The linearCoordinate and geometricCoordinate children of linearLocation should be removed to stay consistent with the use that you are describing. And I would prefer either a clear documentation of when to use linearLocation versus areaLocation, or removing the latter. Should a level/over/underCrossing that crosses a multitrack line have one linearLocation for each track or an areaLocation for all tracks? Is a switch a linear or an area element?

Best regards,
Thomas


Thomas Nygreen – Common Schema Coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [raillML3] Revision of rulebook
Next Topic: [railML2] Single and double derailer
Goto Forum:
  


Current Time: Wed Oct 02 09:44:10 CEST 2024