Opened 6 years ago

Last modified 4 years ago

#25 new enhancement

Generate human readable operating period phrases (de: Erzeugung leicht verständlicher Verkehrstageformulierungen)

Reported by: susanne.wunsch Owned by:
Priority: normal Component: Tabular TT Viewer
Version: 2.x Keywords:

Description (last modified by susanne.wunsch)

There are multiple kinds of information about operating periods available in the railML files:

  1. operatingPeriod/@timetablePeriodRef
  2. operatingPeriod/@bitMask
  3. operatingPeriod/@startDate and operatingPeriod/@endDate
  4. operatingDay/@operatingCode
  5. operatingDay/@operatingCode and operatingDay/@startDate and operatingDay/@endDate
  6. operatingDayDeviance/@operatingCode and operatingDayDeviance/@holidayOffset
  7. operatingDayDeviance/@operatingCode and operatingDayDeviance/@holidayOffset and operatingDayDeviance/@ranking
  8. specialService/@type and specialService/@singleDate
  9. specialService/@type and specialService/@startDate and specialService/@endDate

What to do with this amount of information? A nice human readable phrase may be deduced, but nevertheless it will possibly not fulfill everyones expectations.

Maybe it can be reduced with railML3 without restricting the possible operating periods.

What to do with specialService/@startTime and specialService/@endTime in operating periods? What is the use case described in railML-Ticket 31 (

Why is operatingPeriod/@dayOffset explained at the railML Wiki ( but not implemented - means meanwhile deleted (

See also #9 for the basic behaviour

Change History (4)

comment:1 Changed 6 years ago by susanne.wunsch

  • Description modified (diff)

comment:2 Changed 6 years ago by susanne.wunsch

  • Description modified (diff)

comment:3 Changed 6 years ago by susanne.wunsch

See also #36 for considered functionality for version 1.0.

comment:4 Changed 4 years ago by birgit.jaekel

  • Version changed from 1.1 to 2.x
Note: See TracTickets for help on using tickets.