use osmium tool

[missinglink]

heya,

I'd like to suggest using http://docs.osmcode.org/osmium/master/osmium-extract.html instead of osmconvert, it's more modern and has way more options and clipping strategies, plus it lets you cut multiple extracts with a single config.

I have a docker image based off alpine you can play with (based off master): https://hub.docker.com/r/missinglink/osmium/

I would really like it if we could use the smart strategy like they do at geofabrik, the other clipping strategies are not appropriate for data processing and things like geocoding because geometries are clipped and become invalid.

Here's a linting tool I wrote a while back which should be able to validate extracts made with different tools using different clipping strategies: https://github.com/missinglink/pbflint

Some issues I found with the old osmconvert method:

• I saw something: broken boundary relations mapzen/metro-extracts#273
• I saw something: PBF contains geometry outside bbox mapzen/metro-extracts#290

[iandees]

👍 Sounds good. My goal was to get it working adapting the existing system and then we can make improvements like this.

[drewda]

@missinglink @iandees FYI, we're now using Osmium to cut extracts on Interline's OSM Extract service at https://www.interline.io/osm/extracts/ We ran into similar problems with ways and nodes at extract edges, so are now using Osmium's complete_ways strategy.

//cc @irees