TomTom and TeleAtlas - Take Two!
So, last time we were thinking through the evolutionary path that TomTom might take now that it owns TeleAtlas. We concluded that TomTom is on the road to becoming a content company, rather than a device company, but that there appears to be an interesting fork in the road ahead.
Content publishing and map database publishing are very similar. You need to collect information, compile it, verify the facts and then publish/distribute the “product”. Completing this cycle in a profitable manner requires managing your costs across the production spectrum. We think this is the road that TomTom is taking and at present, it appears that the company is focusing on the collection and distribution aspects of the process.
Let’s look at the collection process
We all know that TomTom is a big proponent of UGC (See this blog or search for UGC using the Category menu on the left) and that the company would like to find more ways to leverage its MapShare software, to help collect and assist in the compilation of road data. For example, in its recent press release on its new deal with Google, TeleAtlas announced that the agreement provided the company access to the edits of its maps from Google’s community of users.
We could view the data pool that is used to compile TA maps as having two main feeder pipes, each with a variety of inputs. Let’s label one pipe “TeleAtlas” and the other “UGC” (User Generated Content). The TeleAtlas crew collects data by soliciting it from authorities (city, state, national) and uses the data from these sources as a compilation asset. In addition, TeleAtlas utilizes field crews and instrumented vans to collect road and road-related information in the real world. To date, these “TeleAtlas” collection methods have been the mainstay of the databases they produce. The inputs go through a variety of validation processes, some automated, some not, before the data is pronounced fit for use.
There is now a second input pipe to the data input pool made possible by harnessing User Generated Content. As of last February, TomTom claimed, in a press release, that it had received one million map improvements through MapShare and that the MapShare community had over half a million members registered users. Clearly, all of these changes will be supplied to TA, for its use. In addition, TeleAtlas will be able to utilize the changes to its base maps made by Google users, as a second source of UGC. How will these data be verified and will either of these sources materially benefit TomTom/TeleAtlas?
The significant problem in collecting spatial data, is not finding a source of information about roads or navigation attributes, although this is sometimes an onerous task. Rather, the challenge is validating the positional and thematic aspects of the information collected. For example, the “change” data that TA will be provided by Google is unverified. We do not know if the user acted in good faith, or even if the change they made was for the correct location. Although Google has indicated that it uses a variety of techniques to determine “outliers” to identify incorrect or bogus edits, it can be difficult to check the integrity of spatial data without verifying it in the field. In essence, TA will receive a report that says, for example, this address has been moved from here to there. Yes, they will get the coordinates, but the moves of addresses are often based on the user seeing the location on satellite imagery and then changing the location on the map. Source mismatches, anyone?
The field generated aspect of UGC, such as that collected by MapShare (i.e. the correction is tied to a coordinates provided by the onboard GPS) seems to be a more fertile source of corrections that might be spatially accurate. Of course, there is nothing in the MapShare software that will identify errors in the thematic portion of the potential edit. For example, when TA receives the MapShare data, it should know “where” the user meant to alter the data, but not if the information related to the coordinate(s) was correct. In other words, the MapShare data might be a potentially effective pointer guiding TA to locations where the TA database needs improvement, but MapShare will not relieve TA of the burden of checking these facts for themselves. If TA already spends a whole lot of money on map updating, will it spend less when it has to sort through tons of UGC while attempting verify these data? I think the answer is “Yes”, but only if it (or TomTom) can figure out how to harness the potential of UGC, while not drowning in its data volumes.
Conversely, the MapShare information might provide a very slick way of capturing geocoded addresses and thematic data for new businesses and “hot-spots” for particular demographic groups.
The real gold in UGC, however, may lie in tracing the paths (devices or cars as probes) of users while they are driving. How TomTom might do that to advantage TA is something that we will write about next time. The use of traces, while complicated by itself, is part of a larger strategy that ties to product distribution and channels. We will write about that next time as well.
[Editor’s Note: We have implemented an anti-spam method to cull the spam comments from valid comments made using our Comment form. The Comment screen, in addition to the id info, now requires you to answer a simple question, based on a string of words that we present to you. We apologize for making you jump through an extra hoop, but the spammers are killing us. Before we implemented the procedure, we were receiving 400 spam/comments a day – and none of it remotely interesting.]
Posted in Mapping, Data Sources, TeleAtlas, TomTom, User Generated Content, map updating | No Comments »





