node package manager


Node.js bindings to Osmium


Fast and flexible Javascript library for working with OpenStreetMap data.

Provides bindings to the libosmium C++ library.

By default, binaries are provided and no external dependencies or compile is needed.

Just do:

npm install osmium

We currently provide binaries for 64 bit OS X and 64 bit Linux. Running npm install on other platforms will fall back to a source compile (see Developing below for build details).

See the tutorial for an introduction. There are some demo applications in the 'demo' directory. See the there. You can also have a look at the tests in the test directory.

If you wish to develop on node-osmium you can check out the code and then build like:

git clone
cd node-osmium

Use make debug to build with debug information. Use make coverage to build with code coverage.

Use make VERBOSE=1 to output compiler calls used etc.

npm install mocha
make test
  • Compiler that supports -std=c++11 (>= clang++ 3.2 || >= g++ 4.8)
  • Boost >= 1.46 with development headers
  • OSM-Binary
  • Protocol buffers
  • zlib

See also the dependency information for the Osmium library.

Set dependencies up on Ubuntu Precise (12.04) like:

sudo apt-add-repository --yes ppa:chris-lea/node.js
sudo apt-add-repository --yes ppa:ubuntu-toolchain-r/test
sudo apt-get -y update
sudo apt-get -y install git gcc-4.8 g++-4.8 build-essential nodejs
sudo apt-get -y install libboost-dev zlib1g-dev protobuf-compiler
sudo apt-get -y install libprotobuf-lite7 libprotobuf-dev libexpat1-dev
sudo apt-get -y install libsparsehash-dev
export CC=gcc-4.8
export CXX=g++-4.8
git clone
cd OSM-binary/src
make && sudo make install

Set dependencies up on OS X like:

git clone
cd mapnik-packaging/osx
export CXX11=true
./scripts/ --with-test --with-program_options
# NOTE: in the same terminal then run the build commands 
# Or from a different terminal re-run `source` 

node-osmium is available under the Boost Software License. See LICENSE.txt for details.

Please open bug reports on You can ask questions on the OSM developer mailing list or on OFTC net IRC channel #osm-dev.

  • Dane Springmeyer (
  • Jochen Topf (