Difference between revisions of "GTFS-realtime"

From TransitWiki
Jump to navigation Jump to search
(Add GTFS-RT consumer)
m
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
===Definition===
 
===Definition===
  
''from Google's [https://developers.google.com/transit/gtfs-realtime/ "What is GTFS-realtime?" guide'']:
+
''from Google's [https://developers.google.com/transit/gtfs-realtime/ "What is GTFS-realtime?" guide]:''
  
 
GTFS-realtime is a feed specification that allows public transportation agencies to provide realtime updates about their fleet to application developers. It is an extension to GTFS ([[General Transit Feed Specification]]), an open data format for public transportation schedules and associated geographic information. GTFS-realtime was designed around ease of implementation, good GTFS interoperability and a focus on passenger information.
 
GTFS-realtime is a feed specification that allows public transportation agencies to provide realtime updates about their fleet to application developers. It is an extension to GTFS ([[General Transit Feed Specification]]), an open data format for public transportation schedules and associated geographic information. GTFS-realtime was designed around ease of implementation, good GTFS interoperability and a focus on passenger information.
Line 21: Line 21:
 
* [[OneBusAway]]
 
* [[OneBusAway]]
 
* [[Bing Maps]]
 
* [[Bing Maps]]
* [[Transit App]]
+
* [[The Transit App|Transit App]]
 
* [[Traze.app]]
 
* [[Traze.app]]
 +
* CityMapper
  
 
===GTFS-realtime validation===
 
===GTFS-realtime validation===
Line 29: Line 30:
  
 
However, a [https://github.com/CUTR-at-USF/gtfs-realtime-validator GTFS-realtime validation tool] is currently under development at the [https://www.cutr.usf.edu/ Center for Urban Transportation Research] at the [http://www.usf.edu/ University of South Florida] as part of a [http://nitc.trec.pdx.edu/ National Institute for Transportation and Communities (NITC)]-funded, based on early work from a 2015 Google Summer of Code project.
 
However, a [https://github.com/CUTR-at-USF/gtfs-realtime-validator GTFS-realtime validation tool] is currently under development at the [https://www.cutr.usf.edu/ Center for Urban Transportation Research] at the [http://www.usf.edu/ University of South Florida] as part of a [http://nitc.trec.pdx.edu/ National Institute for Transportation and Communities (NITC)]-funded, based on early work from a 2015 Google Summer of Code project.
 +
== References ==
 +
<references />
  
 
[[Category:GIS]]
 
[[Category:GIS]]
 
[[Category:Technology]]
 
[[Category:Technology]]
 
[[Category:Open data]]
 
[[Category:Open data]]

Latest revision as of 21:42, 26 November 2019

Definition

from Google's "What is GTFS-realtime?" guide:

GTFS-realtime is a feed specification that allows public transportation agencies to provide realtime updates about their fleet to application developers. It is an extension to GTFS (General Transit Feed Specification), an open data format for public transportation schedules and associated geographic information. GTFS-realtime was designed around ease of implementation, good GTFS interoperability and a focus on passenger information.

The specification was designed through a partnership of the initial Live Transit Updates partner agencies, a number of transit developers and Google. The specification is published under the Apache 2.0 License.[1]

Components of GTFS-realtime

How to provide GTFS-realtime

This is a stub section that needs to be developed.

Applications that consume GTFS-realtime data

List is not comprehensive

GTFS-realtime validation

As of March 2017, there is no official public validation tool either endorsed by the GTFS-realtime community or provided by Google that validates that a GTFS-realtime feed contents are correct.

However, a GTFS-realtime validation tool is currently under development at the Center for Urban Transportation Research at the University of South Florida as part of a National Institute for Transportation and Communities (NITC)-funded, based on early work from a 2015 Google Summer of Code project.

References