Difference between revisions of "General Transit Feed Specification"

From TransitWiki
Jump to navigation Jump to search
(Added reference to "The Many Uses of GTFS Data" by Antrim and Barbeau)
(Added origins & history section)
Line 6: Line 6:
  
 
GTFS "feeds" allow public transit agencies to publish their transit data and developers to use that data to write applications. The feeds are represented in a series of text files that are compressed into a ZIP file, and include information such as fixed-route schedules, routes, and bus stop data. Many transit agencies have created and published GTFS data with the primary purpose being integration with Google Maps. However, GTFS data can used by a variety of third-party software applications for many purposes, such as trip planning, [[Ridesharing|ridesharing]], and mobile applications.
 
GTFS "feeds" allow public transit agencies to publish their transit data and developers to use that data to write applications. The feeds are represented in a series of text files that are compressed into a ZIP file, and include information such as fixed-route schedules, routes, and bus stop data. Many transit agencies have created and published GTFS data with the primary purpose being integration with Google Maps. However, GTFS data can used by a variety of third-party software applications for many purposes, such as trip planning, [[Ridesharing|ridesharing]], and mobile applications.
 +
 +
==Origins & history==
 +
[http://trimet.org TriMet] in Portland, Oregon was one of the first public agencies to try and tackle the problem of online transit trip planners through the use of open datasets that are shared with the general public. In 2005, TriMet approached Google, as well as a few other driving trip planner vendors, and asked if they had any plans on incorporating transit in their trip planners based on public TriMet data<ref>Matthew Roth. (2012). "How Google and Portland’s TriMet Set the Standard for Open Transit Data." SF.STREETSBLOG.ORG. January 5, 2010. Accessed:  from http://sf.streetsblog.org/2010/01/05/how-google-and-portlands-trimet-set-the-standard-for-open-transit-data/</ref>. Google was the only vendor to reply to TriMet’s request. TriMet and Google then decided to team up to implement one of the first transit trip planners in Portland.
 +
 +
One of the first issues that TriMet and Google faced was the problem of sustainable data – in order to provide quality trips, the trip planner would need quality transit schedule, route, and stop data in an electronic format that was constantly up-to-date. TriMet worked with Google to format their transit data into an easily maintainable and consumable format that could be imported into Google Maps. This transit data format became known as the Google Transit Feed Specification (GTFS)<ref>Google, Inc. "General Transit Feed Specification Reference." Accessed February 24, 2012 from http://developers.google.com/transit/gtfs/reference</ref>. In 2005, this trip planning service was launched as Google Transit<ref>Matthew Roth. (2012). "How Google and Portland’s TriMet Set the Standard for Open Transit Data." SF.STREETSBLOG.ORG. January 5, 2010. Accessed:  from http://sf.streetsblog.org/2010/01/05/how-google-and-portlands-trimet-set-the-standard-for-open-transit-data/</ref>.
 +
 +
After a successful launch with TriMet, Google Transit offered their trip planner service for free to any agency that formatted and maintained their data in the GTFS format.  In 2006, five more agencies were added.  Google Transit’s success continued as more and more agencies wanted access to a free trip planner, and were willing to put their data into the GTFS format to get it.
 +
 +
Since its creation in 2005, GTFS has become the most popularly-used data format to describe fixed-route transit services in the world. Many agencies have decided to share their GTFS data openly with the public, while others choose to restrict access only to select partners (e.g., Google Maps). As of March 2012, there were are an estimated 261 transit agencies worldwide, including 227 transit agencies in the U.S., that share their GTFS data openly with the general public<ref>Front Seat Management, LLC. "City-Go-Round." Accessed March 1, 2012 from http://www.citygoround.org/agencies/</ref>. Google states that their Google Transit service covers 5900 agencies around the world<ref>Google, Inc. "Transit – Google Maps." Accessed August 20, 2015 from http://maps.google.com/landing/transit/cities/index.html</ref>, however, some of this transit information is probably derived from sources other than GTFS.
  
 
==The Many Uses of GTFS Data--A Summary==
 
==The Many Uses of GTFS Data--A Summary==

Revision as of 21:26, 20 August 2015

A GTFS dataset from a transit agency, showing the schedules, routes, and shapes files. Dataset from San Francisco BART.

Introduction

The General Transit Feed Specification (GTFS) defines a common format for public transportation schedules and associated geographic information. The format was developed in 2005, when Trimet in Portland, Oregon began working with Google on incorporating transit agency data in their trip planners.[1] They came up with Google Transit Feed Specification, which was easily maintainable and could be imported into Google Maps. Google offered their trip planning services for free to any agency that formatted and maintained their transit data in that format, later to become called General Transit Feed Specification. Now, GTFS has become the most popularly-used data format in the world, with increasing numbers of agencies choosing to share their transit data with the public.

GTFS "feeds" allow public transit agencies to publish their transit data and developers to use that data to write applications. The feeds are represented in a series of text files that are compressed into a ZIP file, and include information such as fixed-route schedules, routes, and bus stop data. Many transit agencies have created and published GTFS data with the primary purpose being integration with Google Maps. However, GTFS data can used by a variety of third-party software applications for many purposes, such as trip planning, ridesharing, and mobile applications.

Origins & history

TriMet in Portland, Oregon was one of the first public agencies to try and tackle the problem of online transit trip planners through the use of open datasets that are shared with the general public. In 2005, TriMet approached Google, as well as a few other driving trip planner vendors, and asked if they had any plans on incorporating transit in their trip planners based on public TriMet data[2]. Google was the only vendor to reply to TriMet’s request. TriMet and Google then decided to team up to implement one of the first transit trip planners in Portland.

One of the first issues that TriMet and Google faced was the problem of sustainable data – in order to provide quality trips, the trip planner would need quality transit schedule, route, and stop data in an electronic format that was constantly up-to-date. TriMet worked with Google to format their transit data into an easily maintainable and consumable format that could be imported into Google Maps. This transit data format became known as the Google Transit Feed Specification (GTFS)[3]. In 2005, this trip planning service was launched as Google Transit[4].

After a successful launch with TriMet, Google Transit offered their trip planner service for free to any agency that formatted and maintained their data in the GTFS format. In 2006, five more agencies were added. Google Transit’s success continued as more and more agencies wanted access to a free trip planner, and were willing to put their data into the GTFS format to get it.

Since its creation in 2005, GTFS has become the most popularly-used data format to describe fixed-route transit services in the world. Many agencies have decided to share their GTFS data openly with the public, while others choose to restrict access only to select partners (e.g., Google Maps). As of March 2012, there were are an estimated 261 transit agencies worldwide, including 227 transit agencies in the U.S., that share their GTFS data openly with the general public[5]. Google states that their Google Transit service covers 5900 agencies around the world[6], however, some of this transit information is probably derived from sources other than GTFS.

The Many Uses of GTFS Data--A Summary

"The Many Uses of GTFS Data", published by Antrim and Barbeau (2013), provides an overview of the GTFS opportunities for transit agencies and describes many different uses and benefits that can assist agencies in maximizing their investment in GTFS data.[7]

Creating and Maintaining a GTFS Dataset

Transit agencies must choose between formatting a GTFS dataset in-house or outsourcing the task. The datasets have to be updated when there are schedule changes, and since major transit agencies update their schedules several times a year, some agencies might find greater benefits to outsourcing. If agencies choose to outsource, the cost per route ranges from $200 to $500, depending on the complexity of the route and availability of existing route data. [8]

Disseminating GTFS Data

Some agencies have chosen to share their transit data with select vendors such as Google Transit. They are typically concerned with legal exposure due to the lack of accuracy of data, loss of control of agency brand, and loss of control of dissemination of transit service information. However, many others feel the benefits of open transit data outweigh the risks, since developers can screen-scrape agency websites, which is not ideal for either party. Currently, over 200 transit agencies in the United States have chosen to openly share their GTFS data. [9]

The Google Transit Partner Program allows public transportation agencies to provide schedules and geographic information to Google Maps and other Google applications that show transit information. The website provides instructions for agencies just starting the GTFS sharing process and gives suggestions on how to create high-quality feeds. [10] For agencies that wish to make their data available to everyone, they can share the feeds on websites such as GTFS Data Exchange, which was designed to help developers and transit agencies efficiently share and retrieve GTFS data. [11]

Applications Based on GTFS

The following are just a few examples of the types of applications and names of existing application that use GTFS. The Category:GTFS-consuming applications page aims to be a directory of applications that utilize GTFS data for various purposes.

  • Trip planning and maps
Google Maps is currently implemented for most transit agencies that publish GTFS. Other examples of trip planning applications are Bing Maps and OpenTripPlanner. A number of other websites graphically map where GTFS data is available (e.g. TRAVIC: Transit Visualization Client) and the types of data available.
  • Timetable creation
Timetable Publisher is free, open-source software that creates timetables in both HTML and PDF formats. TriMet in Portland, Oregon uses TimeTable Publisher to create all its timetables, as does Hampton Roads Transit in the south-eastern Virginia area.
  • Data visualization
WalkScore is a website that helps people quantify “walkability” of an area by showing the nearby amenities within walking distance. The website also has a Transit Score, that rates how well an address is served by public transportation. These Transit Scores are now shown on a number of other websites, such as real estate websites where they assist potential purchasers rank how well a property is served by public transport.
  • Accessibility
The Travel Assistant Device (TAD) is designed for sight-impaired or intellectually-disabled passengers. Phones with the application installed give audio and vibrating alerts when it is time for the passenger to pull the stop cord and alight from the bus
  • Real-time transit information
Newer formats, such as GTFS-realtime and SIRI, can be added as an extension to a basic GTFS format so transit agencies can share real-time information.

External Links

References

  1. ↑ How Google and Portland’s TriMet Set the Standard for Open Transit Data
  2. ↑ Matthew Roth. (2012). "How Google and Portland’s TriMet Set the Standard for Open Transit Data." SF.STREETSBLOG.ORG. January 5, 2010. Accessed: from http://sf.streetsblog.org/2010/01/05/how-google-and-portlands-trimet-set-the-standard-for-open-transit-data/
  3. ↑ Google, Inc. "General Transit Feed Specification Reference." Accessed February 24, 2012 from http://developers.google.com/transit/gtfs/reference
  4. ↑ Matthew Roth. (2012). "How Google and Portland’s TriMet Set the Standard for Open Transit Data." SF.STREETSBLOG.ORG. January 5, 2010. Accessed: from http://sf.streetsblog.org/2010/01/05/how-google-and-portlands-trimet-set-the-standard-for-open-transit-data/
  5. ↑ Front Seat Management, LLC. "City-Go-Round." Accessed March 1, 2012 from http://www.citygoround.org/agencies/
  6. ↑ Google, Inc. "Transit – Google Maps." Accessed August 20, 2015 from http://maps.google.com/landing/transit/cities/index.html
  7. ↑ The Many Uses of GTFS Data
  8. ↑ Northern California Google Transit Feasibility Study
  9. ↑ City-Go-Round
  10. ↑ Google Transit Partner Program
  11. ↑ GTFS Data Exchange

Additional Reading

Shasta County Regional Transportation Planning Agency. "Northern California Google Transit Feasibility Study.". (2009).

The Shasta RTPA led a study on the feasibility of integrating small-urban and rural public transit service schedules and geographic information with Google Transit. The study makes recommendations on how Google Transit can be improved to address the needs of small rural agencies.

Florida Department of Transportation. "SunRail Electronic Trip Planning Study Final Report" (2013).

This report was prepared for the FDOT in advance of their SunRail launch; it analyzes various online trip planning options for SunRail to consider, and includes a section on GTFS's benefits, risks, and applications.
Retrieved from "https://www.transitwiki.org/TransitWiki/index.php?title=General_Transit_Feed_Specification&oldid=2591"