Tpredictionsbyroute: Query predictions by route

In MBTAr: Access Data from the Massachusetts Bay Transit Authority (MBTA) Web API

Description

Returns predicted upcoming arrivals and departures in the next hour for a particular route.

Usage

 Tpredictionsbyroute(route_id,
include_access_alerts = FALSE, include_service_alerts = TRUE, api_key) 

Arguments

route_id	GTFS-compatible route_id value for which predictions should be returned. Example: "Orange"
include_access_alerts	Whether or not alerts pertaining to accessibility (elevators, escalators) should be returned. Data type: logical. Defaults to FALSE.
include_service_alerts	Whether or not service alerts should be returned. Data type: logical. Defaults to TRUE.
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 predictions are returned. Example: "CR-Franklin"
route_name	The human-readable name for the route for which predictions 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"
stop_sequence	Identifies where the stop comes in the sequence of stops for this trip. Example: "2"
stop_id	The GTFS-compatible unique identifier for the stop. Example: "Back Bay"
stop_name	The GTFS-compatible name for the stop. Example: "Back Bay"
sch_arr_dt	Scheduled arrival time at the stop for the trip, in epoch time. Example: "1361986080"
sch_dep_dt	Scheduled departure time at the stop for the trip, in epoch time. Example: "1361986080"
pre_dt	Predicted time at the stop - departure time for origin stop and arrival time for all other stops - for the trip, in epoch time. Example: "1400855700"
pre_away	Predicted amount of time until the vehicle arrives at the stop, in seconds. Example: "339"

MBTAr documentation built on May 2, 2019, 6:59 a.m.