Versions Compared

Old Version 10

changes.mady.by.user Dick Zetterberg

Saved on

compared with

New Version Current

changes.mady.by.user Kevin Lindgren

Saved on

Key

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

...

NeTEx - ServiceJourney.KeyValue.productCode

vehicleNumbers

The vehicleNumber should be the published train number when possible. For buses without unique id:s use the line number. If the bus needs a unique published id, then use that value. In Samtrafiken’s NeTEx dataset, the value is (almost) always found in the ServiceJourney.PublicCode element.

...

Buses and other traffic: NeTEx - ServiceJourney.PublicCode

Info

There is an exception for this, and that is for trains that change their train numbers during their journey. In those cases it must be taken into consideration that the train number will be different depending on the departure stop of the TripSpecification.
For these trains the vehicleNumber should be the train number that is advertised at the stop of the departure.
In Samtrafiken’s NeTEx dataset, trains that change their train numbers during their journey is expressed as a single ServiceJourney with multiple JourneyParts that refer to TrainNumber-elements with different ForAdvertisment values. The corresponding ForAdvertisment value from these JourneyParts should be used as the vehicleNumber, in this exceptional case.

carriers

In the Samtrafiken ACCESS API, the carrier IDs are used according to the codelist urn:x_swe:carrier:nnn, where nnn is the carrier ID.

...