|
clrc
|
September 6, 2016 at 9:19 am
Hi There,
It appears that the way addresses are being encoded for the maps API is returning incorrect locations. Can you please investigate? I’ve seen elsewhere on the forums this labeled on an API issue, but I don’t believe that is the case.
|
|
Tony
|
September 6, 2016 at 10:28 am
Hi Matthew,
There is a difference between the results returned by the API and maps.google.com
You can feed them the exact same information but the API can then return a different result than regular maps. The format of the address is filterable and can be changed with a custom function if needed.
Do you have an address I can use to see the problem?
|
|
clrc
|
September 6, 2016 at 10:35 am
Please hide address:
— Removed —
When you input the address here, it returns the correct geolocation:
https://developers.google.com/maps/documentation/geocoding/intro
-
This reply was modified 8 years, 1 month ago by
 Tony. Reason: Removed address
|
|
Tony
|
September 6, 2016 at 10:56 am
I get the correct location when I use that address (same location as when using the link above)
Can you provide a link that shows what you see?
|
|
clrc
|
September 6, 2016 at 10:59 am
Please hide link:
— Removed —
The map marks a different building on a different street.
|
|
Tony
|
September 7, 2016 at 1:05 am
Your using a different zip code in your example than you are for the venue you linked to, is that expected?
If I use the same address you have used within the Venue I get the same ‘wrong’ location within both the EE map and the developer link.
If I use the address you provided above as the example, I get the ‘correct’ location shown previously.
|
|
clrc
|
September 7, 2016 at 6:59 am
I have no idea how that was the case, but apologies for the complaint and error and thank you for your time and help.
|
