Difference between revisions of "GTFS-ride"

From TransitWiki
Jump to: navigation, search
(changed image to thumbnail)
(modified introduction language and added image of gtfs-ride support elements)
Line 1: Line 1:
 
<includeonly>
 
<includeonly>
 
[[Category:Stubs]]
 
[[Category:Stubs]]
</includeonly><noinclude>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.
+
</includeonly><noinclude>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, which describe the kinds of service provided by a transit agency. The Oregon Department of Transportation is supporting the development of GTFS-ride to describe occupancy, boarding, and alighting per stop. This will create a standards-compliant data stream for analyzing transit usage.  
 +
 
 +
Applications for GTFS-ride are undergoing development. Uses for GTFS-ride formatted data includes 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 [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]
Line 13: Line 15:
  
 
=== Connecting GTFS to GTFS-ride ===
 
=== Connecting GTFS to GTFS-ride ===
[[File:Ride GTFS relationship.png|left|640x640px|Relationship between GTFS files and newly created GTFS-ride files.|thumb]]
+
[[File:Ride GTFS relationship.png|640x640px|Relationship between GTFS files and newly created GTFS-ride files.|thumb|none]]
 +
 
 +
=== Current GTFS-ride Resources ===
 +
[[File:Spr803 elements.jpg|none|thumb|640x640px|Results of ODOT SPR 803 to develop initial elements of an open ridership data standard]]

Revision as of 04:58, 8 March 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, which describe the kinds of service provided by a transit agency. The Oregon Department of Transportation is supporting the development of GTFS-ride to describe occupancy, boarding, and alighting per stop. This will create a standards-compliant data stream for analyzing transit usage.

Applications for GTFS-ride are undergoing development. Uses for GTFS-ride formatted data includes 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?

  1. Review the standard at spec.gtfs-ride.org.
  2. Take a look at GTFS-ride examples.
  3. Create your own feed based on existing GTFS feed and ridership data.
  4. Use the GTFS-ride feed validator to test your feed.
  5. Publish your validated GTFS-ride feed.

Connecting GTFS to GTFS-ride

Relationship between GTFS files and newly created GTFS-ride files.

Current GTFS-ride Resources

Results of ODOT SPR 803 to develop initial elements of an open ridership data standard