lat and long marker discrepancies between dynamic V3 API and static V2 API

45 views
Skip to first unread message

Al Black

unread,
Jan 6, 2012, 7:41:21 PM1/6/12
to google-map...@googlegroups.com
I have a dynamic V3 map and also about 13 v2 static maps on the one page here: http://www.centurionrunning.com/thames-path-100-2012/aid-stations/

We calibrated on the V3 dynamic map, so that one is correct. I am passing in the exact same lat longs into both the v3 dynamic and the v2 static maps, however the markers are showing in the wrong positions - most of the time the v2 static maps are out by a few 100m. 

Any ideas on what could be causing this and maybe a possible solution? I read that the v2 static api only accepts decimal precision to 6 decimals and have tested this, and the extra precision on the v3 map is not what's causing it. Do v2 and v3 use different geocoding, resulting in different marker positions?

Andrew Leach

unread,
Jan 7, 2012, 6:34:23 AM1/7/12
to google-map...@googlegroups.com
On 7 January 2012 00:41, Al Black <alexle...@gmail.com> wrote:
> I have a dynamic V3 map and also about 13 v2 static maps on the one page
> here: http://www.centurionrunning.com/thames-path-100-2012/aid-stations/

Answered in the Version 2 Group (it's the Static Map URLs)

http://groups.google.com/group/google-maps-api/browse_thread/thread/3771095ab47ec5ce

Reply all
Reply to author
Forward
0 new messages