Stoptime

Object

arrivalDelay

The offset from the scheduled arrival time in seconds. Negative values indicate that the trip is running ahead of schedule.

departureDelay

The offset from the scheduled departure time in seconds. Negative values indicate that the trip is running ahead of schedule

dropoffType

Whether the vehicle can be disembarked at this stop. This field can also be used to indicate if disembarkation is possible only with special arrangements.

headsign

Vehicle headsign of the trip on this stop. Trip headsigns can change during the trip (e.g. on routes which run on loops), so this value should be used instead of tripHeadsign to display the headsign relevant to the user.

pickupType

Whether the vehicle can be boarded at this stop. This field can also be used to indicate if boarding is possible only with special arrangements.

realtime

true, if this stoptime has real-time data available

realtimeArrival

Real-time prediction of arrival time. Format: seconds since midnight of the departure date

realtimeDeparture

Real-time prediction of departure time. Format: seconds since midnight of the departure date

realtimeState

State of real-time data

scheduledArrival

Scheduled arrival time. Format: seconds since midnight of the departure date

scheduledDeparture

Scheduled departure time. Format: seconds since midnight of the departure date

serviceDay

Departure date of the trip. Format: Unix timestamp (local time) in seconds.

stop

The stop where this arrival/departure happens

stopPosition

The sequence of the stop in the trip. This is not required to start from 0 or be consecutive - any increasing integer sequence along the stops is valid.

The purpose of this field is to identify the stop within the trip so it can be cross-referenced between it and the itinerary. It is safe to cross-reference when done quickly, i.e. within seconds. However, it should be noted that real-time updates can change the values, so don't store it for longer amounts of time.

Depending on the source data, this might not be the GTFS stop_sequence but another value, perhaps even generated.

stopPositionInPattern

The position of the stop in the pattern. This is required to start from 0 and be consecutive along the pattern, up to n-1 for a pattern with n stops.

The purpose of this field is to identify the position of the stop within the pattern so it can be cross-referenced between different trips on the same pattern, as stopPosition can be different between trips even within the same pattern.

timepoint

true, if this stop is used as a time equalization stop. false otherwise.

trip

Trip which this stoptime is for