Maybe some of you remember that I conducted a comparison analysis between three OpenStreetMap (OSM) routing engine APIs (CloudMade, MapQuest Open and OSRM) and G**gle Maps API last week. You can find the results in my blog post here. As I mentioned in the article, I wanted to try to do a second analysis with more routing engines.

Thus, I added Bing Maps and two OSM engines (YourNavigation/YOURS and Routino/Roadeeno) to the comparison. All services have a continental coverage with the exception of OSRM. The following table shows an overview of (1) the request-response time of the service, (2) the calculated distance for the test-route and (3) the file size of the service response:

As you can see in the following diagram does the OSM routing engine (OSRM) give the fastest results. A little bit strange is that the Routino/Roadeeno service returns no valid route responses for requests which are longer than 600 km.

The same diagram in a more detailed view:

The routing engines have different ping times (round-trip time). Almost all services have a round-trip time off about 25 ms. You can see the times for each engine in the following diagram:

If you take those ping times into account and use a logarithmic transformation, the result look as shown below:

The above diagram shows in a quite impressive way the results of this comparison that allow the following conclusions: OSRM (OSM) shows the fastest results followed by G**gle Maps (Tele Atlas). Bing (Navteq), MapQuest (OSM) and CloudMade (OSM) are nearly equal in most cases. YOURS (OSM) and Routino (OSM) seem not to be the right choices at least for long route calculations (>600km). Maybe a second comparison with several routes between 10 and 500 km could be an enhancement?

thx @ maɪˈæmɪ Dennis 🙂

Currently I am working on a research paper about the OpenStreetMap evolution of Germany. For the last AGIT conference in Salzburg and the upcoming State of the Map Europe (SotM-EU) conference in Vienna I did a similar analysis about the OpenStreetMap Evolution of Austria. You can see the results in the following posters in English and German:

The OpenStreetMap Evolution of Austria (2007–2011)

Die OpenStreetMap Entwicklung in Österreich (2007–2011)

A further nice visualization of the OpenStreetMap data in Austria for the year 2010, can be found in a blog post by Max Kossatz.

Ok, you want it, you’ll get it! Maybe some of you know the nice website: www.googlefight.com. You can enter two keywords and after that it starts a funny fight between these keywords. Based on the database of “How did you contribute to OpenStreetMap?” I created a similar website where you can set up a “fight” between OpenStreetMap contributors. The following picture shows an example fight:

I am very sure you have some ideas for further fights, don´t you?
“Let´s get ready to rumble!” >>  http://osmfight.neis-one.org/ <<

thx @ Frederik for idea during a talk
thx @ *Fab* for the user-interface
and finally thx @, you know it: maɪˈæmɪ Dennis 🙂

In Salzburg (Österreich) fand dieses Jahr wieder vom 6. bis zum 8. Juli die AGIT statt. Die AGIT ist eine Konferenz für angewandte Geoinformatik, welche bereits seit 1989 stattfindet. Dieses Jahr dürfte sie wohl wieder einen neuen Besucherrekord erreicht haben, mit angeblich knapp 1200 Teilnehmern.

Wie im letzten Jahr gab es auch dieses Jahr am Mittwochnachmittag wieder ein Spezialforum für OpenStreetMap mit insgesamt drei Sessions. Sie bestanden jeweils aus drei Vorträgen über/mit oder wegen OpenStreetMap. Aber nicht nur innerhalb dieses Forums, auch in einigen anderen Sessions, wovon es teilweise insgesamt 10 parallel über die Veranstaltungstage verteilt gab, wurden OSM Daten immer wieder in unterschiedlichen Varianten verwendet. Angefangen von der Verwendung zur Erstellung von Karten, wie auch als Datengrundlage für Routenplaner, die Verwendung von GPS-Tracks zur Ermittlung des Verkehrsaufkommens oder wie in meinem Vortrag, zur Darstellung von Verkehrswarnmeldungen.

