Maps: Unable to find driving route between two addresses in McAllen, Texas — NO_ROUTE_FOUND error

Hello @Soluzione Support 2 ,

Thanks for linking your support ticket to this thread. We're investigating this route pair through that ticket. Your isolation results are the main evidence: both address-to-road legs work, but routing between the two road points still returns NO_ROUTE_FOUND. The addresses connect to the road network, so the gap is most likely in the car-routing road data between them, such as a road segment marked as not drivable or wrongly restricted. We'll post updates on the ticket, and we'll summarize the outcome here so others with the same problem can use it.

These steps help narrow it down, and there's a workaround below:

1. Make sure you're on the current API. If your URL is /route/directions/json?...&query=lat,lon:lat,lon&travelMode=car, that's the v1.0 format. Retest with POST /route/directions?api-version=2025-01-01, a GeoJSON waypoint body with [lon,lat] coordinates and "travelMode":"driving".
   To verify: the response is GeoJSON route features, not a "routes" array.
2. Find the failing section. Add a midpoint on a main road and route each half separately. Keep halving the part that fails until it's under about 1 km.
   To verify: you end up with one short coordinate pair that fails.
3. Check whether it's a road classification issue. Retry that short pair with "travelMode":"walking".
   To verify: if walking works and driving doesn't, the segment is wrongly marked non-drivable. A similar case was fixed by Microsoft reclassifying the road (Stack Overflow, 2019).
4. Workaround (not a permanent fix): add a via-waypoint on a nearby main road that avoids the failing section. Or catch NO_ROUTE_FOUND and retry with that waypoint added.

You've already shared the failing road-point pair, the 07:12 UTC failure details and the geocoding responses on the support ticket, so there's no need to send those again. To move this forward, please add only these on the ticket:

• the result of the POST 2025-01-01 retest (step 1), with its x-ms-request-id and UTC time
• the shortest coordinate pair that still fails (step 2)
• whether walking mode works for that pair (step 3)

That pins the problem to one road segment so the road data can be checked and corrected.

Thanks,
Suhail Ahamed J.