No. I am storing the lat long results in the database. The 403 error that I was getting, is during this geocoding process which runs periodically and geocodes addresses and stores results in database for use by the online process to display on map.
On Nov 10, 7:31 pm, "[email protected]" <[email protected]> wrote: > On Nov 10, 3:54 pm, UST <[email protected]> wrote: > > > Oh yes. You are absolutely right. It should be gl. I will make this > > change immediately and see the results. > > > One change I already did is I put a delay of 2000ms between every two > > requests. Now the process runs successfully without the 403 error but > > I do not like the delay as the process is considerably slower. > > Maybe you should rethink your design. Are you geocoding all the > points for display and not saving the results in a database? > > -- Larry > > > I will change to gl and remove the delay and see if it still does not give > > the 403 error. > > > Thanks for your feedback. > > > On Nov 9, 11:46 am, Rossko <[email protected]> wrote: > > > > > Response: '403: Forbidden' for url: 'http://maps.google.com/maps/geo? > > > > q=<address>&output=csv&key=<KEY>&sensor=false&oe=utf8&g1=UK' > > > > What's the g1= parameter? Is it supposed to be gl > > > (GL)?http://code.google.com/apis/maps/documentation/geocoding/index.html#G... > > > > I think Google have recently changed the geocoder to reject bad syntax > > > rather than just ignore it.- Hide quoted text - > > > - Show quoted text - -- 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=.
