-
Notifications
You must be signed in to change notification settings - Fork 1
GTFS
Jip Claassens edited this page Aug 3, 2026
·
3 revisions
(outline, to be written out)
The General Transit Feed Specification is the de facto standard for publishing public transport timetables. A GTFS feed is a set of related CSV files describing stops, routes, trips, stop times and calendars, and it is the standard input for Public transport routing.
For a worked implementation, see Create a routable network from GTFS files in the Dutch national network model documentation, which covers the full path from feed to routable graph in GeoDMS.
- The core files:
stops,routes,trips,stop_times,calendarandcalendar_dates,transfers, and how they relate - Static versus realtime: GTFS and GTFS-RT, and why accessibility modelling uses the static feed
- Choosing a service day: a feed covers many dates while an indicator covers one, so how do you pick a representative day
- Merging feeds: combining feeds from multiple operators, deduplicating stops and reconciling identifiers
- Common quality problems: missing shapes, stops without coordinates, trips outside the calendar period, and inconsistent transfer definitions
- Availability: national and regional feed registries, including the Dutch feeds
Accessibility modelling documentation
© Object Vision BV

Concepts
Networks
- Network data sources
- OSM
- NWB
- GTFS
- Building a routable network
- Network optimisation algorithm
- Travel speeds per mode
Origins & destinations
Computation
- Shortest path and the Dijkstra algorithm
- Origin Destination matrix (trip table)
- Isochrones and catchment areas
- Public transport routing
Indicators
Applications
Network models
Reference