| Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod [message #1778 is a reply to message #1776] |
Mon, 30 April 2018 14:31   |
Thomas Nygreen JBD
Messages: 68
Registered: February 2017
|
Member |
|
|
Christian Rößiger wrote on Sun, 29 April 2018 22:14
- According to railML-Wiki the attributes startDate / endDate are used
to limit the validity of a <operatingPeriod> compared to its
<timetablePeriod>, i.e. if startDate / endDate is used for a
<operatingPeriod>, a suitable <timetablePeriod> should also be given for
this <operatingPeriod>.
This is noted as a requirement on the wiki page for timetablePeriod[1]:
A railML file may but needs not necessarily to have a timetable period. A railML file may also have more than one timetable period but each train part (and therefore also each train) can refer to only one timetable period.
railML files without timetable period do either not have an element <timetablePeriod> at all or only elements <timetablePeriod> without startDate and endDate. If there is no timetable period defined the elements <operatingPeriod> must also not have attributes startDate, endDate and bitMask and must also not have sub-elements specialService.
startDate and endDate may be used together only, so there are no "open" periods allowed. The numerical difference of the attributes startDate and endDate defines the length of the attribute bitMask of the elements <operatingPeriod> (= startDate - endDate + 1).
[1] https://wiki.railml.org/index.php?title=TT:timetablePeriod
Best regards
Thomas Nygreen
Best regards,
Thomas Nygreen
Railway capacity engineer
Jernbanedirektoratet
|
|
|
|
Members
Search
Help
Login
Home
