Talk by Joe Hughes from the first TransitCampBayArea event about public transit schedule data and how transit agencies can benefit by allowing outside developers to create third-party transit sites.
71. In 2005, we launched
Google Transit, a fast
trip planner that made it
easy to flip through
different results for a
given transit trip.
72.
73. Last year, public transit
became a first-class
citizen in Maps. This
means that it’s easy to
discover whether public
transit makes sense for
your trip...
74.
75.
76.
77. How does Google get this
data?
How can we collect this data, for the whole world?
79. So we started from
something that worked
(Portland TriMet data
dump), and created the
Google Transit Feed
Specification (GTFS)
80. It’s CSV; easy to
understand, and maps
well to the DB table-
oriented workflow that
agency IT staff are
familiar with
81.
82.
83. It’s an open format, and
its further development
is decided by the
community of users.
84. The agencies prepare
these feed and put them
on their server for
Google to retrieve... but
they’re also usable by
other developers if the
agency is willing
http://www.google.com/intl/en
Agency
Your transit
project?
94. Google Maps API learn how to make a mashup
code.google.com/apis/maps
Headway Wiki get inspired by what others have done
headwayblog.com/wiki
Google Transit group talk to like-minded folks
groups.google.com/group/googletransit
GTFS format learn how to publish your schedules for reuse
maps.google.com/transitfeed
Contact me get in touch!
joe@headwayblog.com