MBTAr (version 2.0.0)

Tvehiclesbyroute: Query vehicles by a route

Description

Returns vehicle positions for upcoming trips (including trips already underway) in a direction for a particular route.

Usage

Tvehiclesbyroute(route_id, api_key)

Arguments

route_id

GTFS-compatible route_id value for which vehicle positions should be returned. Example: "Red"

api_key

API key for MBTA API. To obtain one, visit the MBTA Developer Portal (http://realtime.mbta.com/Portal/)

Value

route_id

The unique GTFS-compatible identifier for the route for which vehicle positions are returned. Example: "CR-Franklin"

route_name

The human-readable name for the route for which vehicle positions are returned. Example: "Franklin Line"

route_type

The GTFS-compatible identifier for the type of service (mode). Example: "2"

mode_name

The human-readable name for the type of service (mode). Example: "Commuter Rail"

direction_id

The GTFS-compatible identifier for the direction. Example: "0"

direction_name

The human-readable name for the direction. Example: "Outbound"

trip_id

The unique GTFS-compatible identifier for the trip. Example: "CR-Providence-CR-Weekday-815"

trip_name

The human-readable name for the trip. Example: "815 (4:35 pm from South Station)"

trip_headsign

The text that identifies the trip's destination to passengers. Example: "North Station"

vehicle_id

The GTFS-compatible unique identifier for the vehicle. Example: "1531"

vehicle_lat

The GTFS-compatible latitude of the vehicle. Example: "42.08997"

vehicle_lon

The GTFS-compatible longitude of the vehicle. Example: "-71.4388"

vehicle_bearing

GTFS-compatable bearing of the vehicle. This can be the compass bearing, or the direction towards the next stop or intermediate location. May be empty. Example: "259"

vehicle_speed

Identifies the vehicle's momentary speed, in meters per second. Example: "21"

vehicle_timestamp

Identifies the moment when the content of this feed has been created, in epoch time. Example: "1400855704"

See Also

Tvehiclesbytrip