Hi team,
I am using the Azure Maps Route Directions API to calculate driving routes between two waypoints. I’ve noticed that when I use coordinates from Australia, I consistently get errors or undefined responses, whereas the same API works correctly for other regions.For example, when I use the v1.0 Directions API:
https://atlas.microsoft.com/route/directions/json?api-version=1.0&query=-25.874568266795862,133.0222229003906:-27.01891,136.08636&routeRepresentation=polyline&instructionsType=text&language=en-US&travelMode=car&computeBestOrder=true&routeType=fastest
I get the following error response:
{
"error": {
"code": "400 BadRequest",
"message": "Engine error while executing route request: MAP_MATCHING_FAILURE: Origin (-25.8746, 133.022)"
}
}
I also tried the newer v2025-01-01 API endpoint with the following POST body:
{
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"geometry": {
"type": "Point",
"coordinates": [133.0222229003906, -25.874568266795862]
},
"properties": {
"pointIndex": 0,
"pointType": "waypoint"
}
},
{
"type": "Feature",
"geometry": {
"type": "Point",
"coordinates": [136.08636, -27.01891]
},
"properties": {
"pointIndex": 1,
"pointType": "waypoint"
}
}
],
"optimizeRoute": "fastestWithTraffic",
"routeOutputOptions": ["routePath"],
"maxRouteCount": 1,
"travelMode": "driving"
}
And received this response:
{
"error": {
"code": "BadRequest",
"message": "No routable road could be found near one or more specified points."
}
}
When I perform the same type of request for European coordinates, it works fine and returns the expected route path.
So I wanted to confirm —
- Is this expected behavior for Australian coordinates (perhaps due to limited road network data in certain regions)?
- Or is there any specific way to handle such cases or adjust parameters (e.g., tolerance, snapping, map view) to get valid route results in these regions?
Appreciate any clarification or guidance on this.
Thank you,