On Jan 25, 12:32 pm, Andrew Leach <[email protected]> wrote: > On Jan 25, 5:17 pm, Anthony B <[email protected]> wrote: > > > have an application where I would prefer to get error code 602 rather > > than a best guess for a good > > address. I am flagging bad addresses for the user (since they are > > input by the user via a file) by putting them in a known geo-location > > to flag them for the user. If the API guesses for me and returns a > > high accuracy guess I can't do this. > > The geocoder does what it does. You might look at the "Significantly > different address" here:http://econym.org.uk/gmap/didyoumean.htm
I am having a similar issue. Sometimes, I would rather it return nothing, or at least indicate that it is just making a wild guess. This is especially a problem since my search box takes both free-text and addresses, and I treat it as an address when it finds something, so it's important that non-addresses are not treated as addresses. http://services.northcarolina.edu/find Examples: Cameron Village => Cameron, Tuckerman, AR 72473, USA Cameron Village Library => Cameron Dr, Norfolk, ON, Canada I think these types of results add little value except the ability to provide false positives. I am currently working on ways to remove wild guesses: If over 3 G_ACCURACY_STREET results are returned, throw those away, or more than 5 G_ACCURACY_SUBREGION+G_ACCURACY_TOWN are returned, throw those away etc. Either the user isn't being specific enough and/or the geocoder is making a wild guess. For INTERSECTION, STREET, and ADDRESS, user must have typed at least three words, or those results are thrown away I wish at the minimum Google would just say which terms are actually in the address and which aren't. -- 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.
