400 Bad Request on one specific address

REST APIs
#1

The following address can not be used as destination in the routing api.

Bosboomstraat 1
3582 KE Utrecht
(in the Netherlands)
This address has (according to the BAG) the coordinates: 52.08156123 , 5.13827178

The call to
https://api.tomtom.com/routing/1/calculateRoute/52.07157633,5.09082824:52.08156123,5.13827178?key=<my_key>
results in a “HTTP/1.1 400 Bad Request” error: Engine error while executing route request: NO_ROUTE_FOUND

This address as origin and all other addresses are no problem. It is just this address as destination.

#2

It looks like a data problem. Can you report this via Map Share reporter?

1 Like
#3

I did. The status is now ‘accepted’. The problem is not (yet) solved.

#4

The final status should be “fixed”. So we need to wait till it gets this status + some time to propagate new data.

#5

The status is now “fixed”. Waiting for the data to propagate…

#6

Still waiting for the data to propagate…

#7

fixed (for the second time). Still waiting for the data to propagate.

#8

Still waiting for the data to propagate. No response on support ticket.

#9

Still waiting for the data to propagate. Still no response on support ticket.

#10

I have identified your report and I see that it was partially fixed. I created an internal ticket to fix this issue. I’ll let you know once I have more info.

#11

Can you check now? I just checked at MyDrive and it looks that it is now possible to calculate a route to this address.

#12

I’m sorry. No route found. Can you check this link?
https://api.tomtom.com/routing/1/calculateRoute/52.07157633,5.09082824:52.08156123,5.13827178?key=<my_key>
Of course, with your api-key.

#13

It seems to be a difficult problem, taking months to solve…

#14

Still no solution … after such a long time …