The otherwise well-informed GPS Business News, run by Ludovic Privat is one of the rare industry services that we happily pay for. Besides Ludovic being something like a Rolodex on legs, his broad industry experience fuels insightful analysis. Most of the time at least.
In his last piece and from our decent point of view, Ludovic gets it substantially wrong by titling "Google: building its own map data, step by step - Integration of user generated data into Google Maps gets started in 16 countries".
Why?
The indication Ludovic cites is that "Tele Atlas has been offering (Google) a detailed coverage of Morocco for over 6 months; however, Google is not using it."
Well - nobody knows about the data delivery deal those two have, neither the financials or other
requirements are publicly known. Maybe Tele Atlas' data isn't sufficient from Google's perspective or parts of the Tele Atlas map world are excluded from the deal or whatever legal or technical complication may be around. You know how things may become difficult if two elephants meet.
In fact this is rather isn't a new information nor does it make a point.
We had it for Nairobi, we discussed the rights Map Maker contributers at Google Maps may retain (none) and we shed light on how Tele Atlas would potentially benfit from use generated Map Maker additions besides their own user driven change requests. Finally, O'Reilys infamous Brady Forest provided valuable context giving a clear interpretation and put it all together, much better than we could.
So where's the beef?
There still is a sincere dinstinction between gathering GPS coordinates and serious maps.
Besides all the bells and whistles of wikiesque approaches and OpenStreetMap, there always will be enough headroom for professional mapmakers, comprehensive products and reasonable coverage to substantially distinguish from crowdsourced maps. We encounter the difference each and every day by interacting with datasets from both Navteq and Tele Atlas - and OpenStreetMap and official cadastre sets. There a hilarious omissions on any side and I'll post the best-of in the coming weeks until we launch our hyperlocal map of Germany.
Driving around in streetview cars doesn't generate better maps - it just generates more pixel data that cries for integration. Raster imagery doesn't really make better maps, it only gets you better looking maps. Or, as Dr. Joe Berry puts it "raster is faster but vector is more corrrrector"
Driving around on streets per se generates maps for vehicles (and I won't elaborate on this for now).
Even if The Register was right last year posting "Britain to fall within a year", then the UK should be completely street viewed in autumn 2008:
(...) these boys are at times starting their engines at 7am, and covering up
to 160 miles in a single day. Now, the UK's roads extend around 233,000
miles. If we assume Google has ten black ops vehicles working five days
a week (call it 260 working days a year), covering an average of 100
miles a day, it will take the search monolith less than 12 months to complete its dark task.
This calculation works if the weather is OK. Even in the UK it rains, sometimes. Anyone taking a bet?
Now approximate that calculation to the rest of Europe: you do the math. It's pointless even if you'd want to map only highly populated regions.
Ludovic moves on with "Google is surely harnessing enough data to create navigable maps of these areas." - and again: Google yet isn't in the vehicle navigation business (as Tele Atlas and Navteq are), Google is in the search/find, the people navigation and finally in the eyeball business. Logically, street view imagery is a likely extension of Google's acclaimed mission "to organize the world's information", it is a waypoint, not the ultimate goal.
Besides all that, Google may be "in danger of losing its focus", according to California Assemblyman Joel Anderson who is proposing a new "security" measure that will require Google - and other providers of similar map data - to blur images of schools, churches, hospitals and government buildings.
Anderson's proposed bill would prohibit operators such as Google Earth from making aerial or satellite images of schools, places of worship, medical facilities or government buildings available to the public, unless those images have been blurred. (...) would also ban (...) from providing street view photographs or imagery of those buildings and facilities
Ludovics conclusion might be pointing to the wild:
"Nowadays the question is not IF Google intends to develop its own maps, but better WHEN they will be ready for prime time. "
Collecting unstructured user additions and change requests is one thing that Google seems to handle perfectly - integrating mountains of data points into fully navigable and structured vector databases is a completely different beast and yet unsolved.
Finally, the question is: if user generated maps are to become better than anything else - why doesn't Google just support Cloudmade and its APIs and replace Tele Atlas?
In its meteoric history, Google never produced data, it smartly gathered and aggregated data.
Guess why.