Innhold
| Table of Contents |
|---|
Line 109, Oslo
| Infonote |
|---|
Accordning According to the Norwegian NeTEx-profile, each Line must be defined in its own separate XML-file. |
Route pattern
Line 109 is a 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
There are three departure departures each morning, but times differ between weekdays and weekends. A Line with one route is modeled modelled accordingly to the example for Simple route for bus line with rhytmbased rhythm-based departures, but Timetable is modeled modelled as an explicit ServiceJourney for each departure.
Link
The entire XML sample file is located 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
| Info |
|---|
Because some data structures relevant to this example have already been covered in Simple route - Bus ( rhytmbased (Copy)and Projection (Copy), parts of the relevant structure have been omitted, and this example covers only the ServiceJourney structure. |
Service Frame
ServiceJourney
Structuring of Passenger transport for a given day type is specified in this example as a set of ServiceJourneys (under vehicleJourneys), which describe one trip each. Although the pattern could have been defined as a rhytmrhythm-based departure, ref. Simple route - bus (rhytmbased)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 an a departure operating on weekdays and Saturdays:
...