Isochrone endpoint
Compute a travel-time polygon from a coordinate. Answers “everywhere you can reach within N minutes” by driving, walking, cycling, or transit.
GET
https://{country}.yatmo.com/isochrone
LicenseKey header
Computed live via routing engine; can take ~1s for large polygons.
Request
| Name | In | Type | Description |
|---|---|---|---|
| travelMode required | query | int | 1 = Driving, 2 = Walking, 3 = Bicycling, 4 = Transit. |
| latitude required | query | double | Origin latitude. |
| longitude required | query | double | Origin longitude. |
| numberOfSeconds required | query | int |
Travel-time limit in seconds. Standard values: 300 (5 min), 600 (10 min), 1200 (20 min). Larger values take much longer to compute.
|
Examples
curl -H 'LicenseKey: YOUR_KEY' \
'https://be.yatmo.com/isochrone?travelMode=1&latitude=50.8520525&longitude=4.3442926&numberOfSeconds=600'
const url = 'https://be.yatmo.com/isochrone'
+ '?travelMode=1&latitude=50.8520525&longitude=4.3442926&numberOfSeconds=600';
const res = await fetch(url, { headers: { LicenseKey: 'YOUR_KEY' } });
const featureCollection = await res.json();
// featureCollection.features[0].geometry is a Polygon with the reachable area
$qs = http_build_query([
'travelMode' => 1,
'latitude' => 50.8520525,
'longitude' => 4.3442926,
'numberOfSeconds' => 600,
]);
$ch = curl_init("https://be.yatmo.com/isochrone?$qs");
curl_setopt($ch, CURLOPT_HTTPHEADER, ['LicenseKey: YOUR_KEY']);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$geo = json_decode(curl_exec($ch), true);
curl_close($ch);
using var http = new HttpClient();
http.DefaultRequestHeaders.Add("LicenseKey", "YOUR_KEY");
var qs = "travelMode=1&latitude=50.8520525&longitude=4.3442926&numberOfSeconds=600";
var geo = await http.GetStringAsync($"https://be.yatmo.com/isochrone?{qs}");
Variants
GET /isochrone— the standard endpoint above. Returns a single isochrone polygon.GET /isochrone/TravelTime— same shape, optimized for faster computation. Same parameters, same response.GET /isochrone/GetMultipleTimes— returns three polygons (5 / 10 / 20 minutes) in one call. Requireslanguageinstead ofnumberOfSeconds.
Notes
- Output is GeoJSON — a
FeatureCollectionwith one (or several) polygon features. Coordinates are[longitude, latitude]per the GeoJSON spec. - Don’t request huge time horizons. 30 / 60-minute isochrones can take many seconds to compute and produce massive polygons. Stick to the standard 5 / 10 / 20-minute brackets unless you really need more.
- Transit availability varies by country.
travelMode=4requires GTFS data; some countries have full coverage, others only major cities.