Sorry about the mistake with the JSON array. It was the ftp client that failed to upload the file fully. It works now and I have also added a setTimeout as suggested but now the issue I was worried about at the start has appeared, i.e. the results don't come back in the same order. I can't think of a decent way identify the returned result against the lat/lon I have passed in or the locality name I have in the JSON array.
The only thing I can think to do is extend the timeout and leave it run over night. On Mar 4, 7:11 pm, Mike Williams <[email protected]> wrote: > Wasn't it Denis who wrote: > > >(the new page is live at the previous location) > > 1. Your localities.js file ends with an invalid partial line. The whole > file gets ignored in Firefox, leaving "place" undefined. > > 2. There's a geocoding speed limit. If you try to geocode in a tight > loop, then most of your requests will fail with error 620. See: > http://econym.org.uk/gmap/geomulti.htm > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
