Statically linked cross-platform SpatiaLite 4.0 binding for node.js. The goal of this project is to have a completely standalone build of SpatiaLite that doesn't require any system dependencies (no need to
apt-get install ... other than the ones required to build native node.js modules. The result is a consistent build across platforms with a guarantee of functionality and the versions of the dependencies. There are number of ways to get SpatiaLite binaries on the various platforms, but none of them include all of the features in a consistent way. This project contains a complete gyp build system for SpatiaLite - so someone might find it useful for other things outside of nodejs also.
If you're familiar with SQL, this is a great way to get easy access to the power of GEOS, Proj4, and SQL without needing a full PostGIS server.
$ npm install spatialite
This module simply exposes node-sqlite3 with an additional method on the
Database object to enable SpatiaLite. I opted to re-use this awesome library and dynamically load the extension so you can still use the
node-sqlite3 API without SpatiaLite if you like.
Here is a simple example that shows the usage of GEOS-enabled
var sqlite = ;var db = ':memory:';var query = "SELECT AsGeoJSON(Centroid(GeomFromText('POLYGON ((30 10, 10 20, 20 40, 40 40, 30 10))'))) AS geojson;";db;
GEOS_TRUNKflag so all of the latest functions are available:
There's a lot of code in these dependencies and the build scripts are fairly complex. If it doesn't work, submit an issue!
To build the shared library, you will need to first install
$ npm install -g node-gyp
$ node-gyp configure build
Compiling on Windows is a bit more involved. You will need to install these in this order. This should give you a working environment to compile native node.js bindings. The node-gyp repo also has some documentation on getting things working with Windows. It's possible it will also work with VS2012, but it's untested. I use veewee for testing with clean versions of Windows and this process does work. If you have problems, it's most likely something else that's installed conflicting with the build environment. This information was taken from here.
A lot of this was inspired by @TooTallNate's post on embedding dependencies in node modules.
This module is BSD licensed. The dependencies have their own licenses which are available in their directories.