Filed under Geocoding

on Geocoding – (Part 2 Building an Evaluation DataSet)

In essence, an ideal address geocoder will parse, normalize, and geocode an address, which can be of very flexible format. The normalized and geocoded result should follow some standard (USPS standard for address normalization is a pretty well developed standard, which I think, is the de facto standard for address geocoding). The expected output of geocoding should include not only lat, long, but also precision. ThereĀ  could be some additional spatial information, such as county or MSA this address belongs to, that might be useful for certain applications. There might also be fixing of missing zipcode, misspelled street, city, or state names, depending on how lenient/tolerent you want the geocoder to be.

 

Of all of these complicated software development demand/goals, where do you start?

 

You start with building an address list

Continue reading

On Geocoding (part 1 – definition)

=What is Geocoding=

More than once have I received the same response to a discussion related to geocoding :” hold on for a sec, what is geocoding again?”. To which I response with the same definition you can find on wikipedia: “geocoding is the procedure to translate addresses into lat/lons (wiki), along with a accuracy/precision/confidence, so that you can pin it to a map, as well as know how reliable that pinpoint is.” There are a number of web services that can make this job very easy for you. including google, bing, yahoo, and if you want to develop a geocoder yourself, a list of resources might be helpful. However, a more thorough and modern definition of geocoding requires further discussion. In my opinion, geocoding has been too narrowly defined as pinning addresses. People’s thoughts on “geocoding”, once related to “putting addresses on a map”, would be, “Oh, that’s useful; shouldn’t that be a simple task?”, There are at least the following 3 point that is worth noting when talking about geocoding:

Continue reading