{"id":112,"date":"2007-02-23T17:57:14","date_gmt":"2007-02-23T21:57:14","guid":{"rendered":"http:\/\/blumenthals.com\/blog\/?p=112"},"modified":"2007-02-25T21:23:38","modified_gmt":"2007-02-26T01:23:38","slug":"how-accurate-is-google-maps-data","status":"publish","type":"post","link":"https:\/\/blumenthals.com\/blog\/2007\/02\/23\/how-accurate-is-google-maps-data\/","title":{"rendered":"How accurate is Google Maps data?"},"content":{"rendered":"

There has been a recent upsurge in complaints about the accuracy of data that Google uses in Maps. There were recent (false) reports of hijacking<\/a>, of very old & outdated listings not being removed<\/a> and of complete bungling of a medical facility’s listings<\/a>. The increase in complaints is due in large part to the increased exposure of the data in the Local OneBox<\/a> and the resulting increase of awareness on the part of business owners.<\/p>\n

Bill Slawski<\/a> and I have written about the issue of data accuracy as has Greg Sterling<\/a>. It was (is) my contention that the data will improve in accuracy over time<\/a> due to the self interest of the many parties involved. As I noted several months ago, the last step in that process would be getting small businesses directly involved in correcting their own record. That is starting to happen<\/a> with the increased visibility of the Local OneBox<\/a>.<\/p>\n

There are other accuracy issues that are not addressed by my original post. For example: the problems with Google’s heavy reliance on an aglorithmic approach<\/a> to information, the quality of the data that Google uses to create, verify and ultimately delete records, and the lack of easy end user corrections<\/a> of obviously erroneous data.<\/p>\n

That all being said, I wanted to test a data set against on the ground information to see if it was “accurate enough”. To do so I chose the data generated by the query: “Restaurants Olean, NY<\/em><\/a>“. Why? Three reasons: 1)I know most of them by sight, 2)I had a local Chamber of Commerce list of current restaurants and 3)it presented a small enough set that I could manage the information.<\/p>\n

Here is what I found:<\/p>\n

*Google identified 71 restaurants with the query, the Chamber list identified 50.<\/p>\n

*6 of Google’s 71 were in fact closed. Some as many as 3 (maybe 4) years<\/p>\n

*4 of Google’s 71 were either duplicates or not really restaurants<\/p>\n

*11 of Google’s were pubs and bars and in Olean. In this area, they don’t really serve food unless you consider Bud one of the basic food types.<\/p>\n

*Google missed including 3 coffee shops that the Chamber had as restaurants and to its credit found 3 restaurants that the Chamber did not include.<\/p>\n

*Google generally ranked the restaurants reasonably by their local popularity on the Maps listing (with the exception of my favorite that they put at number 10…guess its time to stuff the reviews:)).<\/p>\n

*The ranking and choices for the Local OneBox were very good. The number 1 and number 2 choices are two of the area’s most popular and busiest restaurants. The choice for number 3, Pizza Hut is arguable but a reasonable choice.<\/p>\n

*In the top 10 Map listings there was only one closed restaurant
\n<\/p>\n

The bulk of Google’s data accuracy problems occur below the top 10 Map’s listings. The types of errors range from mildly annoying (dupes & poor categorization of bars as eating establishments) to more serious (the closings). The issue of the closings not being removed in a timely fashion is far more problematic from a users perspective than a duplicate. And it is an area that definitely needs work. End user input would dramatically improve timeliness on this and there would be a strong incentive (for competitors) to report the problem. This probably can’t happen soon enough.<\/p>\n

For the most part, the data works well enough. Why then is this data “acceptable” but we see other data sets that are not?<\/p>\n

One theory I have is that those industries that more aggressively promote themselves through multiple channels are more likely to be kept up to date with Google’s system. The restaurants & hotels are examples. Industries like the health care industry and research hospitals promote themselves through fewer channels and are less likely to have accurate data.<\/p>\n

We need to see how deep and wide the inaccuracies are within the Map product, particularly in the Local OneBox<\/a>. While in my example the quality of the data seems “acceptable” if by no means perfect as I point out elsewhere that is of no consolation to the poor schmuck who suffers the imperfection.<\/p>\n

Other little tidbits of interest:<\/p>\n

*The search “Restaurant Olean NY<\/a>” brings up an authoritative onebox which strikes me as overly agressive.<\/p>\n

*Only one restaurant (Domino’s Pizza) had a coupon. This is probably from ValPak<\/p>\n

*It appeared that many but not all of the national chains had a feed as they had their own category like: Category: Restaurants Subway. Pizza Hut was one that appeared to not have a feed…go figure.<\/p>\n

*Reviews are not that common in the rural area in which we live. Although of the top 20 listings, 17 had reviews, none had more than 6 and most had 1 or 2<\/p>\n

If anyone would like to review my source data, feel free to email me. I thought it too copious and boring to post.<\/p>\n","protected":false},"excerpt":{"rendered":"

There has been a recent upsurge in complaints about the accuracy of data that Google uses in Maps. There were recent (false) reports of hijacking, of very old & outdated listings not being removed and of complete bungling of a medical facility’s listings. The increase in complaints is due in large part to the increased …<\/p>\n","protected":false},"author":262,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-112","post","type-post","status-publish","format-standard","hentry","category-google-maps-google-local"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/posts\/112","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/users\/262"}],"replies":[{"embeddable":true,"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/comments?post=112"}],"version-history":[{"count":0,"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/posts\/112\/revisions"}],"wp:attachment":[{"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/media?parent=112"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/categories?post=112"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blumenthals.com\/blog\/wp-json\/wp\/v2\/tags?post=112"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}