Versions Compared

Old Version 3

changes.mady.by.user Hans Inge Letnes

Saved on

compared with

New Version 4

changes.mady.by.user Johan Wiklund (Unlicensed)

Saved on

Key

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

Innhold

Table of Contents

Line 109, Oslo

Info

For a description of route data according Accordning to the Norwegian NeTEx-profile, one separate file should be sent per Line.

...

each Line must be defined in its own separate XML-file.

Route pattern 

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

  • Helsfyr T
  • Brynseng T
  • Høyenhall T
  • Manglerud T
  • Ryen T
  • Holtet stasjon

The departure runs three times There are three departure each morning, but at different times for differ between weekdays , Saturdays and Sundaysweekends. A Line with one route is modeled accordingly as in to the example for Simple route for bus with rhytmbased departure, but Timetable is modeled as an explicit ServiceJourney for each departure.

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

PublicationDelivery

Info

Service Frame

ServiceJourney

Structuring of Passenger transport setup for a given day type is specified in this example as a set of ServiceJourney ServiceJourneys (under vehicleJourneys), which individually describes describe one trip each trip. Although the pattern could have been defines defined as a rhytm-based departure, ref. Simple route - Bus bus (rhytmbased) (Copy), it is due to few departures and different departure times on those different days easier , 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 an departure that runs operating on both weekdays and SaurdaysSaturdays:

Code Block
languagexml
<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>

...