Content
Simplified example
This document describes a simplified example of specifying tariff zone / tariff per Line and / or ServiceJourney using a key-value pair for tariff code.
Note that in the example, included in the XML file added to GitHub (see below), is only designed to illustrate this concept and therefore lacks a number of data objects and references required to be valid data submission under NeTEx NORWEGIAN PROFILE..
Routepattern
Structured in the same way as normal submission by Line, see NeTEx sample-directory (i arbeid).
Link
The entire XML sample file is located on the project's GitHub repository below https://github.com/entur/profile-norway-examples/blob/master/netex/fares/tariff-code.xml
PublicationDelivery
Structured in the same way as normal submission by Line, see NeTEx sample-directory (i arbeid).
Service Frame
Line
To define a tariff zone/ tariff per Line, this is entered with a keyList containing a KeyValue pair:
<Line version="1" id="RUT:Line:1"> <keyList> <KeyValue> <Key>Tariffkode</Key> <Value>Dagtakst</Value> </KeyValue> </keyList> <Name>Line-name</Name> <TransportMode>bus</TransportMode> <TransportSubmode> <BusSubmode>localBus</BusSubmode> </TransportSubmode> [...] </Line>
Timetable Frame
ServiceJourney
To define a tariff zone/ tariff per ServiceJourney (individual departure), this is entered accordingly with a keyList containing a KeyValue pair for each affected ServiceJourney:
<ServiceJourney version="1" id="UNI:ServiceJourney:1"> <keyList> <KeyValue> <Key>Tariffkode</Key> <Value>Nattakst</Value> </KeyValue> </keyList> [...] <DepartureTime>00:00:00</DepartureTime> <passingTimes> <TimetabledPassingTime version="1" id="RUT:TimetabledPassingTime:1"> <ArrivalTime>00:00:00</ArrivalTime> </TimetabledPassingTime> </passingTimes> </ServiceJourney>