-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add file linked_datasets.txt containing the Trip Updates, Vehicle Positions and Service Alerts URLs #93
Add file linked_datasets.txt containing the Trip Updates, Vehicle Positions and Service Alerts URLs #93
Changes from 7 commits
fc0ca24
659ef8e
e4a7336
1d9edf3
58c90e6
6e68143
857cfb9
29ebbbc
d6a554a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,6 +22,7 @@ This document explains the types of files that comprise a GTFS transit feed and | |
- [shapes.txt](#shapestxt) | ||
- [frequencies.txt](#frequenciestxt) | ||
- [transfers.txt](#transferstxt) | ||
- [linked_datasets.txt](#linkeddatasetstxt) | ||
- [feed\_info.txt](#feed_infotxt) | ||
|
||
## Term Definitions | ||
|
@@ -50,6 +51,7 @@ This specification defines the following files along with their associated conte | |
| [shapes.txt](#shapestxt) | Optional | Rules for drawing lines on a map to represent a transit organization's routes. | | ||
| [frequencies.txt](#frequenciestxt) | Optional | Headway (time between trips) for routes with variable frequency of service. | | ||
| [transfers.txt](#transferstxt) | Optional | Rules for making connections at transfer points between routes. | | ||
| [linked_datasets.txt](#linkeddatasetstxt) | Optional | URLs to linked datasets: Trip Updates, Vehicle Positions and Service Alerts. | | ||
| [feed_info.txt](#feed_infotxt) | Optional | Additional information about the feed itself, including publisher, version, and expiration information. | | ||
|
||
## File Requirements | ||
|
@@ -414,6 +416,30 @@ Trip planners normally calculate transfer points based on the relative proximity | |
| min_transfer_time | Optional | When a connection between routes requires an amount of time between arrival and departure (transfer_type=2), the **min_transfer_time** field defines the amount of time that must be available in an itinerary to permit a transfer between routes at these stops. The min_transfer_time must be sufficient to permit a typical rider to move between the two stops, including buffer time to allow for schedule variance on each route. | | ||
| | | The min_transfer_time value must be entered in seconds, and must be a non-negative integer. | | ||
|
||
### linked_datasets.txt | ||
|
||
File: **Optional** | ||
|
||
| Field Name | Required | Details | | ||
| ------ | ------ | ------ | | ||
| url | **Required** | The **url** field contains the URL to the linked dataset. The value must be a fully qualified URL that includes a scheme such as **http**:// or **https**://, and any special characters in the URL must be correctly escaped. See http://www.w3.org/Addressing/URL/4_URI_Recommentations.html for a description of how to fully qualified URL values. | | ||
| trip_updates | **Required** | The **trip_updates** field indicates whether the dataset at this URL may contain [a `TripUpdate` entity](https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/reference.md#message-tripupdate). Valid values for this field are: | | ||
| | | * **0** - The dataset at this URL doesn't contain TripUpdate entities. | | ||
| | | * **1** - The dataset at this URL may contain TripUpdate entities. | | ||
| vehicle_positions | **Required** | The **vehicle_positions** field indicates whether the dataset at this URL may contain [a `VehiclePosition` entity](https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/reference.md#message-vehicleposition). Valid values for this field are: | | ||
| | | * **0** - The dataset at this URL doesn't contain TripUpdate entities. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be |
||
| | | * **1** - The dataset at this URL may contain TripUpdate entities. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be |
||
| service_alerts | **Required** | The **service_alerts** field indicates whether the dataset at this URL may contain [an `Alert` entity](https://github.com/google/transit/blob/master/gtfs-realtime/spec/en/reference.md#message-alert). Valid values for this field are: | | ||
| | | * **0** - The dataset at this URL doesn't contain TripUpdate entities. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be |
||
| | | * **1** - The dataset at this URL may contain TripUpdate entities. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be |
||
| authentication_type | **Required** | The **authentication_type** field defines the type of authentication required to access the URL. Valid values for this field are: | | ||
| | | * **0** or **(empty)** - No authentication required. | | ||
| | | * **1** - Ad-hoc authentication required, visit URL in `authentication_info_url` for more informations. | | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should be |
||
| | | * **2** - The authentication requires an API key, which should be passed as value of the parameter `api_key_parameter_name` in the URL. Please visit URL in `authentication_info_url` for more information. | | ||
| authentication_info_url | **Optional** | If authentication is required, the **authentication_info_url** field contains a URL to a human-readable page describing how the authentication should be performed and how credentials can be created. The value must be a fully qualified URL that includes **http**:// or **https**://, and any special characters in the URL must be correctly escaped. See http://www.w3.org/Addressing/URL/4_URI_Recommentations.html for a description of how to fully qualified URL values. This field is required for `authentication_type` `1` or greater. | | ||
| api_key_parameter_name | **Optional** | The **api_key_parameter_name** field defines the name of the parameter to pass in the URL to provide the API key. This field is required for `authentication_type` `2`. | | ||
|
||
|
||
### feed_info.txt | ||
|
||
File: **Optional** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest we include an example here such as:
...just to make sure that it's clear agencies should provide a full URL to a protocol buffer file, not a root directory where the various protocol buffer files are available.