Sounds like you are trying to compare forward and reverse geocoding calls. These will often vary with just about any mapping platform for a whole lot of possible reasons. The coordinates you have for the input address (forward geocoding) appear to be rooftop coordinates (on top of the building) which is actually a fair distance from any road. When those are past into a reverse geocoder, the reverse geocoder snaps them to the closest road segment as reverse geocoders estimate the address of a coordinate based on the street number blocks of a road. In this case there is a home (2298 Marron Rd, Carlsbad, CA 92008) that is closer to the snapped coordinate snapped and since it is closer than the mall address, this home address gets returned by the reverse geocoder as the top result. I've seen this behavior on nearly every single map platform over the past decade.
Why the map data is inaccurate
Tim Li (CN)
0
Reputation points
The address called to the Bing REST service is 33.178244, -117.331757 according to the address 2525 El Camino Real, Carlsbad, CA 92008, but the address queried according to the latitude and longitude 33.178244, -117.331757 is 2298 Marron Rd, Carlsbad, CA 92008, United States
Azure Maps
Azure Maps
An Azure service that provides geospatial APIs to add maps, spatial analytics, and mobility solutions to apps.
832 questions
1 answer
Sort by: Most helpful
-
rbrundritt 20,836 Reputation points Microsoft Employee Moderator
2023-08-14T22:40:44.2133333+00:00