Reid, Geocoding is a GIGO process - garbage in, garbage out. If your database is getting failed addresses, then you might want to use these more as clues for cleaning your data rather than tools for selecting the geocoding service. What you are missing, at this point, is how many mis-matched addresses you are getting as completed matches.
My gut feeling, looking at the first two addresses, is that this is a pre E-911 street address. Those aren't guaranteed to be in ANY database. A big part of E-911 was to standardize rural addresses and get them all entered into databases. Prior to E-911, you might have 1953 County Road B2 and 1955 County Road B2 several miles apart and maybe not even on the same side of the street. E-911 address actually encode some of the segment distance into the street number. -Eric Reid Priedhorsky wrote: > All, > > Thanks for the tips. To be clear, what we are trying to figure out is > which geocoding service to use, not which nifty Python/AJAX/whatever > library to use to interact with the service. > > Anyway, here's some of the addresses which seem to be tricky: > > A 1955 county rd b2 w, roseville, mn > B 1955 county road b2 w, roseville, mn > C lake st and hennepin ave, minneapolis, mn > D lake st w and hennepin ave s, minneapolis, mn > > Sadly both geocoder.us and Multimap (via http://www.multimap.com/) fail > on the first two. > > Thanks, > > Reid > _______________________________________________ > Geowanking mailing list > [email protected] > http://lists.burri.to/mailman/listinfo/geowanking > _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
