In my last post, I was asked what the accuracy of the locations in our generated Google Earth files are. Before I divulge that information, I’d like to explain some of the challenges of getting accurately geocoded data. (I’ll get on my soapbox and complain about the state of NWMLS data in my next post).

Now, in partial defense of realtors and the MLS, it is unrealistic to expect perfect data. For example, consumer-level GPS receivers aren’t always as accurate as one might think. This weekend I loaded up Microsoft Streets & Tips 2006 on my desktop computer, hooked up my GPS receiver, turned on GPS tracking , created a GPS trail, and walked away for an hour. An hour later, my map had a line drawing that resembled the type my 3 year old son likes to create. So even if a realtor was to use a GPS receiver, to get a latitude & longitude reading, it’s entirely possible that the measurement would be off by a house or two (or four).

Another problem, is that most digital maps are created with data sold by companies like TeleAtlas or NavTeq. The companies compile their data by driving around previously unknown streets & neighborhoods, with computers & GPS receivers (kinda like how that annoying guy in the Verizon ads, test their network). I should note that in-vehicle navigation systems are more accurate than GPS receivers alone, because the vehicle’s navigation system can also use the vehicle’s steeling wheel position and the speedometer to determine what your location is.

Unfortunately, by the time the Microsoft’s, Yahoo’s and Google’s of the world get their hands on the data, it is at least 3-6 months out of date (and probably closer to 12-18 months out of date by the time it gets on the web or published on a CD). This is a problem because about 25% of the properties in the NWMLS are new construction (where new construction is defined as a property that was built in 2005 or later). Since new construction is often located near new roads, the giants of digital mapping may be unable to help and are always in a position of playing catch up.

Then when the companies convert the raw data into digital maps, they end up using multiple sources of data, and interpolating it into one set of data they are going to use for a map. However, the data sources don’t always agree on where a point of interest is.

For example, Google Earth thinks the top of the Seattle Space Needle is at 47.620367° north latitude & 122.349005° west longitude. Meanwhile, Microsoft’s Virtual Earth, seems to think it’s located at 47.620336° north latitude & 122.348515° west longitude. Now, a few ten thousand-enths of a degree means the difference between the tip of the needle & one of the air conditioning units on the roof (a few yards). But if they can’t agree on where the top of the Space Needle is, it’s likely they aren’t going to agree on where 742 Evergreen Terrace is either. However, a few yards of error is better than a few miles of error (which is what can happen when I use raw NWMLS data)

Because of this, I have to geocode every single property in the database because I don’t trust the NWMLS data. So I to call Yahoo! Maps Web Services – Geocoding API to get a latitude & longitude for everything. Although Yahoo is far from perfect, at least it’s free and try’s harder than the MLS. So without further delay, here is the current geocoding precision of the points on our generated maps.

In closing, I’d like to ask real estate professionals to be as complete and as accurate as possible when submitting listing data to their local MLS. I’d also like to state even if the MLS was accurate, it’s unrealistic to expect prefect geo-coding from imperfect data. If digital mapping companies and GPS technology can’t get it exactly right, a house or two off, is probably as accurate as you can realistically hope for given the current state of the art.

Robbie
Caffeinated Software