Skip to content
C++/Javascript framework for working with OSM files
C++ JavaScript Shell
Pull request Compare This branch is 365 commits behind joto:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



Osmium is a C++ framework for working with OSM data files. Osmium can read OSM
data in XML or binary format (PBF) and can call different handlers for each OSM

Available handlers include:
* Javascript handler (calls Javascript callbacks you provide)
* Multipolygon handler (assembles areas(multipolygons) from relations and ways)
* NodeLocationStore handler (stores node locations and builds way geometries from them)
* Statistics handler (does some general statistics)
* (others...)

Of course, you can also write your own handlers.

There are a few applications that use Osmium in the examples directory.

The osmjs directory contains the osmjs application that calls your Javascript code
which can then work with the OSM data. It can, for instance, be used to convert
OSM data into Shapefiles.

Note that OSM input files must contain objects in the right order for Osmium to
work properly: first nodes, then ways, then relations. Normally OSM files are
sorted this way, but if yours aren't, you can use Osmosis with the --sort
option to do this.


Different parts of Osmium and the applications build on top of it need
different libraries:

boost (several libraries)
    Debian/Ubuntu: libboost-dev

zlib (for PBF support)
    Debian/Ubuntu: zlib1g-dev

shapelib (for shapefile support in osmjs)
    Debian/Ubuntu: libshp-dev

libsqlite3 (for some applications only)
    Debian/Ubuntu: libsqlite3-dev

libgd (for tagstats and nodedensity applications only)
    Debian/Ubuntu: libgd2-xpm-dev

GDAL (for OGR support)
    Debian/Ubuntu: libgdal1-dev

Expat (for parsing XML files)
    Debian/Ubuntu: libexpat1-dev

GEOS (for assembling multipolygons etc.)
    Debian/Ubuntu: libgeos-dev

Google sparsehash
    Debian/Ubuntu: libsparsehash-dev

Google V8 Javascript engine (for Javascript support)
    Debian/Ubuntu: libv8-dev

LibICU (for UTF-8/UTF-16 conversion, only for Javascript support)
    Debian/Ubuntu: libicu-dev

Google protocol buffers (for PBF support) (at least Version 2.3.0 needed)
    Debian/Ubuntu: libprotobuf-dev protobuf-compiler
    Also see

Doxygen (to build API documentation)
    Debian/Ubuntu: doxygen

libboost-test (for tests)
    Debian/Ubuntu: libboost-test-dev

OSMPBF (for PBF support)
    You need to build this first.

You need to either install the Debian/Ubuntu packages (or equivalent for other
distributions) or install those libraries from source. Most libraries should be
available in all distributions. The Google libs (V8, protobuf, sparsehash)
are only available in newer distributions (Ubuntu since Maverick).


Doxyfile    - Needed for building the Osmium C++ docs, call "make doc" to build.
include     - C/C++ include files. All of Osmium is in those header files which
              are needed for building Osmium applications.
osmjs       - Osmium application "osmjs".
osmjs/js    - Example Javascript handlers.
examples    - Osmium example applications.


First you need to (build and) install all the prerequisites.

Osmium is a header-only library, so there is nothing to build for the
library itself.

Call "make doc" in the top-level directory to build the Osmium C++ docs.

Call "make install" to install the include files and documentation.

See "examples/README" for build instructions of the example applications.

See "osmjs/README" for build instructions of osmjs.

Call "make clean" in any of those places to clean up.


There are a few tests using the Boost Unit Test Framework in the 'test'
directory. Go there and type "./" to compile and run the tests.
Many more tests are needed, any help appreciated.


Osmium is available under the GNU LGPL version 3 or later, or - at your option -
the GNU GPL version 3 or later.

See for a good
description of what that means.


Osmium was mainly written and is maintained by Jochen Topf <>.

Other authors:
* Frederik Ramm <> (Multipolygon code, ...)
* Christian Vetter <> (PBF parser)
* Scott A. Crosby <> (PBF format)
* Peter Körner <> (XML and PBF writer, ...)

Something went wrong with that request. Please try again.