Für mich persönlich war es gerade am Mittwochnachmittag interessant zu hören, dass in Wien noch weitere amtliche Geodaten freigegeben werden und andere Ämter, zumindest in Österreich, über die Freigaben ihrer Geodaten nachdenken. Auch im Vortrag vom LVG-Bayern über die Luftbildfreigabe in Bayern, die unter anderem auch für das Abdigitaliseren für OSM verfügbar waren/sind, gab es Aussagen das gerne immer wieder neue Orthopohots freigegeben werden.

Was meiner Meinung nach vor ein paar Jahren irgendwie noch undenkbar war, wird langsam Realität: Behörden in Österreich oder auch Deutschland geben ihre Geodaten frei oder sprechen zumindest offiziell darüber sie zu veröffentlichen!

Ich sehe hier ein wirklich großes Potential gerade für OpenStreetMap im Bereich der Qualitätsvervollständigung, Qualitätsanalyse und vor allem in der immer wieder nachgefragten Qualitätssicherung. Aber nicht nur OpenStreetMap würde davon profitieren, so wie im LVG-Bayern Vortrag von offizieller Seite zu hören, haben auch die Ämter viele positive Effekte durch die Verwendung von OSM Daten bei ihrer Arbeit. Ingesamt also eine absolute Win-Win-Situation? Warten wir mal ab, was sich bis zur nächsten AGIT 2012 in Salzburg noch so alles ergibt …

This article was written in the ICE720 from Munich to Frankfurt, with a delay of 22min.
Thanks for travelling with Deutsche Bahn!

In the past blog post I wrote about the newest changes and encoding techniques that have been implemented in the Open Source Routing Project (OSRM). So I think it is time do a little comparison analysis about the request/response time of several routing APIs. The main question I wanted to answer was: “Is an OpenStreetMap direction service faster than G**gle?” I tested the following direction APIs for cars (fastest): MapQuest, CloudMade, G**gle and finally OSRM. For the analyses I wrote a small Java tool, which measured the time to get a result of a routing-service. I did all tests at home with a “regular” 12kbit/s internet connection. I tested several distance levels and the results can be seen in the following table. It shows the average times of five requests for each route with a delay of 3 seconds between each request/response. Overall I did this analysis three times.

The results are quite impressive. OSRM calculates the fastest route for all five test routes! Unfortunately we do not have any information about the server infrastructure at G**gle, MapQuest or CloudMade but the OSRM engine is running on a virtual server with limited hardware resources. It seems that the CloudMade directions service does not like Paris very much, as can be seen in the following image 😉

I will try to do a second comparison with Bing Maps, YOURS and Routino. So stay tuned …

— Update —

>> The second blog post is here: Comparison of (OSM) routing-engines – Reloaded <<

thx @ maɪˈæmɪ Dennis 🙂

One of the many bottle necks of today’s web services are network latency and bandwidth. While I was working on a research paper, I recognized that G**gle encodes some information when you calculate a route on G**gle Maps. This process reduces, besides the gzip compression, the response from the server. This means that this is a speed improvement for the server client communication besides the zoom-level-generalization. You can read more about the “Encoded Polyline Algorithm Format” and how it works here.

We integrated this nice feature into the code of the Open Source Routing Machine (OSRM) project. The following table shows a few results for some sample routes comparing the old and the new file sizes (@ zoomlevel 18):

And if you are not a numbers person, let us put this in perspective: The fast routes just got faster! And that’s not all. As a second new feature the web frontend of the OSRM has shortlinks for the calculated route now. You can find the link of your route at the route summary. Try it out here: http://map.project-osrm.org/

thx @ maɪˈæmɪ Dennis 🙂

First of all, I really like the following blog post and the idea behind it: “Yes! It is possible to cross Dublin without passing a pub”

It shows the power of crowd sourced geodata (OpenStreetMap) and the skills of some individuals. In the following steps I am going to show you a different way to get to the same result.

