Skip to end of banner
Go to start of banner

Samtrafiken Noptis to GTFS-R mapping

Skip to end of metadata
  • Created by Former user, last modified on 2021-01-25
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

This page describes how Samtrafiken maps Noptis data to GTFS-realtime data. For a complete specification of the GTFS-realtime format, please see http://gtfs.org/reference/realtime/v1/.

Header

Feed metadata header.

GTFS-R

Value

header.gtfs_realtime_version

“2.0”

header.incrementality

FULL_DATASET

header.timestamp

UTC time in seconds of file creation. Example: 1611582680.

Alert

Filename: ServiceAlerts.txt and ServiceAlerts.pb.

GTFS-R

NOPTIS

id

DeviationMessageVersion.Id

alert.active_period.start

DeviationMessageVersion.PublishFromDateTime

alert.active_period.end

DeviationMessageVersion.PublishUpToDateTime

alert.header_text.translation.text

DeviationMessage.Content (UsageTypeShortName=HEADER)
OR
DeviationMessageVersion.PublicNote

alert.description_text.translation.text

DeviationMessage.Content (UsageTypeShortName=DETAILS)
OR
DeviationMessageVersion.PublicNote

alert.cause

UNKNOWN_CAUSE
OR
DeviationReasonStandardCategoryCode → alert.cause

  • MEDICAL → MEDICAL_EMERGENCY

  • POLICEDECISION → POLICE_ACTIVITY

  • ROADWORK → CONSTRUCTION

  • MAINTENANCE → MAINTENANCE

  • WEATHER → WEATHER

  • ACCIDENT → ACCIDENT

  • STRIKE → STRIKE

  • VEHICLEBREAKDOWN, TECHNICALFAILURE → TECHNICAL_PROBLEM

  • ELSE → OTHER_CAUSE

alert.informed_entity.route_id

Line.Gid

alert.informed_entity.stop_id

StopPoint.Gid
OR
StopArea.Gid

alert.informed_entity.agency_id

TransportAuhtority.Id

alert.informed_entity.trip.trip_id

VehicleJourney.Id

alert.informed_entity.trip.schedule_relationship

If a vehicle journey exists, then SCHEDULED, else field is not included.

Vehicle position

Filename: Vehiclepositions.txt and Vehiclepositions.pb.
Entity Position in the below table refers to a POSROI message.

GTFS-R

NOPTIS

id

Position.Nr

vehicle.trip.trip_id

VehicleJourney.Id

vehicle.trip.route_id

Line.Gid

vehicle.trip.direction_id

DirectionOfLine.DirectionCode → vehicle.trip.direction_id

  • EVEN → 0

  • ODD → 1

vehicle.trip.start_time

DatedVehicleJourney.TimetabledStartDateTime

vehicle.trip.start_date

DatedVehicleJourney.TimetabledStartDateTime

vehicle.trip.schedule_relationship

If vehicle journey exists, then SCHEDULED, else ADDED.

vehicle.position.latitude

Position.Northing

vehicle.position.longitude

Position.Easting

vehicle.position.bearing

Position.Heading

vehicle.position.speed

Position.Speed

vehicle.timestamp

Position.Timestamp

vehicle.vehicle.id

Position.Vehicle

Trip updates

Filename: TripUpdates.txt and TrupUpdates.pb.

GTFS-R

NOPTIS

id

DatedVehicleJourney.Id

trip_update.trip.trip_id

VehicleJourney.Id

trip_update.trip.start_date

DatedVehicleJourney.TimetabledStartDateTime

trip_update.trip.schedule_relationship

If DatedVehicleJourney.VehicleJourneyState exists and is
CANCELLED, then CANCELED
ELSE
If a vehicle journey exists, then SCHEDULED, else ADDED

trip_update.vehicle.id

MonitoredVehicleJourney.IsAssignedToVehicleGid

trip_update.stop_time_update.stop_id

trip_update.stop_time_update.stop_sequence

trip_update.stop_time_update.arrival.delay

trip_update.stop_time_update.arrival.time

trip_update.stop_time_update.arrival.uncertainty

trip_update.stop_time_update.departure.delay

trip_update.stop_time_update.departure.time

trip_update.stop_time_update.departure.uncertainty

trip_update.timestamp

  • No labels