On Apr 27, 9:34 pm, Andrew Leach <[email protected]> wrote: > I'd go the other way. You can forget the number stage; that's already > failed. But I'd start at street level and go backwards towards country- > level, because I want the *first* one which works to stop that loop.
You're right, we can forget the number, but after that, if you send a street in the next step, without a city, zip or state, you almost certainly get multiple possible matches. We're under the assumption that the user made some mistake when entering the address, but where is the mistke? in the street name, where there are millions of variations? or in the state name, where there are only 50 possibilities? But anyway, I'll admit that I didn't think it through. ;-) I was just pointing out to the OP that there could be a lot of different useful techniques. -- Marcelo - http://maps.forum.nu -- > [Side comment: "works" is a subjective judgement call, but since the > result includes datafields it should be reasonably easy to discover > whether the result returned matches the address given] > > I don't want to do country, state, zipcode, city, street, then find > street fails and I should have remembered what the city geocode was. > Going the other way, street fails but city works, so I use city and > don't need to do any more. It's more likely that street (or city) will > work, so you shouldn't need to do country, state, zipcode (and maybe > even city), and that will speed up the process. > > Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
