[osmosis-dev] --used-node performance and a possible way to improve it

[Peter Körner]

Dear Developers

Am 08.06.2011 13:47, schrieb Frederik Ramm:
> For example, there's "osmconvert"
> (http://wiki.openstreetmap.org/wiki/Osmconvert), a tool that can
> read/write OSM, apply diffs, do bounding box, polygon, and tag
> filtering, and people published benchmarks in the forum where that
> program was almost 5 times as fast as Osmosis. The program is certainly
> not a marvel of software design (6000 lines of rather unreadable C code
> in one source file, and it uses NO LIBRARIES except lz, not even an XML
> parser or a geo library or Protobuf code - all hand-coded)
Whoooo.. What a brave approach! To all developers that don't feel like 
hand-coding pbf reading: take a look at osmium! Building a 
Read-Filter-Write Tool is a matter of some dozens of lines, take a look 
at the osmium_convert tool which does a simple Read-Write but with 
anchor points to add filtering with ease.

And: osmium is fast! I'm able to read a full-history pbf, cut its 
contents into 5 BBoxes (of the size of germany or france) and write them 
back to 5 pbfs within *one hour*

> - but still,
> it seems to have a growing user base because it is fast and can be
> easily installed/compiled everywhere.
Well, yep. Osmium has a wide range of requirements of which most aren't 
really required, but installing them on debian or ubuntu is a 
fire-and-forget thing.

Peter