Home » railML newsgroups » railml.interlocking » Definition of Emergency Stop Area for railML 3.3
Re: Definition of Emergency Stop Area for railML 3.3 [message #3167 is a reply to message #3140] Mon, 20 November 2023 06:37 Go to previous messageGo to previous message
Jörg von Lingen is currently offline  Jörg von Lingen
Messages: 87
Registered: March 2016
Member
Thanks Heidrun for this post.
The definition of borders of an ESA will come from operational rules of the infrastructure manager.

When considering only IL domain for definition of ESA one would always need some kind of track asset (signal, detection point etc.) as border elements. Otherwise it might be conceivable to define special border elements in IS which are then referred to.

As proposed such ESA can use a similar definition as for WorkZone or LocalOperationArea. However, for the modelling in railML3.3 it needs to be discussed before what is needed in addition to border elements.
1) isLimitedBy = reference to border elements
2) trackAssetInArea = references to any track assets inside (optional/mandatory)?
3) any track asset states?
4) any additional information, e.g. validity?


Dr.-Ing. Jörg von Lingen - Interlocking scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 351 87759 40; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Previous Topic: Switch/Derailer/Crossing in Overlap requires a position
Next Topic: [railml3] Signal types and functions
Goto Forum:
  

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

Current Time: Mon May 13 22:40:03 CEST 2024