Download Google Maps Old Version

[Billi Mayhue]

TheMaps JavaScript API team regularly updates the API with new features, bug fixes, and performance improvements. This page describes the versions of the API that are available for use in your applications.

If you do not explicitly specify a channel or version, you will receive the weekly channelby default. If you migrated from the premium plan and did notexplicitly specify a channel or version, you will receive the quarterly channel by default. If youspecify an invalid version, you will receive your default channel.

For most applications, we recommend the weekly channel. This is the most current and up-to-date version and contains the latest bug fixes and performance improvements. You can specify the weekly channel by loading the Maps JavaScript API with the following script tag:

Some applications may benefit from fewer but larger updates, because it gives greater predictability. These applications should use the quarterly channel. Use this approach if you want bug fixes and performance improvements to arrive at an expected time (see quarterly updates). You can specify the quarterly channel by loading the Maps JavaScript API with the following script tag:

Currently, the quarterly channel is version 3.56. During the quarter, this version does not receive new features, bug fixes, or performance improvements. We may, from time to time, introduce security bug fixes into this version.

In mid-August, the quarterly channel will be updated to version 3.57. At that time, the new version will include new features, remove deprecated features, and/or introduce backwards incompatibilities from the previous three months.

Use the beta channel to try out new beta features and changes. Beta featuresare feature complete but might have some outstanding issues (please useIssue Trackerto report issues and provide feedback). The beta channel is not covered by anySLA or deprecation policy, and some changes might not be backward compatiblewith earlier releases.

Use the alpha channel to try out new experimental features and changes. Please use Issue Tracker to report issues and provide feedback. The alpha channel is not covered by any SLA or deprecation policy, and some changes might not be backward compatible with earlier releases. It is for development purposes only and should not be used in production.

Specify a version by number only if you regularly test and update your application. This is because numbered versions are eventually deleted as new versions are created every quarter. You can specify the version number by loading the Maps JavaScript API with the following script tag:

When we update the release channels, it could affect your application. This could occur because your application is relying on undocumented or deprecated features, or because of a bug or bug fix we have introduced.

Once the temporary workaround is in place, you will have time (typically 3 to 6 months) to update your application, so it no longer uses undocumented or deprecated features, and accounts for bugs or bug fixes.

Once per quarter, the Maps JavaScript API team releases a new version.This happens mid-February, mid-May, mid-August, and mid-November.The next update will be mid-August.The new weekly channel will provide version 3.58,and at that time the other channels will be updated.

In mid-August, the weekly channel will be updated from version 3.57 to version 3.58. At this point, the new version will include new features, remove deprecated features, and/or introduce backwards-incompatibilities. You may need to test for these changes when the channel is updated.

Over the course of the quarter, the new version will be updated weekly with new features, bug fixes, and performance improvements. It will not remove deprecated features and will not introduce backwards-incompatibilities.

In mid-August, the quarterly channel will be updated from version 3.56 to version 3.57. Upon update, this version will include new features, remove deprecated features, and/or introduce backwards-incompatibilities from the previous three months. You may need to test for these changes when the channel is updated.

Over the course of the quarter, this version will not include new features, bug fixes, or performance improvements. It will not remove deprecated features and will not introduce backwards-incompatibilities.

A new version 3.58 will be released in mid-August. Upon release, this version will include new features, remove deprecated features, and/or introduce backwards-incompatibilities compared to version 3.57. You should test your application when changing between version numbers.

During the quarter, the new version will be updated weekly with new features, bug fixes, and performance improvements. It will not remove deprecated features and will not introduce backwards-incompatibilities.

This version includes new features, removes deprecated features, and/or introduces backwards-incompatibilities compared to version 3.56. You should test your application when changing between version numbers.

After mid-August, this version will no longer be updated with new features, bug fixes, or performance improvements. It will not remove deprecated features and will not introduce backwards-incompatibilities.

This version includes new features, removes deprecated features, and/or introduces backwards-incompatibilities compared to version 3.55. You should test your application when changing between version numbers.

This version will no longer be updated with new features, bug fixes, or performance improvements. It will not remove features deprecated after this version and will not introduce new backwards-incompatibilities.

This version includes new features, removes deprecated features, and/or introduces backwards-incompatibilities compared to version 3.54. You should test your application when changing between version numbers.

For debugging, use the google.maps.version property to obtain the current version of the Maps JavaScript API in your application. The following code sample writes the API version to the browser console. (For more information about the browser console, see the guide to checking errors in your browser.)

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

If your computer meets the requirements but you still aren't seeing the full version of Maps with 3D, check your browser. Some browsers block the WebGL technology used to make 3D images. To find out which browsers might cause problems, see this list for more information. To see if your web browser can use WebGL, check this website.

Probably just missing a step, but I keep missing it consistently. I have a Traditional versioned dataset in our Portal. The Web Map and layers is configured for sync with a version per user. Creating offline area, editing and syncing all works fine. But when I go to delete the version created for this user I get the error "Operation not allowed on a version with dependent children." I know how to fix this in the SQL Server backend, by manually deleting all the dependent children first. But am I missing a step in a typical offline editing process? thanks!

Posting a final follow-up. I submitted a support ticket with Esri and went all the way through a number of very helpful support departments from Field Maps to Enterprise, finally landing on the SDE / DB team. This is a synopsis of how far we got.

It seems like my process is generally correct, but somewhere along the way when I remove an Offline Area from Field Maps the action to remove the child SYNC versions of the offline editing version is not making it to the back-end and so those child versions are not being deleted.

ArcGIS Pro only displays the main offline edit version, a child of DEFAULT, but does not display the other children of that version. Trying to delete the main offline edit version results in the `160361: Operation not allowed on a version with dependent children.` error, which is recognized but has no solutions, here.

So the only solution we could identify was to access the SDE_VERSIONS table in the back-end DB and manually delete the dependent children of the main offline edit version. So in the screens below version_id = 173 is the main offline edit version that is visible in ArcGIS Pro and which cannot be deleted in Pro. The additional SYNC versions below that are all children of that version and these are not visible in ArcGIS Pro. These versions should be deleted when the Offline Area is removed, but for some reason in my workflow that is not always happening.

So. I manually, and carefully, write out the DELETE statement for each of the child versions, double checking that it is part of the version tree of version_id = 173. Extreme caution here since this example on our dev environment is relatively easy and there are no other versions happening at the same time. In production, it is more likely that there are other versions mixed in among these, so it is an arduous task. Obviously be careful here because DEFAULT is right there! So we felt there was no "smart" SQL statement way to perform this, no range or JOIN, and that each WHERE should be typed out manually and deliberately.

With the versions deleted the, there are no more dependent children of the main offline edit version and that version can and should be removed in ArcGIS Pro only, don't delete it from the DB back-end!

I'd say this situation comes up for me about 80% of the time. So I will continue to test this out. 20% of the time when I remove an Offline Area after offline work is complete and the rec/post have been performed, I am able to delete the main offline edit version in ArcGIS Pro as expected without this back-end work.

3a8082e126