An Azure service that automates the access and use of data across clouds without writing code.
Hi ohad as,
This behavior is expected based on which Azure Maps API you’re calling.
The newer reverse geocoding APIs (date‑versioned) do not currently return speedLimit in the response. Speed limit data is only available via:
- Search Address Reverse v1 using the
returnSpeedLimit=trueparameter, or - The Snap to Roads API, which is the recommended approach going forward if you need reliable speed limit data for GPS coordinates.
If you’re currently using the newer reverse geocode endpoint and not seeing speedLimit, that’s why it simply isn’t exposed there yet. For new implementations, switching to Snap to Roads is the best option, as it’s actively supported and designed for this use case.
Docs for reference:
- Search Address Reverse (v1) with speed limit: https://learn.microsoft.com/en-us/rest/api/maps/search/get-search-address-reverse
- Snap to Roads (recommended): https://learn.microsoft.com/en-us/rest/api/maps/route/post-snap-to-roads
Hope this helps clarify the difference. Do let me know if you have any further queries.
If this answers your query, please do click Accept Answer and Yes for was this answer helpful.
Thankyou!