Navigation

Routing runs on the Austrian road graph (GIP.at). Coordinates are lon,lat, joined with ;. Every request needs a token (Access and limits); curl samples send it as a header, browser samples as access_token.

Profiles

Public transport is a separate API: Transit.

A route

const url = "https://api.mapx.at/v1/directions/driving/16.3725,48.2085;15.3294,48.2272?steps=true&language=en&access_token=YOUR_TOKEN";
const { routes } = await (await fetch(url)).json();
const r = routes[0];
console.log(r.distance, "m", r.duration, "s");

overview=simplified (default) returns a light geometry, full every vertex, false none. steps=true adds turn-by-turn steps. alternatives=true adds up to two more routes[]. annotations=duration,distance,speed,maxspeed,elevation adds values per segment. With cycling_surface=any (default) unpaved sections are rated worse but stay allowed. Heights inside bridges and tunnels are not taken from the terrain model. maxspeed (step and annotation) is {speed, unit, legal}: legal: true marks a statutory limit (5, 10, 20 … 130 km/h), legal: false a modeled GIP speed such as 53 or 84 km/h, which is a routing speed and not a limit and must not be shown as a speed sign. {unknown: true} means no value (many motorways). Existing clients that only read speed and unit keep working. Cycling and walking steps carry grade_pct; the route summary has ascent, descent and elevation range.

Speed limits along a route

GET /v1/speedlimits returns the statutory limits of the road network as compact GeoJSON, either in a box (bbox, at most 0.08 square degrees, about 28 by 28 km) or in a corridor around a route (corridor as polyline6 plus buffer in meters, default 30). Each road link is a LineString (digitizing direction) with limit_kmh, direction (both, forward, backward) and id. Links without a statutory limit are left out, so the sign display never shows a modeled speed.

# route as polyline6, then the limits in a 30 m corridor
curl -s -H "Authorization: Bearer YOUR_TOKEN" "https://api.mapx.at/v1/speedlimits?bbox=15.325,48.225,15.335,48.23" | jq '.features | length'
curl -s -H "Authorization: Bearer YOUR_TOKEN" "https://api.mapx.at/v1/directions/driving/15.6256,48.2049;15.3294,48.2272?geometries=polyline6&overview=full" | jq -j '.routes[0].geometry' > route.txt
curl -s -H "Authorization: Bearer YOUR_TOKEN" -G "https://api.mapx.at/v1/speedlimits" --data-urlencode "corridor@route.txt" -d buffer=30 | jq '.features | length'

Write the polyline without a trailing newline (jq -j). Long routes can exceed the URL length of a GET request; split them into sections of about 500 points. Source: GIP.at, CC BY 4.0.

Offline rerouting

GET /v1/corridor-graph returns the road network around a route as one compact binary file (gzip stream, application/vnd.mapx.corridor-graph+gzip), so an app can recompute a route without network, for example after a wrong turn in a dead zone. Pass the route as polyline6 in polyline, the radius in buffer (100 to 5000 m, default 3000) and profile (driving default, cycling or walking). The file holds nodes, arcs with the travel times the router uses, road names, speed limits and turn restrictions; expect 1 to 3 MB per 100 km of route. Zone heavy. Source: GIP.at, CC BY 4.0.

curl -s -H "Authorization: Bearer YOUR_TOKEN" -G "https://api.mapx.at/v1/corridor-graph" --data-urlencode "polyline@route.txt" -d buffer=500 -o corridor.mxcg

Truck routes

curl -s -H "Authorization: Bearer YOUR_TOKEN" "https://api.mapx.at/v1/directions/driving-truck/15.6256,48.2049;15.3294,48.2272?weight=40&height=4&width=2.55&length=16.5&truck_type=semi&overview=false" | jq '.routes[0] | {distance, duration, truck}'

The router avoids roads closed to the vehicle: weight-class and trailer bans, height, width, weight and length limits. Speeds are capped at 80 km/h on motorways, 70 on rural roads, 50 in built-up areas. District-wide bans from free-text ordinances are not routed; affected roads are reported in steps[].notices[] with type: truck_restriction.

Tolls

Car routes include toll_road, toll_road_m and toll with vignette products and special toll sections. Truck routes report the kilometers subject to the GO toll in routes[].toll.truck_go_km. Avoid tolls or motorways:

