Copyrights and disclaimers

All the content of this website is mine and can't be used without written authorization.
This website is private and has no relation with my current employer.

News


Follow-up: Why OSM fails to replace official or proprietary base maps in a sustainable way ?

posted 4 Jan 2012 07:56 by Cédric MOULLET

My blog initiated an interesting debate around the 13 points I mentionned. You can read it in the GeoWebForum.ch. I of course disagree with some answers, but I think it's important to discuss these aspects.
Thanks to Stefan KellerMark Wick, Ralph Strauman and Stephan Heuel

Seven 2012 geo predictions

posted 3 Jan 2012 21:03 by Cédric MOULLET   [ updated 3 Jan 2012 21:04 ]

I tried the predictions exercise last year, let's try again ;-)

First 2012 geo prediction: WebGL for 3D portals (or the end of 2d web portals)
Always more 3D data are available. It's now time to publish them and I believe that it's possible to make web portals that combine 2D and 3D. And of course, all this will be supported by HTML5 technologies.

Second 2012 geo prediction: 4D
The world is 4D, GIS data, too.

Third 2012 geo prediction: OpenStreetMap will have a QA process
Data quality is very important and OSM will, hopefully, defines strong processes in order to deliver data with a known quality.

Fourth 2012 geo prediction: all applications in the cloud
Always more applications will be available in the cloud or will have pricing models based on cloud pricing models. And let's hope that public cloud will be used.

Fifth 2012 geo prediction: big geo data & linked geo data
The amount of geo data is always bigger. Location based services or sensors generate huge datasets. The traditional storage, treatments and analysis processes will have to evolve. Linked geo data are very important in order to make the web "geo aware".

Sixth 2012 geo prediction: mobile, mobile, mobile
Applications and services need to be accessible on mobile plattforms. I predict that the "desktop first" paradigm will evolve towards a "mobile first" paradigm since the majority of users will be soon on mobile plattforms.

Seventh 2012 geo prediction: social geo

Facebook or Twitter have offered recently to geo tag the statuses. This is a first step towards a wider usage of geoinformation within social media. Let's call it GeoSoMe ;-)

For a summary of last year:

YES - First 2011 geoprediction: the geospatial mobile year
YES - Second 2011 geoprediction: always more cloud gis applications
YES - Third 2011 geoprediction: the start of the end of heavy clients
NO - Fourth 2011 geoprediction: clear separation between web mapping and web gis
YES - Fifth 2011 geoprediction: geoservices for all and everything
YES - Sixth 2011 geoprediction: REST, RESTFull and (Geo)JSON
YES - Seventh 2011 geoprediction: WebGL will allow fantastic 3D applications

TomTom versus OpenStreetMap

posted 2 Jan 2012 19:53 by Cédric MOULLET

A very well documented article "The Street Network Evolution of Crowdsourced Maps: OpenStreetMap in Germany 2007–2011" compares OSM and TomTom datasets.
Here is the conclusion of this article with aspects that I consider as particularly important in bold:

