Difference between revisions of "GTFS-ride"
(Updated URL for more information) |
(Added numbered list of initial engagement steps.) |
||
Line 4: | Line 4: | ||
More on GTFS-ride can be found at [http://www.gtfs-ride.org www.gtfs-ride.org] | More on GTFS-ride can be found at [http://www.gtfs-ride.org www.gtfs-ride.org] | ||
+ | |||
+ | === How do I get started? === | ||
+ | # Review the standard at [http://spec.gtfs-ride.org spec.gtfs-ride.org]. | ||
+ | # Take a look at GTFS-ride [https://github.com/ODOT-PTS/GTFS-ride/tree/master/spec/en/examples examples]. | ||
+ | # Create your own feed based on existing GTFS feed and ridership data. | ||
+ | # Use the [http://validation.gtfs-ride.org GTFS-ride feed validator] to test your feed. | ||
+ | # Publish your validated GTFS-ride feed. |
Revision as of 20:44, 16 February 2018
https://www.transitwiki.org/TransitWiki/index.php?title=GTFS-ride&veaction=editGTFS-ride is a feed specification that allows public transportation agencies to describe and assess service consumption. GTFS-ride has arisen as a necessary complement to GTFS and GTFS-RT, which describe the kinds of service provided by a transit agency. The Oregon Department of Transportation is funding GTFS-ride specifications to describe occupancy, boarding, and alighting per stop. This will create a standards-compliant data stream for analyzing transit usage. This data is also a prerequisite for assessing transit-corridor person delay, a metric which can be used to prioritize investments in Bus Rapid Transit projects.
More on GTFS-ride can be found at www.gtfs-ride.org
How do I get started?
- Review the standard at spec.gtfs-ride.org.
- Take a look at GTFS-ride examples.
- Create your own feed based on existing GTFS feed and ridership data.
- Use the GTFS-ride feed validator to test your feed.
- Publish your validated GTFS-ride feed.