Search the USF Web site Site Map USF home page


Center Identification Number:  77902   

Project Title:  Expanding the Google Transit Data Feed Specification to Support Operations and Planning

Principal Investigator:

Martin Catalá, Senior Research Associate
Phone: 813-974-9791


Center for Urban Transportation Research
University of South Florida
Fax: 813-974-5168

External Project Contact:     

Diane Quigley
Florida Department of Transportation
(850) 576-2788


I.  Start and End Dates

Start Date:  July 2009               Expected End Date: January 2011

I.  Project Objective/Problem Statement

The development of Google's free on-line transit trip planner has been one of the most exciting developments in transit for many years.  Transit agencies that store trip information into a specific file format (the Google Transit Feed Specification) and forward the data to Google's transit team will have a robust, recognizable on-line trip planner for free.  But perhaps equally exciting is the impact of the open data architecture, which is not hidden under the veil of proprietary software and has spurred many other developments including extending the usefulness of the Google Transit Feed Specification (GTFS).  One clear example is the development of an Open Source application, TimeTable Publisher, developed by TriMet in Portland, Oregon. Anyone using the GTFS is able create transit timetables in print and web formats using TimeTable publisher.  FTA is promoting the use of TimeTable Publisher through the development of a webinar.  Additional examples of applications built off the GTFS data, include the development of transit planning mobile applications including an IPhone application and a text messaging application.  Also, more traditional GIS desktop applications are using the GTFS, with the development of an ESRI data model for the GTFS.  Given the growing utilization of the GTFS data, this research project proposes an examination of opportunities and existing uses of the GTFS and developing a data schema and application that will help leverage the GTFS data to further benefit transit agencies.  Since the primary purpose of the Google Transit application is to better communicate with the customer, this project will focus on using the GTFS to support service planning and operation business activities.

II.  Objectives/Tasks

The primary goal of the project is to identify how the Google Transit Feed Specification data can be leveraged to further assist transit agencies with business activities such as service planning and operations.  Achieving this goal requires two efforts; an inventory of how transit agencies and software developers are expanding the utility of the Google Transit Feed Specification (GTFS) and the development of a data schema that incorporates the GTFS and supports additional business functions within a transit agency. 

It is important to note, that the goal of the project is not to change the Google transit specification.  The project team will communicate with the Google Transit team during this project to better understand the feed specification.  Changes to the specification may be a by product of this effort but it is not the primary goal. 

Task 1:  Project Management

This task will deal with on-going management activities of the project, preparing progress reports, and reviewing and editing final deliverables.

Task 2:  Literature Review and Case Studies

A review of the research and literature of on-line transit trip planners will be conducted to examine how the trip planning transit data are being used for operations and planning.  The disciplines of information and geo-spatial technologies are at the core of these activities within a transit agency.  Consequently, this research will also examine (minimally) how these technologies and disciplines are being used at transit agencies.   

Case Studies

Transit Agency Case Studies

Transit agencies using Google Transit offer a great deal of insight on the challenges to implementation.  These agencies may reveal a roadmap for how to implement Google transit at their agency. 

Inventory of GTFS Applications and Opportunities

Given that the Google Transit Feed Specification is an open data architecture and is not hidden under the veil of proprietary software it has spurred the development of many other software applications which extends the usefulness of the Google Transit Feed Specification (GTFS).  An inventory of these applications will illustrate the power of an open data architecture and the opportunity it presents for the transit industry.

Examples such as TriMet’s TimeTable Publisher is a high profile example of a transit agency extending the utility of the GTFS, however, other agencies and software developers may be extending the usefulness of the data but are not programmatically developing open source applications as TriMet has done.  Consequently, there may be equally significant applications that are being used internally within transit agencies and developed by private developers.  A review of agencies using Google Transit will assist with identifying such opportunities. 

There are 50 plus North American transit agencies currently employing the Google Transit web application, this task will inventory of how and if the data is being used for other purposes. Additionally, an inventory of applications developed by private developers and research institutions will be conducted to better understand the opportunities available from using the GTFS. 

Recognizing that the GTFS was developed for a single purpose, there are most probably inherent limitations of the GTFS as it pertains to operations and planning within a transit agency.   The inventory will also document the limits of the GTFS and difficulties associated with working with this data set as well as potential opportunities. 

Task 3: Examining Additional Business Application of GTFS

Given the robust nature of the GTFS data it can possibly support several additional business functions; including but not limited to customer service, bus stop inventory management and service planning.  A thorough review of the data elements of the GTFS and the potential business applications will be examined in this task and used in Task 4 to develop and expand a data schema to support these business applications.  Some examples may include:

            Integration with AVL applications

Automatic Vehicle Locator technologies can be used to show “real-time” location of bus information.  This technology is already being utilized as part of “mash-up” applications and Google’s mapping applications.  Integration with the GTFS can help communicate to the public as well as transit managers.  

            Integration with APC Applications

