Innhold

...

Line 109, Oslo

Rutemønster

...

Route pattern 

Line 109 is an early morning bus service between Helsfyr and Holtet, partly as a supplement for the metro. It operates on all weekdays serving the following stops:

• Helsfyr T

• Brynseng T

• Høyenhall T

• Manglerud T

• Ryen T

• Holtet stasjon

Avgangen kjøres tre ganger hver morgen, men til ulike tidspunkt for ukedager, lørdager og søndager. Line med én route er modellert tilsvarende som i eksempel Enkel rute for buss med rytmebasert avgang, men Timetable er derimot modellert som eksplisitte ServiceJourney for hver avgang.

Lenke

Hele XML eksempelfilen ligger på prosjektets GitHub-repository under There are three departures each morning, but times differ between weekdays and weekends. A Line with one route is modelled accordingly to the example for Simple bus line with rhythm-based departures, but Timetable is modelled as an explicit ServiceJourney for each departure.

Link

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

PublicationDelivery

Service Frame

ServiceJourney

Oppsett av passasjertransport for en gitt dagstype er i dette eksempelet spesifisert som et sett av ServiceJourneyStructuring of Passenger transport for a given day type is specified in this example as a set of ServiceJourneys (under vehicleJourneys),  som hver for seg beskriver den enkelte tur. Selv om mønsteret kunne vært definert som en rytmebasert avgang, ref. Enkel rute - Buss (rytmebasert avgang) (Copy), er det p.g.a. få avganger og ulike avgangstider de forskjellige dagene enklere å definere den enkelte avgang som en egen ServiceJourney.Eksempelet under viser en avgang som kjøres både ukedager og lørdagerwhich describe one trip each. Although the pattern could have been defined as a rhythm-based departure, ref. Simple rhythm based bus line, it may be easier to define each departure as a separate ServiceJourney. in cases where there are very few departures, or deviating journey patterns, or departure times.

The example below shows a departure operating on weekdays and Saturdays:

<ServiceJourney version="any" id="UNI:sj:109:CODE-0530">
	<DepartureTime>05:30:00</DepartureTime>
	<dayTypes>
		<DayTypeRef ref="UNI:dt:weekday"/>
		<DayTypeRef ref="UNI:dt:saturday"/>
	</dayTypes>
	<JourneyPatternRef ref="UNI:JourneyPattern:109"/>
	<!-- Optional: -->
	<LineRef ref="UNI:line:109"/>
	<passingTimes>
		<TimetabledPassingTime>
			<!-- Helsfyr T -->
			<StopPointInJourneyPatternRef version="any" ref="UNI:StopPointInJourneyPattern:helfyr_t"/>
			<DepartureTime>05:30:00</DepartureTime>
		</TimetabledPassingTime>
		<TimetabledPassingTime>
			<!-- Brynseng T -->
			<StopPointInJourneyPatternRef version="any" ref="UNI:StopPointInJourneyPattern:brynseng_t"/>
			<DepartureTime>05:32:00</DepartureTime>
		</TimetabledPassingTime>
		<TimetabledPassingTime>
			<!-- Høyenhall T -->
			<StopPointInJourneyPatternRef version="any" ref="UNI:StopPointInJourneyPattern:hoyenhall_t"/>
			<DepartureTime>05:33:00</DepartureTime>
		</TimetabledPassingTime>
		<TimetabledPassingTime>
			<!-- Manglerud T -->
			<StopPointInJourneyPatternRef version="any" ref="UNI:StopPointInJourneyPattern:manglerud_t"/>
			<DepartureTime>05:34:00</DepartureTime>
		</TimetabledPassingTime>
		<TimetabledPassingTime>
			<!-- Ryen T -->
			<StopPointInJourneyPatternRef version="any" ref="UNI:StopPointInJourneyPattern:ryen_t"/>
			<DepartureTime>05:35:00</DepartureTime>
		</TimetabledPassingTime>
		<TimetabledPassingTime>
			<!-- Holtet -->
			<StopPointInJourneyPatternRef version="any" ref="UNI:StopPointInJourneyPattern:holtet"/>
			<ArrivalTime>05:40:00</ArrivalTime>
		</TimetabledPassingTime>
	</passingTimes>
</ServiceJourney>

...