| Re: [railML2] Adding a new element informationArea to ocp [message #2819 is a reply to message #2812] |
Fri, 20 August 2021 17:35   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Dear Torben,
Torben Brand wrote on Thu, 19 August 2021 12:16
- the sub element <localArea> is missing (as a redesign of in option 1 proposed @type="local")
I updated the proposed railML 2.5 solution documented in Trac ticket #393 [1] following the suggestion by Thomas: a <controller> shall have a repeatable, but optional child element <localOperationArea>, which references a <genericArea> with the attribute @ref. This approach models an area that is locally controlled.
Torben Brand wrote on Thu, 19 August 2021 12:16
- a misunderstanding that working zones (#395) are the same as working areas and the attributes for working zones have been placed under workingArea. #395 should be as proposed but with a new sub elements <workingZone>
Following the latest discussion, I want to clarify: a <workZone> is some area considered for working, which is integrated into the interlocking system. Consequently, it is modelled as child element of <controller>, providing a reference to a <genericArea>. On the other side, there exist "track sections with impairments" affecting railway operation, e.g. by extending train running times. The reason for impairments can be construction sites or other reasons. I summarized this approach in modelling <impairmentSection> as optional, but repeatable child element of <track>, which references a <genericArea>.
If anyone has any comments on this updated implementation, please let us know ASAP.
[1] https://trac.railml.org/ticket/393
BR
Christian
Christian Rahmig – Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Altplauen 19h; 01187 Dresden; Germany www.railML.org
|
|
|
|
Members
Search
Help
Login
Home
