Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

InnholdContent

Table of Contents

...

Calendar-

...

Definisjon av dager, dagtyper, operasjonelle perioder og andre kalendar-objekter, samt tilknytninger mellom disse, gjøres i en Service Calendar. Disse definisjonene brukes videre i oppsett av (hovedsakelig) Timetable, for å spesifisere når en Line betjenes.

Lenke

...

objects

Service Calendar defines days, dayType, operational periods and other calendar items, as well as the connections between them. These definitions are further used (mainly) in the Timetable to specify when a Line operates.

The XML example in it its entirety can be found in the GitHub repository: https://github.com/entur/profile-norway-examples/blob/master/netex/schedule/ServiceCalendar-example.xml

Elementer

Under følger en nærmere beskrivelse av de viktigste elementene ved modellering av kalender-objekt.

Info

Merk at dette kun er en forenklet oppbygning av NeTEx-XML. I henhold til norsk profil  det være med flere elementer for at filen skal være gyldig for dataoverføring til holdeplassregisteret.

Se eksempel for enkelt stoppested, buss for XML som inneholder andre nødvendige elementer for å være gyldig i henhold til profilen.

PublicationDelivery

Alle XML-filer etter norsk NeTEx-profil skal være av type PublicationDelivery som inneholder relevante Frames. (Se GitHub for komplett eksempel.)

Info

Beskrivelse av dummy ServiceFrame og TimetableFrame i eksempelet er kun gjort for å indikere en komplett PublicationDelivery.

ServiceCalendarFrame

...

Elements

Below is a more detailed description of the most important elements of modelling a calendar object.

Note that this is only a simplified example of NeTEx XML.

PublicationDelivery

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

Info

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

ServiceCalendarFrame

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 the dataset, it is recommended to define these directly in ServiceCalendarFrame.

ServiceCalendarFrame
Code Block
title
languagexmlServiceCalendarFrame
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

Definisjon av type dag ved hjelp av hvilke ukedager dagtypen gjelder. Typen kan presiseres nærmere med ytterligere egenskaper, f.eks. ferie-type, hvis relevantDefining day type by means of weekdays.

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>

timebands

Timeband viser tidsangivelseshows time indication.

  • StartTime

    og EndTime eller Duration angir periodeDersom StartTime og EndTime er like, spesifiserer dette et bestemt klokkeslett. F.eks. når man angir et bestemt tidspunkt hver hele time (ifm. Rhythmical Journey) er dette indikert med konsekvent timeangivelse

    and EndTime or Duration specify the period span.

  • If StartTime and EndTime are equal it specifies a specific time. E.g. when specifying a repeating hourly departure (in Rhythmical Journey), this is indicated by a consistent 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>

operatingDays

Spesifisering av en operasjonsdag, evt. også start og lengde for en operasjonsdag. Kan knyttes til en dagtype v.h.a. 637370378.Specification of an operating day, possibly also the start and length of an operating day. Can be linked to a dayType , e.g. Kalender#dayTypeAssignments.

Code Block
languagexml
<operatingDays>
	<OperatingDay version="any" id="RUT:OperatingDay:default:1">
		<CalendarDate>2016-05-01</CalendarDate>
		<EarliestTime>10:10:00</EarliestTime>
		<DayLength>PT12H45M</DayLength>
	</OperatingDay>
	<OperatingDay version="any" id="RUT:od:default:2">
		<CalendarDate>2016-07-07</CalendarDate>
		<EarliestTime>11:11:00</EarliestTime>
		<DayLength>PT9H10M</DayLength>
	</OperatingDay>
</operatingDays>

operatingPeriods

Spesifisering av en operasjonsperiode, med basis i tidligere definerte start- og slutt-dagerSpecification of an operating period, based on previously defined start and end days.

Code Block
languagexml
<operatingPeriods>
	<OperatingPeriod version="any" id="RUT:op:default">
		<FromOperatingDayRef ref="RUT:OperatingDay:default:1"/>
		<ToOperatingDayRef ref="RUT:od:default:2"/>
	</OperatingPeriod>
</operatingPeriods>

dayTypeAssignments

Knytning av en dagtype til en spesifikk dato eller pre-definert OperatingDay/-Period for en gitt kalender, dvs. en dagtype vil være gyldig innenfor tidsrommet spesifisert av kalenderobjektet den tilknyttesAttaching a dayType to a specific date or pre-defined OperatingDay/Period for a given calendar, i.e. a dayType will be valid within the time period specified by the calendar object to which it is associated.

Code Block
languagexml
<dayTypeAssignments>
	[...]
	<DayTypeAssignment version="any" order="1" id="RUT:DayTypeAssignment:period">
		<OperatingPeriodRef ref="RUT:OperatingPeriod:default"/>
		<DayTypeRef version="any" ref="RUT:DayType:weekdays"/>
	</DayTypeAssignment>
</dayTypeAssignments>

...