Erik Fonselius

I have added a example https://github.com/Fonsan/curvature/blob/3c0f62d03d0e60d89ec7e0b2b290ec654ab9416b/processing_chains/callback_chain_example.py The next step is to express a tree with multiple branches that is supported by callbacks with a minimal memory footprint but would unusable...

Here is a working example of a Fanout solution ``` python class CallbackedProcessor(object): def __init__(self, processor, callback): self.processor = processor self.callback = callback def input(self, arg): # Since processors do...

As I realised here https://github.com/adamfranco/curvature/pull/34#issuecomment-219293457 without a proper abort signal convention by explicitly returning some value like `True`, post processors such as `Head` will not work when moving to callbacks

I think we need to define a way of measuring how much data is loaded into memory before we proceed, otherwise we risk making the wrong assumptions on what parts...

I have worked on this problem a bit more and I think it is prudent to split the problem up into two separate parts: - applying coordinates - joining ways...

I have put in quite a lot of work of creating a coordinate joiner that would exploit the fact that coordinate chunks are sequential by essentially iterating over the way...

I have successfully cut out more than half of Japan `./osmconvert japan-160524.osm.pbf -b="128,30,144,40" --complete-ways --out-pbf | pv > j3.pbf` ``` 854M pbfs/j3.pbf 1.0G pbfs/japan-160524.osm.pbf ``` And `osmconvert` never used more...

> The only thing I can think of is that both the way reading and the coordinate reading involve the PBF, whereas the joining doesn't necessarily need to know about...

@adamfranco I think we should keep _all_ `tags` throughout the whole pipe and provide a post processor that is able to filter them

I think the issue is that the three data points simply are in a straight line. If you imagine a triangle in which the base is equal to the two...