In this article, we outlined the development of Volunteered Geographic Information in Germany from 2007 to 2011, using the OpenStreetMap project as an example. Specifically, we considered the expansion of the total street network and the route network for car navigation. With a relative completeness comparison between the OSM database and TomTom‘s commercial dataset, we proved that OSM provides 27% more data within Germany with regard to the total street network and route information for pedestrians. On the contrary, OSM is still missing about 9% of data related to car navigation. According to our projection for the future, this discrepancy should disappear by the middle or end of 2012, and the OSM dataset for Germany should then feature a comparative route network for cars as provided by TomTom.
In addition to the route network comparisons, we conducted further analyses regarding topology errors and the completeness of street name information. The results showed that the OSM dataset is not flawless; however, the trend shows that the relative and absolute number of errors is decreasing. Thus, it can also be discerned that not only is new data being added to the project database but also quality assurance is becoming a major factor within the OSM community. Our findings with regard to turn restrictions within the OSM database, which are of critical importance to navigation, showed that based on the current development rate and activity, it will take more than five years for OSM to catch up with the information found in the proprietary dataset used in our analysis. This slower development in comparison to the regular street data collection can have several reasons. It can be based on the fact that turn restrictions cannot be seen in the regular OSM map and thus are less appealing for contributors to be added. Some members might also not be familiar with the importance of turn restrictions for the dataset or do not understand how to implement them correctly.
Overall, a certain trend can be distinguished from our studies, as well as in all other studies conducted to date for the countries that were examined. Preliminary statements and conclusions in the past were that OSM data is sufficient for use with map applications. Today we can say that, at least in countries in which the OSM project is well developed, the data is becoming comparable in quality to other geodata from commercial providers regarding the different factors analyzed in this paper such as temporal accuracy and geometric accuracy.
However, several questions remain and further research is still needed. One important factor that has not been addressed yet is the importance of whether users who contribute data to OSM should also maintain it. Also, it is unclear whether missing attribute information, such as street types or names, if added at a later date, could be analyzed and provided useful insights. So far it seems as if processing within the OSM project is closely related to visual factors, meaning that most data is collected in areas where there are white spots on the map, and thus no information is available. We will investigate specific questions regarding this user behavior in detail in the near future. It will be important to obtain further information on the project‘s participants and data contributors. These are some of the questions that need to be addressed: Are OSM mainly long-term contributors or are most of them so-called ―submarine users‖; that is, do they appear for a short period, add information, and then disappear again? Do members only add new data, or do they also edit existing information? Can an activity radius or area be determined for the participants of the project? Is the administrative area of an entire country completely covered by volunteers of the project or are data contributions by agencies playing a major role in certain areas ?
It will continue to be important to carry out studies about the quality assurance of VGI. Preliminary suggestions have been made on how consistency of compiled VGI data could be achieved by improving quality during production and providing quality metadata for the users [43].

Why OpenStreetMap fails to replace official or proprietary base maps in a sustainable way ? Clarifications

posted 28 Dec 2011 22:56 by Cédric MOULLET

I received a lot of reactions about my previous blog. So here are some clarifications:

- I strongly believe that Open Data is the way to follow, but this way requires to have strong fundations. The goal of this blog was simply to highlight actual problems that can and should be solved. I have also read the nestoria success story, but I would like to see hundred of equivalents stories ;-)
- Yes, I use OSM. I'm a contributor, too ;-)
- Point #1: Cartographers have demonstrated that automatic generalization is, at least for now, not possible. If we take the example of the UK Ordnance Survey, Vector Maps are delivered with two scale ranges: local and district.  Google Maps use various sources of data depending of the scales: GeoBasis DE/DKG, TeleAtlas, Europa Technologies or their own data.
- Point #3: OSM has always a duality between cartography and GIS. The main goal of OSM is to make a map, but GIS data are used to create this map. From a GIS perspective, the fact that "You can assign tags ("keys" and "values") to any point (node), street (way), area (closed ways) or relations (containers of the previous ones). see" creates difficulty when you want to use the data.
- I'm really suprised that points #4, #5 and #6 can be questionned. These are simply facts. A standard GPS is able to measure with a precision of 2 to 5 meters. The digititalization over an orthophoto with a 20 cm resolution is able to measure with a precision of 20 to 50 cm. A professional GPS is able to measure with a precision of 2 to 5 cm.
- Point #8: this is due to two reasons: all is based on three primitives and tags can be associated with everything.
- Point #11: all is in english in OSM. A translation mechanismus should exist is order to be able to obtain localized data.
- Point #13: this is the KISS principle. Currently, it's not very simple (or user friendly) to acquire data for OSM.

Regarding the interesting blog of Steven Feldman, I will extract the sentence: "...for this level of trust to be achieved a more formal approach to quality assurance and a more structured and consistent approach to data capture (content, geography and attribution) will be needed.". I think that the majority of my points goes toward this direction. (small hint to the author: precision and reliability are mathematics concepts used to deliver information about measurments (introduction))

Reactions

@cedricmoullet Rebuttal: wherewithal1.wordpress.com/2010/08/03/why… and wherewithal1.wordpress.com/2010/10/14/tra…

