On Dec 28, 9:55 pm, Karlson <[email protected]> wrote: > > I want use Google static maps in such way. > I gave user "code for insertion" like this "http://mydomaine.com/ > staticmap/536326.gif". My script parse this url, create proper url for > Google static map, send request to Google static maps, receive content > of response and return it to user. In this way I want hide coordinates > of marker that I'll show on map. > > But I am afraid that in one time I'll receive a lot of such requests.
As with all questions of this type, any answer is only personal opinion. You need to satisfy *yourself* of the legality or otherwise of what you propose. Carry on reading and see if the arguments below are convincing... > How I can determine that my case of using Google static maps will be > in suit with "except that you may store limited amounts of > Content ......." and not with "you must not ..... pre-fetch, cache, > or store any Content ..." Those are not mutually exclusive. You *can* pre-fetch, cache and store Content if doing so satisfies the permissions which are given: if it's "improving the performance of your Maps API Implementation [and] you do so temporarily, securely, and in a manner that does not permit use of the Content outside of the Service." The only point of your cache is to thwart the harvesting of coordinates? I reckon there's far too much effort involved for no [or very little] return. Once you have a map with a marker on it, it's not difficult to find the position of the marker using an interactive map and matching the marker position. You won't stop anyone who is determined enough. Your server-side script will be subject to Google's 1000/day limit on getting images, because it's that script (with its static IP address) which is requesting them, not each individual user. Your cache won't help with that because each individual request is only counted once, so there will be no impact on Google's counting whether subsequent requests are served from them or from your cache. Because your cache time is 24 hours, the same as Google's, you don't get any benefit, but I reckon that "temporary" can't really be longer than 24 hours. You need to ensure that your cached images are secure; that you only satisfy requests from your service and not from anyone else. That's possible to do but you shouldn't rely on referer headers to do it because they are not secure. You need to ensure that your cached images can't be used outside a web browser or otherwise in contravention of the Terms of Service. The security issue will probably deal with this. The real killer is that your use of a cache must be for the purpose of improving the performance of your Maps API implementation. Introducing a server-side script can't do that, and in any case you are not trying to improve performance: you are [unsuccessfully] subverting identification of locations. Sorry. I believe the answer is that you should not do what you propose. You should use ordinary static-map URLs. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