The website OpenRouteService.org offers the same functionality to calculate a route. You can avoid certain areas by defining them (just simply draw them) on the map. However, your first step would be to “Search for Points of Interest (POI)” (PUBS), for example in Dublin within a distance of 10 km. The following picture shows the result:

After that you can create several polygons around your pubs resulting in a map with several, “red” areas:

And finally you can calculate a route from almost any point in Dublin. The last image show such a route without crossing a red area or Pub:

However, the original blog post is brilliant !
Or do you want it the opposite way: Search all pubs *along* my route? 😉

thx @ maɪˈæmɪ Dennis 🙂

On Saturday, May 28th members of the OpenStreetMap (OSM) community and employees of the Federal Office of Civil Protection and Disaster Assistance (in German “Bundesamt für Bevölkerungsschutz und Katastrophenhilfe (BBK)”) met for a workshop at Bad Neuenahr-Ahrweiler.

Source: Haiti Crisis Map - OpenStreetMap NL (http://haiti.openstreetmap.nl/)

The main goal of this event, taking place at the Academy for Crisis Management Emergency Planning and Civil Protection (in German “Akademie für Krisenmanagement, Notfallplanung und Zivilschutz (AKNZ)”), was to inform active contributors of the OpenStreetMap community and employees of AKNZ and BBK about OpenStreetMap and crisis mapping.

During the devastating earthquake in Haiti (2010) OSM proved to be a valuable source of up-to-date geodata and partner for international relief organizations. Crisis-Mapping includes but is not limited to e.g. the determination of infrastructure, collapsed buildings, spontaneous camps and more in crisis areas, which can be an important contribution to the orientation of rescue workers on-site. This has also been documented in specific reports by the mass media.

The workshop had 20 participants and started with a reception and short introduction about the AKNZ by Dieter Franke. Subsequently Dr. Michael Judex (BBK) explained the specific tasks of the BBK and highlighted the importance of geoinformation for the protection of citizens or during crisis management.

Stephan Bialonski started the OSM-part during this event with his presentation. Next to some basic information (Main goal of the OSM project, data model, tagging, license) he also introduced the participants to the way the OSM community thinks and works, since these factors differ highly from the working processes of regular administrative and governmental agencies. He specifically mentioned to the participants from the BBK that voluntary active contributors can be best included in their projects as long as the goal of the project is also a goal of the OSM-community.

During the following presentation Werner Kathe introduced the participants to the Humanitarian OSM Team (H.O.T.). “It is a new initiative to apply the principals and activities of Open Source and free data on humanitarian purposes and economic growth”

Special attention had been given to the presentation by Pascal Neis who explained how the operation sequence and processes during two well known OSM-relief operations (Haiti 2010 and Japan 2011) took place. Certain advantages and disadvantages considering the usage of OSM-data during these specific catastrophes were mentioned during this presentation. The participation of the OSM-community, the data collection increase in different crisis areas and several applications based on OSM-data were demonstrated. At the end Pascal showed with an example application how OSM can also be used for preventive crisis planning and organization of rescue forces.

After a lunch break including some intense conversations the employees of the BBK and AKNZ were introduced to OSM-procedures on-site. A practical workshop organized by Bernd Weigelt, Edbert van Eimeren and John Bergenholtz lead through an area of debris on the AKNZ-compound that is being used by the rescue forces for training purposes. The participants collected data about destroyed buildings and ways which shortly after have been imported to the OSM database. This way the participants were able to learn how to add GPS data, fotos taken by digital cameras and areal images to OSM using crisis-mapping specific tags in the OSM-Editors.

Trümmerstraße - Quelle: http://strdbn.posterous.com/osm-community-bonn-trifft-bbk-im-aknz-bilder

The entire event lasted for about six hours and the participants gave a very positive feedback. The open and informal atmosphere during the event allowed for several questions by the participants and showed mutual interests. We would like to thank everyone involved for the successful event.

This is a translation from the German blog post @ blog.openstreetmap.de by Stephan Bialonski & Pascal Neis. Translation provided by maɪˈæmɪ Dennis 🙂

During my Easter holidays I created a web-fronted for Dennis Luxen’s Open Source Routing Machine (OSRM Project). The OSRM project (http://project-osrm.org/) is in my opinion probably the fastest Open Source software which is using data from the OpenStreetMap project. “In contrast to most routing servers OSRM does not use an A* variant to compute shortest path, but Contraction Hierarchies.” You can read a little bit more about Contraction Hierarchies in Wikipedia.

The website that I created contains in its first version an address-search (geocoding) and of course routeplanning. For the geocoding I integrated the Nominatim search from OpenStreetMap. You can find a How-To on the MapQuest-site. Unfortunately the OSRM routing service covers only most parts of Europe for now. The current version of my web-fronted can be found here: http://map.project-osrm.org

Anyway, perhaps some of you would say: “A website with OSM routing? This is nothing new and we actually did have something like that before …” I agree, BUT I think none of them is as fast and can handle as many requests, try it out! Through its really good route calculation performance the route can also be changed or adjusted by dragging the start- and destination point (I think you know this from other websites). The following video shows the great functionality:

WebGUI for Project-OSRM from Pascal Neis

Further does the new website automatically generalize the desired route on the server side for smaller map scales. This reduces the traffic between server and client and less data needs to be visualized by the client which saves system resources. Additionally I created the following feature: If a calculated route contains a segment that has no name, it is going to be displayed in a different color. I think this is a great feature to map missed road names! The next picture shows such a route. You can find the complete sources of the website in the OSRM Sourceforge project folder.

There is a lot of discussion on OpenStreetMap.org about a Routing-Integration. In my opinion there should be two routing options available on the OSM start page. One option that provides a very fast routing such as OSRM and another option that is easy to adjust and configure and is able to work with different OSM tags. A combination of both will probably not be available soon. Bigger companies such as “G****E” offer high performance routing applications to their users. Thus it should also be a desirable goal for the new OSM software to get to the same performance level that the users are familiar with from other websites. I don’t think that an integration of ”Non-Open-Source Routing Software” such as provided by CloudMade or Mapquest is a good idea. It still should be an Open Source App after all. But this limits the selection to OSRM, YOURS, Routino and Roadeeno. For now OpenRouteService is not completely Open Source.

So *if* we add routing to the OSM main website I would vote for a fast-route-planning software e.g. by the OSRM project. Hence we must only search for a preferably configurable solution, what would be your suggestion?

thx @ Dennis L.: Continue with your great work!
thx @ Frederik (Geofabrik) for supporting the OSRM Project with a VM for hosting
thx @ *Fab* for the video
and finally: thx @ maɪˈæmɪ Dennis 🙂

First of all, sorry that I did not create a new stat regarding the Routing View past month. To all the new readers: Usually I create an analysis about the Routing View of the OpenStreetMap Inspector for each month for Europe. You can find more information about the OSM Inspector (OSMI) here. The Routing View within the OSMI “shows problems in the data related to routing and navigation”. You can read more about it here … A direkt link to the OSMI Routing View is here!

However, here are the new stats for May, 2011: we have a total of about 124000 “Unconnected Roads” and about 108000 “Duplicate Ways” (number of duplicate segments). Overall this means that we have about 17000 *new* „Unconnected Roads” errors and only ca. 1300 “Duplicate Ways” have been fixed in Europe. For the past three months we have an increment of about 2850000 new OSM way segments for routing. (May 7th: 34500000, February 20th: 31700000, January 20th: 30600000)

In the following images you can see the amount of errors divided by country and the amount of errors in detail per country for “Europe”:

For this month only a few countries were able to reduce their errors. France (-2200) and Poland (-4800) are ahead of everyone else, so Poland this is your month 🙂 Here you can find the February stat of the OSMI Routing View. Hopefully this is going to be better in the next month :S …

thx @ maɪˈæmɪ Dennis 🙂