Home » railML newsgroups » railML.infrastructure » Mapping of availability periods of the infrastructure by TT:operatingPeriod
Re: Mapping of availability periods of the infrastructure by TT:operatingPeriod [message #1849 is a reply to message #1845] Tue, 19 June 2018 08:43 Go to previous messageGo to previous message
Christian Rößiger is currently offline  Christian Rößiger
Messages: 61
Registered: March 2015
Member
Hello Christian,

Am 18.06.2018 um 13:42 schrieb Christian Rahmig:
> <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?

Almost ;-) But: The length of the bitmask must correspond to the length
of the <timetablePeriod>, not that of the <operatingPeriod>.

See: https://wiki.railml.org/index.php?title=TT:operatingPeriod, section
"constraints", attribute "bitmask"

Many Greetings
Christian Rößiger

--
iRFP e. K. · Institut für Regional- und Fernverkehrsplanung
Hochschulstr. 45, 01069 Dresden
Tel. +49 351 4706819 · Fax. +49 351 4768190 · www.irfp.de
Registergericht: Amtsgericht Dresden, HRA 9347
 
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
Read Message
Read Message
Read Message
Previous Topic: etcsTrainCategory
Next Topic: Signal characteristics (de: Signaleigenschaften)
Goto Forum:
  


Current Time: Wed May 01 18:14:09 CEST 2024