<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title>Florian Ledermann - maps &amp; code</title>
<link href="http://www.floledermann.com/" rel="alternate"></link>
<link href="http://www.floledermann.com/feed.xml" rel="self"></link>
<id>http://www.floledermann.com/</id>

<updated>2011-10-14T19:08:59+02:00</updated>

<subtitle>Updates for entries on &lt;a href="http://floledermann.com/"&gt;floledermann.com&lt;/a&gt;</subtitle>


<entry>
<title>Efficient Filtering and Conversion of OpenStreetMap Files with Osmium</title>
<link href="http://www.floledermann.com/blog/tech/filtering-and-conversion-osm-files-osmium/" rel="alternate"></link>
<updated>2011-10-14T19:08:59+02:00</updated>
<id>http://www.floledermann.com/blog/tech/filtering-and-conversion-osm-files-osmium/</id>
<summary type="html">
For creating the world maps for Maps Without Borders, I am currently creating thematic extracts of the global OpenStreetMap data, containing for example all motorways or train routes of the world. Processing a full planet dump is a task that will let you face your computer's hardware limitations, even if you have a reasonably powerful machine by general standards. Very simple tasks can, depending on the tools you use, take days for completion. After initial unsuccessful attempts using the standard, Java-based OSM processing tool Osmosis, I discovered Osmium, a C++ library for writing your own tools to work with OSM data.
&lt;p&gt;&lt;a href="/blog/tech/filtering-and-conversion-osm-files-osmium/"&gt;Read more...&lt;/a&gt;&lt;/p&gt;
</summary>
</entry>

</feed>