Difference between revisions of "GTFS-ride"
Jump to navigation
Jump to search
m (fixed image scaling) |
(changed image to thumbnail) |
||
| Line 13: | Line 13: | ||
=== Connecting GTFS to GTFS-ride === | === Connecting GTFS to GTFS-ride === | ||
| − | [[File:Ride GTFS relationship.png|left| | + | [[File:Ride GTFS relationship.png|left|640x640px|Relationship between GTFS files and newly created GTFS-ride files.|thumb]] |
Revision as of 20:55, 22 February 2018
GTFS-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.
