IMO, this is how Accuracy should be documented: The Accuracy Level returned by Google Map API queries relates to the precision of the latitude and longitude information returned. The higher the value, the greater the precision. An explanation of each Accuracy Level, along with an example query shown in the braces, is shown here:
0 = A point somewhere in the middle of a continent (Europe) 1 = A point somewhere in the middle of a country (United States) 2 = A point somewhere in the middle of a state / province / region (Michigan, US) 3 = A point somewhere in the middle of a county (Kent County, MI, US) 4 = A point somewhere in the middle of a city (Grand Rapids, MI, US) 5 = A point somewhere in the middle of a postal code. Can only use first 5 characters for US postal codes. (Grand Rapids, MI, 49501,US) 6 = A point somewhere on a street. If a street has multiple segments, runs through multiple postal codes, street direction suffixes, (sw, ne etc.), or changes it's name slightly, such as W. Fulton, Google Maps will return multiple points. (Fulton, Grand Rapids, MI, US) 7 = A point calculated for an intersection. Could be multiple (Fulton and Division, Grand Rapids, MI, US) 8 = A point calculated for an address. (155 Michigan St. NW Grand Rapids, MI) 9 = A point where the geological coordinates have been measured. There will never be more than one point returned. (GRR, US) Observed Google Map Priorities: - Country - State - City - At this point plurality exists between street direction suffix , city, and postal code. The best two out of 3 are used to select the address. Example: For a given street address, if it can exist with two different street direction suffixes (SW, SE), and two different postal codes, and the postal code does not agree with the street direction suffix, there will be multiple locations returned. If the city can disambiguate, making it a 2 out of 3 vote, there will be only one returned. If the city is in the area, but technically invalid for both addresses, it is a tie vote and both locations will be returned. I now have the confidence I need to work with the Google Map API. I know, hopefully, how Accuracy Levels work, what gets passed back for each Accuracy Level, and enough about the decision logic to design something reliable and useful. To increase the robustness of the code, I didn't trust my observations about what get's passed for each Accuracy Level, but rather implemented a try / catch block. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
