ServiceCalendar
A SERVICE CALENDAR groups the calendar related ENTITies and provides in particular a set of assignments of OPERATING DAYs to DAY TYPEs.
ServiceCalendar – XML Element
Classification | Name | Type | Cardinality | Description |
::> | ::> | DataManagedObject | ::> | SERVICE CALENDAR inherits from DATA MANAGED OBJECT. |
«PK» | id | ServiceCalendarIdType | 1:1 | Identifier of SERVICE CALENDAR. |
| Name | MultilingualString | 0:1 | Name of SERVICE CALENDAR. |
| ShortName | MultilingualString | 0:1 | Short name of SERVICE CALENDAR. Currently not in use in the Austrian NeTEx Profile |
| FromDate | xsd:date | 0:1 | Inclusive start date for validity of SERVICE CALENDAR. |
| ToDate | xsd:date | 0:1 | Inclusive end date for validity of SERVICE CALENDAR. |
| EarliestTime | xsd:time | 0:1 | Earliest time that days start SERVICE CALENDAR. Default to use if not specified on individual OPERATING DAY. Currently not in use in the Austrian NeTEx Profile |
| DayLength | xsd:duration | 0:1 | Day length used with earliest time to work out end of day. Default to use if not specified on individual OPERATING DAY. Currently not in use in the Austrian NeTEx Profile |
«cntd» | dayTypes | DayType | 0:* | DAY TYPEs in SERVICE CALENDAR. Currently not in use in the Austrian NeTEx Profile |
«cntd» | timebands | Timeband | 0:* | TIMEBANDs in SERVICE CALENDAR. IN EPIP, each DAY TYPE must declare its own timeband Currently not in use in the Austrian NeTEx Profile |
«cntd» | operatingDays | OperatingDay | 0:* | OPERATING DAYs in SERVICE CALENDAR. Currently not in use in the Austrian NeTEx Profile |
«cntd» | operatingPeriods | OperatingPeriod | 0:* | OPERATING PERIODs in SERVICE CALENDAR. Currently not in use in the Austrian NeTEx Profile |
«cntd» | dayTypeAssignments | DayTypeAssignment | 0:* | DAY TYPE ASSIGNMENTs in SERVICE CALENDAR. Currently not in use in the Austrian NeTEx Profile |
Example from the Austrian NeTEx Profile:
OperatingDay (Subcomponent of ServiceCalendar)
An OPERATING DAY is in most cases similar to a calendar day (i.e. an indidual date in the calendar, such as ‘1st April 2019’), but may differ in its start and end times.
An assignment process, allocating DAY TYPEs to an OPERATING DAY, allows selection of the most appropriate schedule to meet the expected demand and to face the traffic conditions. This leads to an operational plan for every OPERATING DAY. The plan is completed by the assignment of physical resources to the theoretical work and amended as necessary to deal with unexpected circumstances (such operational measures are outside of the scope of EPIP).
OperatingDay – XML Element
Classification | Name | Type | Cardinality | Description |
::> | ::> | DataManagedObject | ::> | OPERATING DAY inherits from DATA MANAGED OBJECT. |
«PK» | id | OperatingDayIdType | 1:1 | Identifier of OPERATING DAY. |
| CalendarDate | xsd:date | 1:1 | Calendar date of OPERATING DAY. |
«FK» | ServiceCalendarRef | CalendarRef | 0:1 | SERVICE CALENDAR to which OPERATING DAY belongs. |
| Name | MultilingualString | 0:1 | Name of OPERATING DAY. |
| ShortName | MultilingualString | 0:1 | Short Name of DAY TYPE. |
«AK» | DayNumber | xsd:integer | 1:1 | Day Number if different from @id. |
«AK» | PrivateCode | PrivateCode | 0:1 | SERVICE CALENDAR to which DAY TYPE belongs. |
| EarliestTime | xsd:time | 1:1 | Start time of OPERATING DAY. |
| DayLength | xsd:duration | 1:1 | Length of OPERATING DAY. |
Currently this XML Element is not in use in the Austrian NeTEx Profile