On 24 December 2010 17:28, netlatch <[email protected]> wrote: > It wouldn't do any good to post a link to the map. What I am doing is > verifying an input users address and then saving the latitude and > longitude to a database using PHP. I have not had any 620s so far > today so maybe I have no actual problem. But I am afraid that since I > am doing this work on the server side that I may be sharing an IP > address with others and subject to query limitations caused by other > users. I will keep an eye on this. Thanks for your reply.
Without knowing more of your use case, I'm not going to say that's against the rules -- but you could do the geocoding client-side, using something like John's http://maps.huge.info/pinpointaddress.htm. Not only does that distribute the geocoding amongst your users, but it gives them a part in the process by ensuring the geocoding is accurate, lets them have some ownership of the data you are collecting, and satisfies the Terms of Service by ensuring the geocoding is shown on a Google map. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
