An update on the JavaScript Maps API v2 deprecation
April 29th, 2013 | Published in Uncategorized
In May 2009, we released JavaScript Maps API v3, rebuilding the Maps API from the ground up with a deliberate focus on reduced latency and increased performance. A year later, on May 19, 2010, v3 graduated from Labs to become the default JavaScript Maps API. JavaScript Maps API v2 was subsequently deprecated and scheduled for shutdown on May 19, 2013.
Over the past 3 years we’ve added numerous additional features to v3, such as elevation, cycling and transit directions, and symbols, and we’ve seen fantastic adoption, but we also recognize that a number of long-standing sites have not yet migrated their applications to v3.
Therefore, we’re extending the deprecation timeline for JavaScript Maps API v2 by six months, to November 19, 2013. On that date, we will attempt to automagically turn remaining v2 maps into v3 maps, by way of a JavaScript wrapper we will deploy. We expect this wrapper to work for most simple maps, but to avoid any last minute surprises we strongly encourage sites to complete their migration to v3 ahead of this date. We have prepared an upgrade guide to help make the migration process as painless as possible.
If you have questions about these changes, Google and the broader Google Maps developer community can help. Please refer to our forum for ways that you can seek support, including the JavaScript Maps API v3 mailing list for non-code related questions or Stack Overflow for code-related questions.
Over the past 3 years we’ve added numerous additional features to v3, such as elevation, cycling and transit directions, and symbols, and we’ve seen fantastic adoption, but we also recognize that a number of long-standing sites have not yet migrated their applications to v3.
Therefore, we’re extending the deprecation timeline for JavaScript Maps API v2 by six months, to November 19, 2013. On that date, we will attempt to automagically turn remaining v2 maps into v3 maps, by way of a JavaScript wrapper we will deploy. We expect this wrapper to work for most simple maps, but to avoid any last minute surprises we strongly encourage sites to complete their migration to v3 ahead of this date. We have prepared an upgrade guide to help make the migration process as painless as possible.
If you have questions about these changes, Google and the broader Google Maps developer community can help. Please refer to our forum for ways that you can seek support, including the JavaScript Maps API v3 mailing list for non-code related questions or Stack Overflow for code-related questions.