Model station wayfinding and step-free accessibility using GTFS-Pathways
domain: gtfs.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the feed includes pathways.txt and levels.txt in addition to standard stops.txt
Model each station as a graph of stop 'nodes' connected by pathway 'edges' (stairs, escalators, elevators, walkways) per gtfs.org/documentation/schedule/examples/pathways/
Read pathway_mode and is_bidirectional to determine mode and directionality of each connection
Use levels.txt to place pathways/stops correctly across multiple building floors
Feed the pathway graph into trip-planning software to compute step-free or minimal-stair routes for accessibility
Known gotchas
Pathways models static topology only; real-time outage information (elevator/escalator down) is a separate, less-standardized layer and isn't guaranteed to exist in a given feed
Sparse or incomplete pathway graphs make a routing engine report 'no accessible path' even when one exists physically
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?