Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Finpuss

Content

Table of Contents

Calendar-objects

Definition of Service Calendar defines days, daytypes, operational periods and other calendar items, as well as the connections between them , are done in a Service Calendar . These definitions are further used in the (mainly) in the Timetable setup to  to specify when a Line is operatedoperates.

The entire XML sample file is located on in the project's GitHub repository: https://github.com/entur/profile-norway-examples/blob/master/netex/schedule/ServiceCalendar-example.xml

...

Info

Note that this is only a simplified structure example of NeTEx XML. According to the Norwegian profile, there must be several elements for the file to be valid for data transfer to the stopplaceregister.

See example for simple stopplace, bus for XML containing other necessary items to be valid according to the profile.

PublicationDelivery

All XML files according to the Norwegian NeTEx profile should be of type PublicationDelivery containing relevant Frames. (See GitHub for complete example.)

Info

Description of the dummy ServiceFrame and TimetableFrame in the example is only made included to indicate a complete PublicationDelivery.

...

All calendar objects are defined in a ServiceCalendarFrame. It can be done in a ServiceCalendar object, but given that most components are often reused across timeplanerthe dataset, it is recommended to define these directly in ServiceCalendarFrame.

Code Block
languagexml
titleServiceCalendarFrame
collapsetrue
<ServiceCalendarFrame version="any" id="RUT:ServiceCalendarFrame:1">
	<ServiceCalendar version="any" id="RUT:ServiceCalendar">
		<Name>Ukedager<<Name>Weekdays</Name>
		<FromDate>2016<FromDate>2019-04-01</FromDate>
		<ToDate>2016<ToDate>2019-08-31</ToDate>
	</ServiceCalendar>
[...]

dayTypes

Definition of day type day by which weekdays the daytype DayType applies. The type can be further clarified with additional features, e.g. holiday type, if applicable.

Definisjon av type dag ved hjelp av hvilke ukedager dagtypen gjelder. Typen kan presiseres nærmere med ytterligere egenskaper, f.eks. ferie-type, hvis relevant. 

Status
colourYellow
titleconvoluted

Code Block
languagexml
<dayTypes>
	<DayType version="any" id="RUT:DayType:weekdays">
		<Name>Ukedager</Name>
		<properties>
			<PropertyOfDay>
				<DaysOfWeek>Monday Tuesday Wednesday Thursday Friday</DaysOfWeek>
			</PropertyOfDay>
		</properties>
	</DayType>
	[...]
</dayTypes>

...

Timeband shows time indication.

  • StartTime and EndTime or Duration specify periodand EndTime or Duration specify the period span.
  • If StartTime and EndTime are equal , this it specifies a specific time. EgE.g. When when specifying a specific time each hour repeating hourly departure (in Rhythmical Journey), this is indicated by a consistent hour time of "00".
Code Block
languagexml
<timebands>
	<Timeband version="any" id="RUT:Timeband:TM15">
		<!--Name>15 minutes past the hour</Name-->
		<StartTime>00:15:00</StartTime>
		<EndTime>00:15:00</EndTime>
	</Timeband>
</timebands>

...

Attaching a daytype to a specific date or pre-defined OperatingDay/Period for a given calendar, ie i.e. a daytype will be valid within the time period specified by the calendar object to which it is associated.

...