Service Calendar Frame

In this chapter:

• ServiceCalendarFrame
• AvailabilityCondition
• ServiceCalendar
• DayType
• Timeband
• DayTypeAssignment

ServiceCalendarFrame

→ Glossary definition

Purpose

Groups calendar definitions that describe when services operate. We do this with AvailabilityConditions stored in this frame. We also have DayTypes and DayTypeAssignments for the holidays.

See the following class diagram for the most important objects of the ServiceCalendarFrame and their relationships to the other frames.

classDiagram
    %% Styles
    classDef frame fill:#FFF8E1,stroke:#FFB300;
    classDef contained fill:#E8F4FF,stroke:#1E90FF;
    classDef external fill:#F6F6F6,stroke:#AAAAAA;

    %% Frame
    class ServiceCalendarFrame {
        - validityConditions : AvailabilityCondition[]
    }
    class ServiceCalendarFrame frame

    %% Contained elements
    class AvailabilityCondition {
        FromDate
        ToDate
        ValidDayBits
    }

    class DayType {

    }

    class DayTypeAssignment {
    }


    class ServiceCalendar {

    }
    class Timeband {

    }

    %% External elements (not in the frame)
    class ServiceJourney {
        
    }

    class CheckConstraint {
    }

    class FacilitySet {
    }

    class StopAssignment {
    }

    class NoticeAssignment {
         }

    %% Containment relations (only contained elements)
    ServiceCalendarFrame "1" o-- "0..*" AvailabilityCondition : contains
    ServiceCalendarFrame "1" o-- "0..*" DayType : contains
    ServiceCalendarFrame "1" o-- "0..*" DayTypeAssignment : contains
    ServiceCalendarFrame "1" o-- "0..*" ServiceCalendar : contains
    ServiceCalendarFrame "1" o-- "0..*" Timeband : contains

    %% Usage relations from external elements to AvailabilityCondition
    ServiceJourney ..> AvailabilityCondition : uses
    CheckConstraint ..> AvailabilityCondition : uses
    FacilitySet ..> AvailabilityCondition : uses
    StopAssignment ..> AvailabilityCondition : uses
    NoticeAssignment ..> AvailabilityCondition : uses

    %% Other internal links
    DayTypeAssignment --> DayType : assigns

Figure: Elements of ServiceCalendar and elements with AvailabilityCondition

Table

A minimal ServiceCalendarFrame must be present in all timetable files.

Table: ServiceCalendarFrame

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<ServiceCalendarFrame id="ch:1:ServiceCalendarFrame" version="1">
  <!-- A minimal ServiceCalendarFrame must be present in all timetable files. -->
  <validityConditions>
    <AvailabilityCondition id="ch:1:AvailabilityCondition:b7" version="1">
      <!-- Our main mechanism for validity and operating days -->
    </AvailabilityCondition>
  </validityConditions>
  <ServiceCalendar id="ch:1:ServiceCalendar:j23" version="1">
    <!-- We only have one ServiceCalendar for the whole timetable year. It is not referenced. -->
  </ServiceCalendar>
  <dayTypes>
    <DayType id="ch:1:DayType:ycy10_1" version="1">
      <!-- Used for holidays only -->
    </DayType>
  </dayTypes>
  <timebands>
    <Timeband id="ch:1:Timeband:1140:1260" version="1">
      <!-- Mainly used for frequency-based lines. -->
    </Timeband>
  </timebands>
  <dayTypeAssignments>
    <DayTypeAssignment id="none" version="not">
      <!-- Used for holidays only -->
      <OperatingPeriodRef ref="generated" version="1"/>
      <DayTypeRef ref="ch:1:DayType:ycy10_1" version="1"/>
    </DayTypeAssignment>
  </dayTypeAssignments>
</ServiceCalendarFrame>

→ Template

Usage Notes

• Note that AvailabilityConditions can be combined and ANDed (all the conditions must be fulfilled at the same time). Allowed elements to specify constraints are FromDate/ ToDate, ValidDayBits, and timebands.

AvailabilityCondition

→ Glossary definition

Purpose

Temporal availability in terms of Dates, Timebands, ValidDayBits.

Table

Table: AvailabilityCondition

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<AvailabilityCondition id="generated" version="1">
  <FromDate>2026-05-17T00:00:00Z
    <!-- Is equal to the start date of the timetable year or, more generally, the period in which the ValidDayBits apply. -->
  </FromDate>
  <ToDate>2026-05-17T23:59:59Z
    <!-- Is equal to the end date of the timetable year or, more generally, the period in which the ValidDayBits apply. -->
  </ToDate>
  <ValidDayBits>01010010111</ValidDayBits>
  <timebands>
    <!-- Can also be referenced -->
    <Timeband id="ch:1:Timeband:4937" version="1">
      <StartTime>06:00:00</StartTime>
      <EndTime>06:20:00</EndTime>
    </Timeband>
    <TimebandRef ref="ch:1:Timeband:4937-2" version="1"/>
  </timebands>
</AvailabilityCondition>

