Home » railML newsgroups » railML.infrastructure » Platform element location: is it really necessary? (How to specify a platform location in absence of mesoscopic/macroscopic description)
Platform element location: is it really necessary? [message #1999] Mon, 29 October 2018 12:17 Go to next message
Fabiana Diotallevi is currently offline  Fabiana Diotallevi
Messages: 21
Registered: October 2018
Junior Member
Dear all,
I was wondering if, in case of a single station representation, the mesoscopic/macroscopic description can be neglected, since there are no other lines or stations to link it to.

In particular, for what I see in the simpleExample documentation, the functionalInfrastructure element "Platform" has to be connected to a mesoscopic element (ne_a11), while the relative elements "PlatformEdge" are connected to microscopic elements (ne_a01 and ne_a02).

Do we really the need to specify the location of the Platform element?
Shouldn't the location of the "PlatformEdges" be enough for the determination of the Platform itself?

How can I model a "Platform" element if I don't have a mesoscopic element to refer it to?

Thanks in advance for your feedback,

Fabiana
Re: Platform element location: is it really necessary? [message #2001 is a reply to message #1999] Fri, 02 November 2018 16:09 Go to previous messageGo to next message
christian.rahmig is currently offline  christian.rahmig
Messages: 447
Registered: January 2016
Senior Member
Dear Fabiana,

Am 29.10.2018 um 12:17 schrieb Fabiana Diotallevi:
> [...]
> In particular, for what I see in the simpleExample
> documentation, the functionalInfrastructure element
> "Platform" has to be connected to a mesoscopic element
> (ne_a11), while the relative elements "PlatformEdge" are
> connected to microscopic elements (ne_a01 and ne_a02).
>
> Do we really the need to specify the location of the
> Platform element?
> Shouldn't the location of the "PlatformEdges" be enough for
> the determination of the Platform itself?
>
> How can I model a "Platform" element if I don't have a
> mesoscopic element to refer it to?

There is no need to have the <platform> element being located on meso or
macro level. You may have the <platform> element also located on a
microscopic level using an <areaLocation>. Even better: you do not have
to have a location for the <platform> element at all (there is no need
from schema syntax point of view). Therefore, you can proceed as you
already mentioned: locate the <platformEdge> elements on microscopic
level and have the <platform> element being indirectly located by its
referenced <platformEdge> elements.

Best regards
Christian

--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org


Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
Re: Platform element location: is it really necessary? [message #2003 is a reply to message #2001] Mon, 05 November 2018 15:10 Go to previous message
Fabiana Diotallevi is currently offline  Fabiana Diotallevi
Messages: 21
Registered: October 2018
Junior Member
Dear Christian,
thanks for your answer, now it's clear as crystal!

Hope to see you soon in Prague,
best regards,

Fabiana

Previous Topic: Infrastructure Visualization
Next Topic: NetElements vs. Tracks vs. TrainDetectionElements vs. TvdSections
Goto Forum:
  


Current Time: Mon Jul 22 16:48:03 CEST 2024