I just generate an XML file with negative ids like: <?xml version="1.0" encoding="UTF-8"?> <osm version="0.6" generator="makePostcodeOSM.py"> <node lat="50.9070538066" lon="-1.39997565144" id="-999999"> <tag k="postcode" v="SO14 0AA" /> </node> <node lat="50.9071275658" lon="-1.39858089334" id="-999998"> <tag k="postcode" v="SO14 0AB" /> </node> ... </osm> and give as a parameter to splitter after the main osm.pbf map data file. Ticker On Sun, 2018-12-02 at 16:02 +0100, Ben Konrath wrote:
Hi Greg,
On Tue, 27 Nov 2018 at 18:21, Greg Troxel <gdt@lexort.com> wrote:
Semi-related, I am carrying a diff to render "boundary=parcel"; I include state parcel boundary data with osm data in splitter. I have no idea how many others want this, but given that parcel data is not in OSM, merging while mapbuilding (or a separate transparent parcel map) seems pretty useful. What I'm doing is not really ok, but I'm just mentioning the concept. I realize this is a bit off-topic on this thread but I'm curious to know your process for combing non-OSM data with splitter. I was just starting a project to add some non-OSM data to my maps but I thought the only way to do this was with osmosis, combining a generated change file with the real data. Is your process documented somewhere? If not, do you mind sharing it here?
Thanks, Ben