Home » railML newsgroups » railML.infrastructure » [railML3] Micro - Meso - Macro
[railML3] Micro - Meso - Macro [message #1677] Mon, 04 December 2017 14:30 Go to previous message
christian.rahmig is currently offline  christian.rahmig
Messages: 472
Registered: January 2016
Senior Member
Dear railML community members,

When talking about railML v3 the possibility to define railway network
topology on several levels plays a key role in the discussion.

A central question, however, has not yet been completely answered:
Which railway infrastructure elements are considered to be the correct
"border elements" at each topology level?

A relevant example for illustration:
A station is an <operationalPoint> and it can be demarcated by the
location of the station entrance signals. If aggregated at mesoscopic
level, one <netElement> shall reference all microscopic topology
elements covered by the <operationalPoint>. Is this demarcation
generally accepted among all of you?

Any comments are highly appreciated...

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
 
Read Message
Read Message
Previous Topic: [railML3]: openend and Macroscopic nodes
Next Topic: SI units in railML 3.x
Goto Forum:
  


Current Time: Mon Oct 14 12:44:33 CEST 2024