Home » railML newsgroups » railML.infrastructure » Station borders
Re: [railML3] Station borders [message #2396 is a reply to message #2385] Fri, 13 March 2020 12:23 Go to previous messageGo to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 436
Registered: January 2016
Senior Member
Dear Dirk,

Dirk Bräuer wrote on Mon, 09 March 2020 22:01
All together: When defining station borders, always allow a definition which kind of border type is meant and allow definitions depending on direction.

Thank you for your feedback. Following your requirement for modelling station borders option 1 (a dedicated <border> element) seems to be the only solution. Are there any other opinions from the community?

I also appreciate the idea of Thomas to distinguish between different purposes. In particular,
* <border> elements can be used to locate a (direction dependent and type specific) station border
* <operationalPoint><areaLocation> may be used to define the (static) station area.

What does the community think about this modelling approach for railML 3.x? Any comments are very much welcome...

Best regards
Christian

Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 3.1] level crossing parameters
Next Topic: Ontology for RailML 3.1.
Goto Forum:
  

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

Current Time: Mon Apr 29 02:23:45 CEST 2024