On Jan 23, 1:39 pm, pinturicchio <[email protected]> wrote:
> I found two details about using "Google Maps Static API" that could
> seem contrasting:

The Terms of Service *always* take precedence. Where there is an
apparent conflict, the TOS apply first. In fact the FAQ do say "the
Google Maps APIs can now be used in Desktop applications, provided
that they adhere to the other restrictions of the Terms of Service"

Consequently the Static Maps must only be used in a web browser.

> Actually we are planning a non-web application that integrate many
> different contents and we would like to employ a simple call to the
> "Google Maps Static API" to show the location of the user; the
> application will employ a web server of ours acting as a proxy between
> the application and the "Google Maps Static API".
> Is this approach violating some of the "Google Maps Static API" terms?

That shouldn't be a problem in my opinion provided that (a) your
webserver will accept requests from those who aren't using your
application; (b) you use a browser control in your application to
display the map.

One problem you may run into with your current plan is the usage limit
http://code.google.com/intl/fr/apis/maps/documentation/staticmaps/#Limits
-- there is a limit of 1000 unique maps per IP address per day, and if
you're using a proxy all your requests will come from the same place.

You would do better to have your desktop application formulate the
request, submit it direct to Google itself and display the result in a
browser control, and not have a proxy server at all. That way each
client can have 1000 different images per day.

Andrew
not a lawyer
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to