Forum: railML.infrastructure » Station borders

Home » railML newsgroups » railML.infrastructure » Station borders

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Station borders [message #2347 is a reply to message #2338]

Wed, 26 February 2020 11:39

christian.rahmig
Messages: 436
Registered: January 2016

Senior Member

Thomas Nygreen wrote on Fri, 21 February 2020 16:16

Dear Christian,
Dear all,

An <operationalPoint> can already be placed using either <spotLocation> (on a macroscopic level), <linearLocation> (if only one track) or <areaLocation> (on one or more tracks). So I'm not sure that I see the need for more ways to do it.

Best,
Thomas

Dear Thomas,

you are right, but in fact, all three options for modelling station borders are already possible. Therefore, it is important to find the best practice, in order to limit flexibility of the model and thus increase compatibility of railML interfaces. So, option 2 is your preferred solution?

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]

		Station borders By: christian.rahmig on Fri, 24 January 2020 17:31
		Re: Station borders By: Thomas Nygreen on Fri, 21 February 2020 16:16
		Re: Station borders By: christian.rahmig on Wed, 26 February 2020 11:39
		Re: Station borders By: Thomas Nygreen on Wed, 04 March 2020 16:37
		Re: Station borders By: Dirk Bräuer on Mon, 09 March 2020 22:01
		Re: [railML3] Station borders By: christian.rahmig on Fri, 13 March 2020 12:23
		Re: [railML3] Station borders By: Fabrizio Cosso on Fri, 20 March 2020 18:00
		Re: Station borders By: Thomas Langkamm on Mon, 24 February 2020 10:39

Previous Topic:	[railML 3.1] level crossing parameters
Next Topic:	Ontology for RailML 3.1.

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Apr 29 09:10:28 CEST 2024