A new section on making a transit feed publicly available. This wasn't
previously discussed on the group, because it wasn't strictly a change to
how the data is interpreted or written. However, some of the folks at
Google thought that it would be informative to include discussion of
non-Google uses of GTFS, since there are an increasing number of
applications that can make use of GTFS-formatted data.
Added note that calendar.txt can be omitted if all the service
dates are defined in calendar_dates.txt.
Made the agency_id field optional in feeds containing only one
agency. This allows existing feeds without agency_id to remain
Added fuller specification of agency_url, stop_url,
and route_url, and additional example values for those
Added 6 (Gondola) and 7 (Funicular) as
valid route_type values.
March 8, 2007
Minor edit to move the stop_url field
from stop_times.txt, where it was incorrectly specified in the
Feb. 28 update, to stops.txt, where it belongs.
March 5, 2007
Minor edit to clarify the description of the route_long_name
February 28, 2007
Addition of frequencies.txt for headway-based schedule
Multiple agencies now allowed in the the same feed. Also added new
agency_id field in both agencies.txt
and routes.txt that lets you specify which route is operated by
Addition of per-route and per-stop URLs.
Addition of direction_id field in trips.txt.
Support for mid-trip headsign changes with addition
of stop_headsign field in stop_times.txt.
Support for route colors with addition of optional route_color
and route_text_color in routes.txt.
Removed the ability to specify stops using street addresses. The
previous version of the spec allowed you to give the location of a
transit stop using a street address in the stop_street, stop_city,
stop_region, stop_postcode, and stop_country fields. Now stop locations
must be given using stop_lat for latitude and stop_lon
for longitude, which are more useful for most applications.
Addition of cable car vehicle type for route_type field