This document lists requirements that are specific to applications developed with the Geocoding API. Note that use of the Geocoding API is governed by the Google Maps Platform Terms of Service.
Displaying Geocoding API results
You can display Geocoding API results on a Google Map, or without a map. If you want to display Geocoding API results on a map, then these results must be displayed on a Google Map. It is prohibited to use Geocoding API data on a map that is not a Google map.
If your application displays data from the Geocoding API on a Google Map, then the Google logo will be included and may not be altered. Applications that display Geocoding API data on the same screen as a Google Map are not required to provide further attribution to Google.
If your application displays data from the Geocoding API on a page or view that does not also display a Google Map, you must show a Powered by Google logo with that data. For example, if your application displays Geocoding API data on one tab, and a Google Map with that data on another tab, the first tab must show the Powered by Google logo. If your application uses search fields with or without autocomplete, the logo must be displayed inline.
|For use on a light background||For use on a dark background|
The Powered by Google logo is not translated into different languages or localized. It's just an image.
The following zip file contains the Powered by Google logo in the correct sizes for desktop, Android and iOS applications. You may not resize or modify these logos in any way.
If you're using the Geocoding API from a device where the attribution display is not practical, please contact our sales team to discuss licenses appropriate to your use case.
Pre-Fetching, Caching, or Storage of Content
Applications using the Geocoding API are bound by the Google Maps Platform Terms of Service. Section 3.2.3(a) and (b) of the terms states that you must not pre-fetch, index, store, or cache any Content except under the limited conditions stated in the terms.
Note that the place ID, used to uniquely identify a place, is exempt from the caching restriction. You can therefore store place ID values indefinitely. Place ID values are returned in the place_id field in Geocoding API responses.