domain: gtfs.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Download the agency's GTFS zip file (required and optional .txt CSV files such as agency.txt, stops.txt, routes.txt, trips.txt, stop_times.txt, calendar.txt)
Check the field-by-field reference at gtfs.org/documentation/schedule/reference/ to confirm which fields are required, conditionally required, or optional
Parse stops.txt and confirm stop_lat/stop_lon are present for stops, stations, and entrances (location_type 0-2)
Join trips.txt to routes.txt via route_id and to calendar.txt/calendar_dates.txt via service_id to resolve which days each trip operates
If shapes.txt is present, associate shape_id from trips.txt with the ordered points in shapes.txt to render the vehicle path
Run the feed through a validator before shipping to catch reference and shape errors early
Known gotchas
GTFS is a loosely-versioned, community-maintained spec (gtfs.org) — check the current reference page rather than assuming a cached copy of the field list is current
Conditionally-required fields (e.g., stop_lat/lon depending on location_type) are easy to miss with a naive required-field check
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?