On Dec 28, 9:17 pm, "[email protected]" <[email protected]> wrote: I said: > > This is important because I get *different* results from getLatLng() > > and getLocations(), ... > > http://www.geocodezip.com/example_geo2.asp?addr1=London,%20England≥... > That query only returns one result for me. You must be doing > something different.
Ok, I'm stumped. I'm passing the string "London, England, Europe", to getLocations(), and I get back: ------------------- 10 destinations found: Europe Rd, Greenwich, Greater London SE18 5, UK London Rd, High Wycombe, Buckinghamshire HP11 1, UK London Rd, Staines, Surrey TW18 4, UK London Rd, Leicester LE2 0, UK London Rd, Bognor Regis, West Sussex PO21 1, UK London Rd, Coventry CV3 4, UK London Rd, Newbury, West Berkshire RG14 2, UK London Rd, Southend-on-Sea SS0 7, UK London Rd, Camberley, Surrey GU15 3, UK London Rd, Merton, Greater London SM4 5, UK ------------------- However, if I pass the same string to getLatLng(), I get one destination, and it's the correct one. But it now dawns on me that the destination in question happens to map to the same as the *first* address in the list. I'll have to check that separately, but I've no doubt that's what's going on now... As for the other point about my running into 620 errors, I checked for that earlier, but I stupidly did the checks in the callback for getLocations while I was still using getLatLng, which wasn't calling my callback--it was using the function closure method because I was still testing this whole confusion over the above errors. So, mea culpa on that count too. I am, indeed, getting 620 errors on the addresses that I *thought* were being unresolved. I suspect that what I'm going to do is create a lat/lng DB for my photos much earlier than I intended--that part will be quite simple. But I was hoping to have the pages do the lookups live, so as to take advantage of map updates as they become available. I didn't think my site would pound it so hard and I could get away with it. In any event, there are still a few outstanding (unaddressed) points I brought up in my post that warrants someone's attention: namely, documentation improvements (links to object definitions), the JSON point, callback params and the like. But I suppose those are really more for google's internal readers. anyway, you've both been helpful. -- 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.
