Access
Where can riders actually get?
Travel-time reach and job access, from any point on your network.
What it measures
Reach isochrones
Where riders can get within 15, 30, 45 and 60 minutes, by walking and transit.
Regional job access
How many jobs the average resident can reach within 30 and 45 minutes, by transit and walking.
Your schedule, real streets
Runs on your GTFS and OpenStreetMap streets, with the open-source Conveyal R5 routing engine.
Before and after a change
Compare reach before and after a change, and see what it adds or removes.
ProTransit reach and job access are part of the Pro plan, and the 90-day trial includes them. See pricing →
Click a point, see the reach
Say you extend a route 2 miles east. How many more jobs can riders reach within 45 minutes? Draw the extension, and reach and job access recompute for your scenario.
Where on your network would you click first?
Frequently asked questions
- What engine computes the travel times?
- The open-source Conveyal R5 routing engine, on your GTFS schedule and OpenStreetMap streets.
- Can I compare access before and after a change?
- Yes. Reach and job access recompute for your scenario, so you can show what a change adds or removes.
- Where do the job numbers come from?
- The U.S. Census LEHD LODES dataset.
See it on your network in 15 minutes
We load your GTFS and walk through one real service change with you: the cost, who it affects, and the report. No sales script.