Run IDs are not unique across the network. If you are interested in a
specific run, consider supplying a value to the optional route_type
argument.
run_information( run_ref, route_type = NULL, include_geopath = FALSE, geopath_utc = NULL, date_utc = NULL, user_id = determine_user_id(), api_key = determine_api_key() )
run_ref | A character run reference. This supersedes the integer
|
---|---|
route_type | Optionally filter results by a route type. A route type can
be provided either as a non-negative integer code, or as a character:
"Tram", "Train", "Bus", "Vline" or "Night Bus". Character inputs are not
case-sensitive. Use the |
include_geopath | Logical. Whether to populate the |
geopath_utc | Date, or character that can be converted to a date. The
UTC date for which the geopaths are effective. Defaults to the current
date. Has no effect if |
date_utc | Date, or character that can be converted to a date. The UTC date for which the results are effective. Defaults to the current date. It's uncertain how much historical or future-dated data is available. This argument is experimental and seems to not be functioning. |
user_id | Integer or character. A user ID or devid provided by Public
Transport Victoria. Refer to |
api_key | Character. An API key, with dashes, provided by Public
Transport Victoria. Refer to |
A tibble with the following columns:
run_id
(deprecated, use run_ref
instead)
run_ref
route_id
route_type
route_type_description
direction_id
run_sequence
final_stop_id
destination_name
status
express_stop_count
vehicle_position
vehicle_descriptor
geopath
if (FALSE) { run_information("100") run_information("100", include_geopath = TRUE) run_information("100", include_geopath = TRUE, geopath_utc = "2020-07-01") run_information("100", date_utc = "2020-07-01") }