Interesting, the problem seems to be in the Ruby library that is making the request. Using Nestful as follows...
>> Nestful.get >> 'http://maps.google.com/maps/api/geocode/json?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA&sensor=false' gives the REQUEST_DENIED response, but using curl or open-uri returns the expected response. Are there particular headers that the Google APIs look for before rendering a response? Not sure why it would work in one instance and not the other. Stu On May 4, 7:45 am, Barry Hunter <[email protected]> wrote: > Its explicitly noted that you may cache the results - provided you > only allow the use of the coordinates within the API implementation. > > So geocode once, and store with your results. Just be prepared to > re-geocode every so-often, so that you are only storing the results > 'temporally' - and in particular when/if Gmaps changes mapping > provider. > > On 4 May 2010 06:48, shenry <[email protected]> wrote: > > > > > > > I'm working on adding a map to a website that collect's the website > > members' addresses in a DB, geocodes them to lat/lng, then displays a > > map with markers at each members' location. > > > Ideally I would like to make an API call when the member is saved in > > the DB to generate the lat/lng data once, instead on a per-request > > basis (or even a per-thousand request basis assuming caching or > > whatever.) > > > This isn't allowed by the TOS, though, so what is the best practice in > > this case? Am I correct that the geocoding API must be called from the > > page via JS? > > > I'm looking at having to geocode ~300 addresses at a time if this is > > done when rendering the page, as opposed to doing this 300 times > > *once* if it was just a callback when each member is saved. I > > understand wanting to limit the load on the web service, but it seems > > that (at least in this case) the load is made to be more burdensome > > than if I could call the api from the app and write them to the DB > > once. > > > Let me know what I'm missing, as I'm sure there is a better way to do > > this. This is my first stab at the Google Maps API and have probably > > missed some details that I should've read in the docs. > > > Stu > > > -- > > 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 > > athttp://groups.google.com/group/google-maps-api?hl=en. > > -- > Barry > > -www.nearby.org.uk-www.geograph.org.uk- > > -- > 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 > athttp://groups.google.com/group/google-maps-api?hl=en. -- 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.
