Solution · Routing · In development
ETAs and service areas from isochrones
An ETA is a /route time, with historical speeds for the time of week. A service area is an /isochrone: the area reachable from a store or hub within a time.
Status · In development
In development, not deployed: there is no routing endpoint to call yet, on geolith.app or api.geolith.app, and no routing plan, price or key.
ETAs and service areas
Arrival times and isochrone delivery zones.
Berlin, byte-identical to Valhalla 3.9.1: 45/45 isochrones; 50/50 historical (predicted) speeds, 30/30 live speeds, 5/5 closures.
Detail
Where routing fits
Two endpoints cover both questions.
ETA: /route with a date_time, so historical speeds apply (in development).
Service area: /isochrone with contours such as 15 and 30 minutes, as GeoJSON polygons to draw or test against (in development).
"Do we deliver here?": geocode the address with geolith Search (live), then test the point against the polygon in your code.
Solutions · In development
More solutions
Sources
- Routing API (planned), geolith docs (read 2026-11-08)
- Routing: traffic and live data, geolith docs (read 2026-11-08)
Routing · In development
Follow routing progress.
Read how the router works today and what has to pass before it is deployed.