Methodology

GTFS and structured city data are normalized into station, line, edge, transfer, fare, shape, service-calendar, and station-schedule datasets. Manual city datasets are used only where the repository already contains structured source records.

Generated route pages use the route graph and fare strategies available for each city. Bulk station-pair route pages are noindexed so search engines focus on stronger city, station, line, and policy pages.

Validation scripts check station counts, route patterns, service dates, stop times, shapes, fares, and route-engine behavior where those records exist. The site still labels estimated or unavailable information because validation cannot turn missing source data into official data.

Pages prefer stable station names, line names, and slugs from the source data. We do not invent gates, facilities, landmarks, live arrivals, fares, or timetable values to make a page appear more complete.

Last updated: August 16, 2026.