Automatic Passenger Counters (APC) can be used to support service planning and other business decisions.  The data obtained from APC recorders can be integrated with the GTFS and used for visualizing performance data, such as on-time performance, load capacity and overall activity. 

Integration with mobile devices

Mobile devices are quickly evolving as a tool for accessing data from the internet.  To this end several programming efforts are being undertaken to make the Google Transit application available through mobile devices such as the cell phone. 

Web-based Stop Inventory and Management applications

With desktop and mobile internet devices communicating with the internet, applications capable of displaying transit data are able to allow editing and querying opportunities which may support a stop inventory and management system which works with the Google Transit Feed Specification.  

            National Transit Database reporting 

The responsibilities and obligations of transit agencies to report to multiple agencies is a significant burden to transit agencies.  The data from the GTFS may support such activities.  In particular, the NTD reporting agencies could be streamlined to assist agencies with this obligation. 

Task 4: Development of a Data Schema to Support Additional Transit Business Applications

Given the findings in Task 3 a data schema will be developed and prototypes will be developed for the testing the data schema, to support the identified business applications.  The data schema prototypes will coordinate with transit agencies willing to work with the project team.   

Task 5:  Implementation of Applications Using the Data Schema Prototype

Working with transit agencies and other organizations the new prototype data schema will be developed and tested to support additional business opportunities identified in task 3.  The full details of this application are still to be known, but at a minimum the application will include the ability to read and write to the GTFS.   This task will include a consultation with the project team about the direction of the application prototype.

Task 6:  Report Findings

The report findings will be organized into three sections.  The first section will document the opportunities which the GTFS data presents for transit agencies and techniques for leveraging the GTFS to assist transit agencies.  The second section will document the developed data schema and how the implementation of the schema expanded the use of the GTFS data.  The final section of this task will address any difficulties and limitations of the GTFS and Google Transit.  The findings will be combined into a publication for printing and distribution (i.e., PDF).

III. Deliverables

Project deliverables will include quarterly progress reports, a draft final report, and a final report.

Progress Reports

Quarterly Progress Reports - Quarterly progress reports will be provided to the Florida Department of Transportation Project Manager and the Research Office.  Reports will include the following sections:

  1. Contract number, work order number, and title

  2. Work done during the quarter

  3. Work to be done in the following quarter

  4. Requested modifications to scope, budget, or schedule, as appropriate

  5. An updated project progress schedule

Draft Final Report

The draft final report will be edited for grammar, clarity, organization, and readability prior to submission to the Department for technical approval.  The editor providing the review will sign a cover sheet attesting to such review prior to submission. It is expected that a well-written, high-quality report will be submitted.  It is understood that reports failing to meet these requirements will summarily be rejected.  The only changes allowable between the final draft and the final report will be those changes requested by the Project Manager and the Research Center.

Final Report

Final Report – Eight (8) copies of the final report in MS Word on CD and a bound original will be delivered, no later than the end date of the RPWO, to:

Florida Department of Transportation

Research Center, MS 30

605 Suwannee Street

Tallahassee, FL 32399-0450

 All Final Reports shall contain:

  1. A cover page that identifies the project title and contract number, the contractor’s name and contact information, the author’s name, the month and date of publication

  2. Disclaimer language, which alone shall be on the first page within the report and include the following: (1) The opinions, findings and conclusions express in this publication are those of the authors and not necessarily those of the State of Florida Department of Transportation, or the U.S. Department of Transportation, and (2)  Prepared in cooperation with the State of Florida Department of Transportation and the U.S. Department of Transportation.

  3. A completed Technical Report Documentation form #F.1700.7, immediately following the disclaimer page. 

NOTE:  All written deliverables will be submitted in electronic format to the Project Manager and the Research Center for processing.  Electronic reports will be e-mailed to Sandra Bell at Hard copies will be sent to the following address:

Sandra Bell, Research Contracts Administrator

Florida Department of Transportation

605 Suwannee Street, MS 30

Tallahassee, FL 32399-0450


Other Deliverables


A software application, or prototype thereof that can read and write to the Google Transit Format (GTFS) will be delivered.

IV.  Project Schedule

V.  Project Budget

Salaries and Fringe                                        89,812.14

Fixed Price Sub Total                                    89,812.14

Indirect Cost (fixed price subtotal x 10%)    8,981.21

Total Fixed Price Amount                             98,793.36


Total Lump Sum Amount (Salaries and Benefits)                98,793.36

Cost Reimbursable (Subtotal)                                                    1,096.00

Indirect Costs (cost reimbursable subtotal x 10%)                     109.00  

Total Project Cost                                                                           99,998.36      

National Center for Transit Research · at the Center For Urban Transportation Research · University of South Florida · 4202 E. Fowler Ave., CUT100 · Tampa, FL 33620-5375 · (813) 974-3120 · (813) 974-5168 · · Comments: