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 |
|
header.incrementality |
|
header.timestamp | UTC time in seconds of file creation. Example: |
Alert
Files: 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) |
alert.description_text.translation.text | DeviationMessage.Content (UsageTypeShortName=DETAILS) |
alert.cause |
|
alert.informed_entity.route_id | Line.Gid |
alert.informed_entity.stop_id | StopPoint.Gid |
alert.informed_entity.agency_id | TransportAuthority.Id |
alert.informed_entity.trip.trip_id | VehicleJourney.Id |
alert.informed_entity.trip.schedule_relationship | If a vehicle journey exists, then |
Trip updates
Files: TripUpdates.txt and TripUpdates.pb.
When trip updates are generated, stop time updates with departure or arrival times that are considered too old are excluded. A departure/arrival is considered too old if the vehicle left the stop 10 minutes ago.
GTFS-R | NOPTIS |
---|---|
id | DatedVehicleJourney.Id |
trip_update.trip.trip_id | If planned, then VehicleJourney.Id |
trip_update.trip.route_id | Line.Gid |
trip_update.trip.direction_id | DirectionOfLine.DirectionCode → direction_id
|
trip_update.trip.start_time | DatedVehicleJourney.TimetabledStartDateTime |
trip_update.trip.start_date | DatedVehicleJourney.TimetabledStartDateTime |
trip_update.trip.schedule_relationship | If DatedVehicleJourney.VehicleJourneyState exists and is canceled, then |
trip_update.vehicle.id | MonitoredVehicleJourney.IsAssignedToVehicleGid |
trip_update.stop_time_update.stop_id | StopPoint.Gid |
trip_update.stop_time_update.stop_sequence | Departure.JourneyPatternSequenceNumber |
trip_update.stop_time_update.arrival.delay | Based on predicted arrival time and planned arrival time |
trip_update.stop_time_update.arrival.time | Arrival.ObservedDateTime or Arrival.TargetDateTime |
trip_update.stop_time_update.arrival.uncertainty |
|
trip_update.stop_time_update.arrival.schedule_relationship |
|
trip_update.stop_time_update.departure.delay | Based on predicted departure time and planned departure time |
trip_update.stop_time_update.departure.time | Departure.ObservedDateTime or Departure.TargetDateTime |
trip_update.stop_time_update.departure.uncertainty |
|
trip_update.stop_time_update.departure.schedule_relationship |
|
trip_update.timestamp | Departure.Timestamp The latest timestamp overall in the list of departures and arrivals in the current trip update |
Vehicle position
Files: Vehiclepositions.txt and Vehiclepositions.pb.
Entity Position in the below table refers to a POSROI message.
GTFS-R | NOPTIS | Comment |
---|---|---|
id | Position.Nr | |
vehicle.trip.trip_id | VehicleJourney.Id | If a scheduled journey exists, then trip_id is used for identification, else route_id and direction_id is used. |
vehicle.trip.route_id | Line.Gid | |
vehicle.trip.direction_id | DirectionOfLine.DirectionCode → direction_id
| |
vehicle.trip.start_time | DatedVehicleJourney.TimetabledStartDateTime | Is only included if a trip is unscheduled. |
vehicle.trip.start_date | DatedVehicleJourney.TimetabledStartDateTime | Is only included if a trip is unscheduled. |
vehicle.trip.schedule_relationship | If vehicle journey exists, then | |
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 |