Re: Google Maps's iframe embeded maps still using API V2?

[Enoch Lau (Google Employee)]

It looks rather like the v2 API but actually doesn't use the v2 API. These iframes should continue to work.

On Thursday, May 9, 2013 1:36:01 AM UTC-7, Paisit Onin wrote:

Hello All,

One of my client use the solution that suggested on this URL http://support.google.com/maps/bin/answer.py?hl=en&answer=72644 

Basically, they search for a location on Google Maps and then click the chain icon to get an iframe code then embedded that code to their site. 

Now I notice that inside the iframe, it still using API v2 so I am not sure what will happen when the V2 really got expired on November 19. Do we have to do anything on our end?

[Nianwei Liu]

Well, this appears to be a sensitive topic. maps.google.com is not using "API" any more, but it's sure based on v2, not v3. to be exact, the version is 2.455k as of today's maps.google.com. https://maps.gstatic.com/cat_js/intl/en_us/mapfiles/455k/maps2/%7Bmain,mod_util,mod_rst%7D.js, and GMap2 and all other V2 objects are right there in firebug's DOM tab. Somehow it seems that Google staff were instructed to avoid this question.

The current official version of V2 is 2.450c, just pushed out a few weeks ago (and broke one of our apps because of closure compiler produced a symbol that clashes). So, SOMEONE in Google is still actively working on v2, and still pushing to new versions despite it's been deprecated, and it's official map.google.com is still use a few version ahead of the official v2 API (e.g 2.455k vs 2.450c)

With the recent postpone of v2 decommission, it appears the acceptance of v3 over v2 is still not there. I think for most v2 users, the reason Google laid out for migration is simply not convincing enough, even the mobile web edition of maps.google.com is still on v2.

[Enoch Lau (Google Employee)]

To tell you the truth, the v2 API and maps.google.com share much heritage, but as of today, they are separate and independently updated. To ensure that v2 continues to function in a changing environment, we sometimes have to make very small changes to it.

If you are using the v2 API, you really should consider migrating to v3 right now, because at the end of the deprecation period, your apps built on top of v2 may stop working, despite our best efforts with our JavaScript wrapper.