osm2obj
Streaming parser from OSM XML to OSM objects
Implements a Node Transform Stream. Takes a readable stream of OSM XML and outputs a stream of objects compatible with Overpass OSM JSON. Also reads OsmChange XML and outputs the same format but with an additional property action
which is one of create
, modify
, delete
. Uses sax-js to work in both node and the browser.
Table of Contents
Install
npm install osm2obj
Usage
var fs = var Osm2Obj = var rs = fs rs
Example Output
// node type: 'node' id: 1 version: 0 timestamp: '2013-09-05T19:38:11.187Z' uid: 1 user: 'gregor' lat: 0 lon: 0 tags: null: 'island' // way type: 'way' id: 3 version: 3 timestamp: '2013-09-05T19:38:11Z' changeset: 49 nodes: 19 20 21 22 26 27 tags: name: 'York St' // relation type: 'relation' id: 1 members: type: 'relation' ref: 1745069 role: 'outer' type: 'relation' ref: 172789 tags: from: 'Konrad-Adenauer-Platz' name: 'VRS 636'
Example: Actual JSON output
var through = var fs = var path = var Osm2Obj = var rs = fs var jsonStream = through jsonStreamvar start = true rs { if !start this else start = false } { this}
API
var Osm2Obj =
var stream = new Osm2Obj(opts)
Create a transform stream with:
opts.coerceIds
- coerce id-type fields (id, uid, version, changeset, ref
) toNumber
(defaultfalse
) - useful for osm-p2p-db where ids can be strings.opts.bounds
- Also parse bounds (defaulttrue
)opts.types
- An array of element types you are interested in, e.g.opts.types = ['node']
(default['node', 'way', 'relation', 'changeset']
)opts.strict
- Be a jerk about XML (defaultfalse
). In strict mode will throw an error if:- XML is badly formatted
- Case of element names differs from spec
- Root node is not one of
osm
,osmChange
,diffResult
- An action element (
create, modify, delete
) appears when the root is notosmChange
- Any element in the XML which is not one of
create, modify, delete, node, way, relation, changeset, bounds, nd, tag, member
Any attribute that is not a valid OSM XML attribute will be ignored (see WHITELISTS
). tag
, member
, or nd
elements without the required attributes will throw an error. The readable side of the stream is in objectMode
.
Parses OsmChange XML. Output objects will have property action
which is one of create
, modify
, delete
.
If a <delete>
block in osmChange XML has an if-unused
attribute, then each object within the block will have a prop ifUnused=true
. The value of the attribute is ignored, as per the OSM API 0.6 spec.
stream.parse(str)
Parse str
and return the result. Will throw any error.
Contribute
PRs welcome. Please follow JS Standard Style. Right now this could do with some tests. If you are feeling ambitious, this could be sped up by using node-expat on node. The interface is similar to sax-js and it should be possible to wrap this to use sax-js on the browser and node-expat on the server using the browserify browser
field
License
MIT (c) 2016, Digital Democracy.