| Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod [message #1845 is a reply to message #1776] |
Mon, 18 June 2018 13:42   |
christian.rahmig
Messages: 436
Registered: January 2016
|
Senior Member |
|
|
Hello Christian,
may I briefly summarize your findings in an updated version of the example:
<infrastructure ...>
<track ...>
<states>
<state disabled="true" operatingPeriodRef="opp01"
startTime="22:00:00" endTime="06:00:00" endDayOffset="1"/>
</states>
...
</track>
</infrastructure>
<timetable ...>
<timetablePeriods>
<timetablePeriod id="ttp01" startDate="2017-12-15"
endDate="2018-12-14"/>
</timetablePeriods>
<operatingPeriods>
<operatingPeriod id="opp01" startDate="2018-04-28"
endDate="2018-04-29" bitmask="0000011" timetablePeriodRef="ttp01"/>
</operatingPeriods>
</timetable>
Is that correct?
Best regards
--
Christian Rahmig - Infrastructure scheme coordinator
railML.org (Registry of Associations: VR 5750)
Phone Coordinator: +49 173 2714509; railML.org: +49 351 47582911
Altplauen 19h; 01187 Dresden; Germany www.railml.org
Am 29.04.2018 um 22:14 schrieb Christian Rößiger:
> [...]
> - The attributes startDate and endDate only define the validity period
> of the <operatingPeriod>, i.e. for which period the <operatingPeriod>
> contains data. The actual days on which an activity takes place (in your
> example the non-availability) must be defined using the bitMask attribut
> and / or the <operatingDay> / <specialService> elements.
>
> - 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>.
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
