We have observed a huge discrepancy in fetching reverse geo addresses using the following API from Azure subscription.
https://atlas.microsoft.com/search/address/reverse/json?api-version=1.0&countrySet=IN&query=29.9522133333333,78.17232
Resultant Address:
{"summary":{"queryTime":9,"numResults":1},"addresses":[{"address":{"routeNumbers":[],"countryCode":"IN","countrySubdivision":"Madhya Pradesh","countrySecondarySubdivision":"Jabalpur","municipality":"Panagar","country":"India","countryCodeISO3":"IND","freeformAddress":"Panagar, Madhya Pradesh","boundingBox":{"northEast":"23.405549,80.207579","southWest":"23.126200,79.830569","entity":"position"}},"position":"23.188238,79.868942","dataSources":{"geometry":{"id":"879800b0-3eb1-49b8-8c75-05f797918d86"}},"entityType":"Municipality"}]}
Addresses we are getting nowhere near to actual locations on any map (Google, Bing, MapMyIndia). Same latitude and longitude returns actual addresses using Google or MapMyIndia.
Google Maps:Dhobhi Ghat Parking Area, X52C+VW Haridwar, Uttarakhand 249401
MapMyIndia: Haridwar Bypass, Ram Ghat, Haridwar, Uttarakhand. 23 m from Panjabi Vesno Bhojnalaya pin-249401 (India)
Another example (in this case State has changed)
Point: 30.08486 77.80136889
Azure:--Behat--Saharanpur-Uttar Pradesh
Google: NH307-Meerpur-Haridwar-Utrakhand
MapMyIndia: NH 307, Aurangzeb Pur, Bhagwanpur, Haridwar District, Uttarakhand
Please help us in case we are using any wrong API or missing anything. We can have a meeting to discuss our requirements and your suggestions for the same.