→ Template

Usage Notes

• Examples of use of AvailabilityCondition include ServiceJourney, TemplateServiceJourney, facilities.
• AvailabilityCondition replaces OperatingDay and OperatingPeriod. Whenever a reference to a VP (“Verkehrsperiode” or “operating period” in english) is needed, we use an AvailabilityConditionRef:
• The referenced AvailabilityConditions are centrally stored in the ServiceCalendarFrame.
• The element ValidDayBits directly indicates the days on which some service is provided or not. They are similar to the HRDF bitfields.
• ValidDayBits is required whenever the AvailabilityCondition is of temporal nature (more often than not). Examples include:
  • ServiceJourney
  • NoticeAssignment
  • ServiceFacilitySet
  • ServiceJourneyInterchange
• AvailabilityConditions can be combined and ANDed (all the conditions must be fulfilled at the same time). Allowed elements to specify constraints are FromDate/ToDate, ValidDayBits, and timebands — none of these is mandatory on its own; an AvailabilityCondition may consist of only one of them (e.g. only FromDate/ToDate for “summer only”, only timebands for “school holiday period”, or only ValidDayBits for “Sundays only”). However, we don’t do this in our profile. There is always exactly one AvailabilityCondition per element.
• Hint: The frames TimetableFrame, ServiceFrame and ServiceCalendarFrame and their elements must have the same validity.
• @id does not need to be kept stable between exports.

ServiceCalendar

→ Glossary definition

Purpose

Long-term planning uses calendar days that are classified as specific DayTypes (example: weekday in school holidays). In the general NeTEx model, a ServiceCalendar defines a mapping between DayTypes and OperatingDays; in the Swiss profile, this mapping via OperatingDays is not used — ServiceCalendar serves only as a container for DayTypes and DayTypeAssignments, defining a mapping of DayTypes to dates.

Table

Table: ServiceCalendar

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<ServiceCalendar id="ch:1:ServiceCalendar:j23" version="1">
  <Name>Fahrplan 2018
    <!-- timetable year -->
  </Name>
  <FromDate>2017-12-10
    <!-- Beginning of timetable year -->
  </FromDate>
  <ToDate>2018-12-08
    <!-- End of timetable year -->
  </ToDate>
</ServiceCalendar>

→ Template

Usage Note

• @id should to be kept stable between exports.

DayType

→ Glossary definition

Purpose

A classification of days on which a specific set of transport services operates (e.g., Weekdays, Saturdays, Public Holidays). The DayTypes of the Swiss profile represent national holidays.

Table

In Switzerland only used for holidays and the like

Table: DayType

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<DayType id="ch:1:DayType:Bundesfeier" version="1">
  <!-- In Switzerland only used for holidays and the like -->
  <Name lang="de">Bundesfeier
    <!-- German or default text -->
    <Text lang="it">Festa nazionale
      <!-- Italian -->
    </Text>
    <Text lang="fr">Fête nationale
      <!-- French -->
    </Text>
    <Text lang="en">National Day
      <!-- English -->
    </Text>
  </Name>
  <properties>
    <PropertyOfDay>
      <!-- Holidays only -->
      <HolidayTypes>NationalHoliday</HolidayTypes>
      <DayEvent>normalDay</DayEvent>
    </PropertyOfDay>
  </properties>
</DayType>

→ Template

Usage Note

• @id needs to be kept stable between exports.
• As we only use DayType for holidays we have strict restrictions on PropertyOfDay: HolidayTypes is only nationalHoliday and DayEvent only anyDay or normalDay.

Timeband

→ Glossary definition

Purpose

A period of time within a day, usually defined by a start and end time.

Table

Table: Timeband

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<Timeband id="ch:1:Timeband:4937" version="1">
  <StartTime>06:00:00
    <!-- Local time (not Zulu), i.e., without “Z” or “hh:mm:ss” suffix. Seconds are not used. -->
  </StartTime>
  <EndTime>06:01:00
    <!-- Local time (not Zulu), i.e., without “Z” or “hh:mm:ss” suffix. Seconds are not used. -->
  </EndTime>
</Timeband>

→ Template

Usage Notes

• Currently Timeband is used in RG 1.0 for InterchangeRuleTimings, later also used for the opening hours in StopPlace models.
• @id should be kept stable between exports.

DayTypeAssignment

→ Glossary definition

Purpose

Assignment of a date to DayType. The DayTypes of the Swiss profile represent national holidays.

Table

We currently use DayType to store the national holidays.

Table: DayTypeAssignment

→ General NeTEx definition

Example

<?xml version="1.0" encoding="UTF-8"?>
<DayTypeAssignment id="BundesfeierAssignment" version="1">
  <!-- We currently use DayType to store the national holidays. -->
  <Date>2023-08-01</Date>
  <DayTypeRef ref="ch:1:DayType:Bundesfeier" version="1"/>
</DayTypeAssignment>

→ Template

Usage Notes

• We currently use DayTypeAssignment only for the national holidays.
• @id should be kept stable between exports.