Hey Berry-

I think that site looks fine; but look over the new Terms of Service
once it's released (in a month or two from now?).

Re lightweight API-- we're working on it. Please give us credit for
our modularization efforts in the meantime.

- pamela


On Thu, Sep 4, 2008 at 1:40 PM, bratliff <[EMAIL PROTECTED]> wrote:
>
> On Sep 4, 8:17 pm, "pamela (Google Employee)" <[EMAIL PROTECTED]>
> wrote:
>> It just uses the API for the initial image map generation. Once it's
>> generated, you only need: static map, image map, 30 lines of
>> javascript for showing canvas poly rollovers. The election news by
>> state map does *not* load in the JS API.
>>
>> Note that I discussed static maps terms of use with my team yesterday,
>> and I should make it clear that you shouldn't be re-creating the
>> dynamic API using the static API. This is a fuzzy area, but it means
>> you shouldn't be doing stuff like pre-fetching static maps, using
>> static maps as tiles, etc.
>>
>> - pamela
>
> I am not trying to simulate the API - just clicks & rollovers with
> pixel to Lat/Lon coordinate conversions.
>
> Is anything illegal in the following:
>
>    www.polyarc.us/static
>
> Is it legal to place two static maps side by side with their logos
> intact to produce one large static map ?
>
> Of course, with a legal / stripped / light weight subset of the API
> with access to the tiles, the whole issue disappears.  Some
> interesting things could be done like an inspection tool, animation,
> flight simulation, multiple synchronized maps.  I believe the
> development community is anxious to give credit to Google but feels
> constrained by an all encompassing API.
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
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