Heading parameter in crossstreet lookup API not working

The heading parameter of the Cross Street Lookup API seems to have no effect.
I was expecting to get the closest crossing in the direction I’m heading but it just returns the closest one regardless of heading. I get the exact same results when not setting the heading at all.

Example:
first point --> latlong: 51.084709, 17.035006 (heading: 188.561996)
Result --> latlong: 51.08458 17.03500
second point --> latlong 51.084324, 17.034912 (heading: 188.561996)
Result --> latlong: 51.08458 17.03500

The second point is already past the crossing but gives me the same results.

Is this a bug?

Hi.

I did a quick checks and it seems that I’m able to receive a different response for different heading value. Can you maybe share your exact calls with all additional parameters which you are using so that we can analyze your particular case in more details?

Regards,
Mateusz

Hi,
thanks for the quick response.
These are the two calls I make:

https://api.tomtom.com/search/2/reverseGeocode/crossStreet/51.084709%2C%2017.035006.json?heading=188.561996&key=*****

https://api.tomtom.com/search/2/reverseGeocode/crossStreet/51.084324%2C%2017.034912.json?heading=188.561996&key=*****

Here’s an image of the map:
grafik
The two red points are the ones requested and the blue one is the location in the response. As the heading is going south there should be another Cross Street location for the lower red point.

Hi.

Sorry for the delay. I think I was able to reproduce your issue and I passed it further to the API team. I’m waiting for their investigation and will let you know about any details.

Regards,
Mateusz