[OSM-dev] complying with google/bing/yahoo geocoding terms of service

Anton Nel anton at lgr.biz
Tue Oct 4 04:54:05 BST 2011


"If that's the case, what are my options for geocoding when OSM is the base map?"
This seems kind of relevant and was also wondering myself, how to go about geocoding for OSM.



This isn't a Google mailing list so you shouldn't expect answers about Google products, but:
On Mon, Oct 3, 2011 at 3:21 PM, Michael Katz <michaeladamkatz at yahoo.com<mailto:michaeladamkatz at yahoo.com>> wrote:
In my OpenLayers application application, the user will have the option of using many types of basemaps: google, bing, yahoo, OSM, plus some custom types.

I see that in the terms of usage for google, bing, and yahoo, it says that geocoding results must be used with the corresponding map (e.g., results from google's geocoding service must be displayed in some way on a google map). I also see they all put a limit on the number of geocoding calls you can make per day.

Two questions about this:

(a) I'm trying to understand how strict the part about using the result on the corresponding map is. For instance, if my application offers all these various map types, including google, is that sufficient for using google geocoding results on *any* of the map types. Or would I have to use google geocoding only when the user has selected a google basemap, bing geocoding when the user has selected a bing basemap, and so on? If that's the case, what are my options for geocoding when OSM is the base map?

In the strictest sense, you are only allowed to use Google's geocoder if you display the results on a Google Maps API (mobile or web), but I have not seen this rule enforced.


(b) I'm trying to understand whether the daily limits on the number of calls to the geocoding service are per machine or per application across all client machines. I think it must be the former, but it's not clear.

It is per API key.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20111004/41ba9326/attachment.html>


More information about the dev mailing list