Good point, boomerbubba. If a visitor views a map which requires, say, 500+ points to be geocoded then isn't it a better experience for the public if we've cached the geocoded results in our database and better for Google as it vastly reduces the number of requests to their servers, plus it doesn't eat up own our daily geocoding allowance?
So long as caching for this purpose doesn't conflict with 10.6 by making the stored coordinates available to anyone as a bulk download, why can't the ToS be more relaxed or understanding about it? How does Google define "temporarily"? Our lives are temporary, they won't last for every and therefore are not permanent. The websites we create by the same measure are temporary. Most won't be around in 5 or 10 years and are certainly not permanent. A quantitative ToS would be more helpful. e.g. caching is permitted up to 1,000,000 points for a maximum of 12 months. At least that would allow developers to write a routine to flush the cache for each point after 12 months knowing that he/she's within the ToS. (Ideally unlimited would be the best license while abiding by 10.6). On Nov 17, 2:45 pm, boomerbubba <[EMAIL PROTECTED]> wrote: > Serious ambiguities remain in deciding how many geocoded points the > API user can cache on the server. The user left to flounder somewhere > between these two prohibitions: > > "10.3 pre-fetch, cache, or store any Content, except that you may > store limited amounts of Content for the purpose of improving the > performance of your Maps API Implementation if you do so temporarily, > securely, and in a manner that does not permit use of the Content > outside of the Service; > ... > > "10.6 use the Service in a manner that gives you or any other person > access to mass downloads or bulk feeds of any Content, including but > not limited to numerical latitude or longitude coordinates, imagery, > and visible map data;" > > Why cannot Google's terms simply state an objective number defining > what "limited" caching of coordinates is permitted? Is it 100 > points, 1,000 points, etc.? Then we can all know what the rules are. > > On Nov 14, 1:05 am, "pamela (Google Employee)" <[EMAIL PROTECTED]> > wrote: > > > Hi developers- > > > We just posted an updated Terms of Service. > > > Blog post > > announcement:http://googlegeodevelopers.blogspot.com/2008/11/posted-by-mickey-kata... > > > New Terms:http://code.google.com/apis/maps/terms.html > > > Updated FAQ:http://code.google.com/apis/maps/faq.html > > > Please read through the terms when you have the chance, as there are > > quite a few clarifications/additions/changes. I understand that there > > may also be sections that appear more restrictive than before, and you > > may have concerns about those. > > > Please post your questions and concerns here, and please know that we > > will be reading through this thread in determining what needs > > clarifying in the FAQ or even in the Terms. But also keep in mind that > > it is the weekend (atleast in our timezone :) and that Terms > > clarifications generally require legal consult, so we will likely not > > have official responses for a few days. > > > Thanks! > > - pamela --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
