Calculate travel time isochrone reachability zones, catchment areas, and routes for driving, cycling, and walking with GeoJSON export.
Calculated 15, 30, and 45-minute driving isochrones for Central London. Catchment area: 486 sq km.
Isochrone Reachability Parameters
Metropolitan Hub Presets:
Point-to-Point Route Comparison
Isochrone Polygon Catchment Map
15 min30 min45 min
Max Reachable Area486.2 km²~187.7 sq miles
Max Radial Distance18.4 kmAlong highway corridors
Estimated Catchment Pop.3.42 MillionUrban density model
Average Travel Velocity28.5 km/hFactoring urban signals
RFC 7946 GeoJSON FeatureCollection
Loading GeoJSON polygon data...
About this tool
How to use it
Enter a starting location or select one of the metropolitan hub presets (London, Paris, NYC, Berlin, Tokyo).
Select your travel profile (Driving by car, Cycling, or Pedestrian walking).
Choose your maximum travel time horizon (15, 30, 45, or 60 minutes) and traffic congestion level.
Click 'Compute Reachability Zone' to render the multi-tiered isochrone polygon map and view catchment area and population metrics.
Download or copy the RFC 7946 compliant GeoJSON output to import into GIS mapping software such as QGIS, Mapbox, or Leaflet.
Why it matters
Isochrone maps visualize real-world travel times rather than simplistic circular 'as the crow flies' distance radiuses. By factoring in road network layout, speed limits, and traffic congestion, isochrones provide realistic assessments for real estate searches, logistics routing, and retail store catchment analysis.
When to use it
Use this tool when evaluating commute times for property purchases, planning delivery service zones, or assessing urban accessibility for public transport and bike infrastructure.
Common questions
What is the difference between a distance buffer and an isochrone?
A distance buffer creates a simple circle around a point ignoring geographic barriers. An isochrone accounts for actual road networks, rivers, highway interchanges, and speed limits, creating realistic irregular polygons reflecting true travel times.
How does the tool model urban road network tortuosity?
The engine applies an empirical road tortuosity factor (0.85) and urban corridor distortions to simulate radial transit along arterials versus slower secondary surface streets.
What format is the exported GeoJSON file?
The file adheres strictly to the RFC 7946 GeoJSON specification with Polygon and Point features, containing attributes for hub coordinates, travel mode, time horizon, and computed area in square kilometers.
Does this calculation require paid API tokens?
No. The calculation and polygon generation algorithms run completely client-side in your browser, enabling instant offline analysis without third-party API keys or subscription fees.