This is also as much a UI problem & solution as a technical one. Cascading geocoding, and allowing users (when users are present) to select from a list of options, allow for corrections, and best of all, provide the correct answers for you to store and use next time - is the best solution.
On Mon, Jun 2, 2008 at 3:59 PM, pamela fox <[EMAIL PROTECTED]> wrote: > GeoKit provides fail-over mechanism for using different services: > http://geokit.rubyforge.org/ > > On Mon, Jun 2, 2008 at 12:51 PM, Eric Wolf <[EMAIL PROTECTED]> wrote: >> Hmmm... Then maybe you need to 'cascade' through different services our give >> the users clues on how to format their address. >> >> Interesting, Google gives a location for 1955 Country Rd B2 W, Roseville, >> MN. >> >> -Eric >> >> On Mon, Jun 2, 2008 at 1:45 PM, Reid Priedhorsky <[EMAIL PROTECTED]> wrote: >>> >>> Eric B. Wolf wrote: >>> > 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. >>> >>> Sadly we don't have that luxury -- the addresses are supplied by users >>> and geocoded immediately. (Address A is from a business' website.) >>> >>> :/ >>> >>> Reid >>> _______________________________________________ Geowanking mailing list [email protected] http://lists.burri.to/mailman/listinfo/geowanking