.../directions/driving/{coordinates}?exclude=toll
.../directions/driving/{coordinates}?exclude=motorway,toll

Vignette roads remain allowed with exclude=toll. Toll source: ASFINAG, CC BY 4.0.

exclude=motorway and exclude=toll work for driving, driving-traffic and driving-truck.

exclude=ferry closes all ferry links and works for every profile (driving, driving-truck, cycling, cycling-mtb, walking) alone or combined, e.g. exclude=toll,ferry; driving-traffic returns 400. Because this variant is computed without contraction hierarchies, the response takes some tens of milliseconds longer. If a destination can only be reached by ferry (an island, for example), the request returns no route.

Closures

Binding full closures from the traffic reports (EVIS/ASFINAG) are avoided by driving and driving-traffic. The roads concerned are blocked for the route search; routes[].closures_avoided lists the closures that the route without closures would have driven through (id, text, road, category). If a closure cannot be avoided, the route runs through it and routes[].closures_unavoidable lists it. Conditional closures (weekdays, hours in the text) only discourage a road and are not listed. Source: ASFINAG, CC BY 4.0; show the texts unchanged.

curl -s -H "Authorization: Bearer YOUR_TOKEN" "https://api.mapx.at/v1/directions/driving/14.2,48.27;14.45,48.30?overview=false" | jq '.routes[0].closures_avoided'

Voice and banner instructions

With steps=true you can add voice_instructions=true and banner_instructions=true (all road profiles: driving, driving-truck, cycling, cycling-mtb and walking). The format follows Mapbox: each step carries the instructions for the maneuver at its end.

curl -s -H "Authorization: Bearer YOUR_TOKEN" "https://api.mapx.at/v1/directions/driving/15.6256,48.2049;15.3294,48.2272?steps=true&voice_instructions=true&banner_instructions=true&language=en&overview=false" | jq '.routes[0].legs[0].steps[1] | {voiceInstructions, bannerInstructions}'

• voiceInstructions[]: distanceAlongGeometry (meters before the end of the step at which to speak), announcement and ssmlAnnouncement. Announcement distances depend on speed: on motorways 2 km, 1 km and 300 m ahead, on rural roads 1 km, 400 m and 120 m, in town 400 m and 150 m; the last one is spoken without a distance. On foot the announcements come 100 m and 40 m ahead, by bike 250 m and 80 m ahead. The texts follow language (de or en) for every profile. The first step also announces the departure. language=de|en selects the language.
• bannerInstructions[]: primary and optional secondary with text, components[] (type icon for the road number, text for names and destination signage), type, modifier. With destination signage, the destination is the primary text and the road the secondary line.

Isochrones, matrix, matching

// Where can I walk in 5, 10 and 15 minutes?
const iso = await (await fetch("https://api.mapx.at/v1/isochrone/walking/16.3725,48.2085?contours_minutes=5,10,15&access_token=YOUR_TOKEN")).json();

// Travel times from the first point to the others
const m = await (await fetch("https://api.mapx.at/v1/matrix/driving/16.3725,48.2085;15.3294,48.2272;14.2858,48.3069?sources=0&annotations=duration,distance&access_token=YOUR_TOKEN")).json();

The isochrone result is a FeatureCollection of polygons, largest first. Show it with a fill layer; see Isochrone and Matrix. Map matching takes a GPS trace and returns the matched route.

Tour planning

optimized-trips orders up to 25 stops (round trip or fixed start and end). POST /v1/optimization plans tours for several vehicles with capacities and time windows.

curl -s -H "Authorization: Bearer YOUR_TOKEN" -X POST https://api.mapx.at/v1/optimization -H "Content-Type: application/json" -d '{
  "vehicles": [{ "id": 1, "start": [16.3725, 48.2083], "end": [16.3725, 48.2083] }],
  "services": [{ "id": 1, "location": [15.6256, 48.2049], "service": 300 },
               { "id": 2, "location": [14.2858, 48.3069], "service": 300 }]
}' | jq '.summary'

Handle failures

422 means the request is valid but unanswerable, for example no route between the points. 400 carries the faulty parameter in param. Retry 429 after Retry-After seconds. See Errors and limits.

Next

• Directions API, Optimization API
• Traffic: incidents along a route
• Route example