| [railML2] extension suggestion for the element <state> for working zones [message #2677] |
Mon, 08 March 2021 16:26  |
Torben Brand
Messages: 157
Registered: March 2016
|
Senior Member |
|
|
The element <state> is used amongst others for the description of certain characteristics of track and catenary works, collectively refered to as work zones. For track works use <track>/<states>/<state>. For catenary works use <electrificationChange>/<states>/<state>.
There are three items missing in railML2.4 for the UC for working zones:
- enumeration "restricted"
- ID of the working zone
- Additional running time that the working zone inflicts on trains passing through
These works may lead to trains not being able to operate, thus the construction site/ the relevant infrastructure is set to <state>@status=disabled. But the infrastructure works may also only restrict the train operations. Thus, we are missing an enumeration value between "operational" and "disabled". We suggest introducing the new enumeration value "restricted" for this purpose.
The working zone must be identified. Jernbanedirektoratet suggest to add an attribute @restrictionID of type xs:string for "Official reference code for the restriction".
Working zones are usually modelled in a macroscopic and not in a microscopic detailed way. Thus we suggest to add the value of the additional running time for all trains passing through the working zone if set to status="restricted". As the time is direction dependant we suggest to add a sub element <additionalRunningTime> containing:
@time of type xs:duration "Additional running time for trains passing through the restriction area"
@absDir "xs:enumeration "Direction of traffic that the additional time applies to. Possible values are "raising" (misspelling of "rising" inherited from railML2.2) and "falling" "
Working zones are amongst others displayed in the graphical timetable in Norway.
What does the community think about this UC and its solution suggestion?
|
|
|
|
Members
Search
Help
Login
Home