@cedricmoullet Not sure about #3, #8, #10, #11, #13 Thanks for your points, more background about why you say that would be cool :)

@cedricmoullet 1, 7 and 9 are true also for Google Map

@cedricmoullet I can understand your stress -> goo.gl/07sIu but many of your points are valid also for google maps #openstreemap

"Why OSM fails..." by @cedricmoullet: points 1/3/4/5/6/7/8/10/11/13 really? have you ever used it? :) http://bit.ly/tF33HH

@cedricmoullet have you ever used #OSM?

Promotion for own products? Sadly no comments are allowed :( RT @cedricmoullet: Why #OpenStreetMap fails ... http://www.cedricmoullet.com/news/whyopenstreetmapfailstoreplaceofficialbasemapsinasustainableway

@pascal_n @cedricmoullet Some strange arguments, IMO. E.g. 99% of all maps are not multilingual. And what does Map Maker have to do with it?

@cedricmoullet Please allow comments

Not all wrong, unfortunately RT @cedricmoullet Why OSM fails to replace offic. or propr. base maps in a sustain. way ?

@puntofisso I think @cedricmoullet misses the point (pun there) #osm not meant to replace official maps but he shld see j.mp/rqNd15

@StevenFeldman @cedricmoullet as you say, but what strikes me is the number of wrong assumptions about #osm

Really ? Then, how do you account for this http://test.geobretagne.fr/mapfishapp/ and that http://geobretagne.fr/geonetwork/srv/fr/main.home?uuid=c098fa63-42a7-4c56-90de-1c0877ff32a8 ?

Why OpenStreetMap fails to replace official or proprietary base maps in a sustainable way ?

posted 27 Dec 2011 20:49 by Cédric MOULLET   [ updated 27 Dec 2011 20:55 ]

  1. Because it’s not possible to make a map for all zoom levels
  2. Because the finances are not secured on long term
  3. Because the data model is not defined
  4. Because the precision is heterogeneous
  5. Because the reliability is heterogeneous
  6. Because the completeness is heterogeneous
  7. Because it requires attribution
  8. Because the data are difficult to extract
  9. Because noone takes the responsibility about the data
  10. Because it lacks a QA step by an accountable body
  11. Because it is not multilingual
  12. Because first acquisition is fun and data update is boring
  13. Because Google Map Maker Workflow is for the broad public and OpenStreetMap workflow for the map enthusiasts

Having said that, OpenStreetMap is great for rapid maping, has great examples of local success (Best Of OSM) and can be used in a lot of cases.

Two non representative examples: Le Lieu CH or Ragusa IT

Swiss Confederation Informatic Strategy 2011-2015

posted 14 Dec 2011 21:17 by Cédric MOULLET

The swiss confederation has defined it's Informatic Strategy for the next years.
This strategy fits with the current trends like cloud computing, service orientation and mobile.

GeoAdmin Goes Mobile and 24 hours with map.geo.admin.ch

posted 14 Dec 2011 21:13 by Cédric MOULLET

mobile.map.geo.admin.ch

posted 1 Sep 2011 08:42 by Cédric MOULLET

After the OpenLayers code sprint in Lausanne, map.geo.admin.ch offers now all its content on mobile Plattform (Android and iPhone). Don't hesitate to test mobile.map.geo.admin.ch on your mobile device or in Chrome or Safari.
Here is a description of the functions:

24.5.2011 - The Beta of mobile map.geo.admin.ch is live !

posted 24 May 2011 09:58 by Cédric MOULLET

If you own an Android or an iOS device, you can play now with the BETA http://mobile.map.geo.admin.ch. Enjoy, and feedback welcome !

20.5.2011 - Président du PLR de Payerne [FR]

posted 20 May 2011 10:17 by Cédric MOULLET   [ updated 20 May 2011 10:21 ]

.. eh oui: j'ai tout dit ici.

1-10 of 35

Sign in  |  Terms  |  Report Abuse  |  Print page  |  Powered by Google Sites