Home » railML newsgroups » railML.infrastructure » railML 2.3 infrastructure extension proposal operational properties of an OCP (railML 2.3 infrastructure extension proposal operational properties of an OCP)
Re: railML 2.3 infrastructure extension proposal operational properties of an OCP [message #2672 is a reply to message #1942] Thu, 25 February 2021 09:59 Go to previous messageGo to previous message
Torben Brand is currently offline  Torben Brand
Messages: 158
Registered: March 2016
Senior Member
I would like to come back to the proposed attribute @simultaneousEntry in the initial posting in this thread and explained further in reply postings in the thread. It is now used in railML2.4nor extension and defined as: Enumerates the different Norwegian infrastructure design and operational rule types of simultaneous entry into a station. See Norwegian technical design rules for definitions of the 4 types that have simultaneous entry. In addition to the two types "none" and "partial".
https://trv.banenor.no/wiki/Signal/Prosjektering/Forriglings utrustning#Samtidige_togbevegelser.

The Norwegian railway sector proposes to introduce the extension into railML2.5 under <propOperational>. For a more international and generic clean approach I suggest to split the existing extension attribute @simultaneousEntry into two attributes @hasSimultaneousEntry with the enumeration values: "yes","no" and "partial". The national rule specific type for stations with simultaneous entry can be defined with @simultaneousEntryruleCode.

What does the community think?

[Updated on: Thu, 25 February 2021 09:59]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: [railML 2.5] state
Next Topic: [railML2] Basic speed profile
Goto Forum:
  


Current Time: Sat Apr 27 09:17:32 CEST 2024