> > Based on helpful suggestions, we are now checking for "ROOFTOP" or > "RANGE_INTERPOLATED" results, and this seems to suit our needs.
That is restricting yourself to pretty much exact matches on the address. > > It doesn't need to be perfect, we just need to be able to find the general > area that the location is in. So in fact you do accept inexact results. Not caring if it an exact address match? The two statements seem contradictory? > > I do not think that the API should return a status of "OK" for an address > when the entire street doesn't exist, however. One of the uses for the geocoder, is to allow the user to center the map on their location. One of the reason the street may not exist is simply that 1) it not in googles database yet at all, or 2) there is some typo or some other reason it was not exactly matched. ... in which case getting the 'part' match, of the general area, can be a useful feature - the user can then manually zoom to the right area. Rather than just getting a hard 'fail' and have to start from scratch anyway. Pretty sure there used to be an explicit option, if you would accept part matches, but its probably not reliable. So examining the results to see if they are good enough quality for your usecase is better, than just expecting the geocoder to use some predefined 'quality level' which might or might not match your usecase. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
