[osmosis-dev] osmosis pipelining troubles

[MERIGHI Marcus]

Hello Andrew, 

andrew at fastmail.net (Andrew Byrd), 2011.12.07 (Wed) 13:50 (CET):
> Rereading your post, it sounds like you want your output to contain
> only simplified ways and points of interest. I think you can get by

"poi-type nodes" that is, nodes with <tag .*/>'s. Or, put differently,
any node that does not consist of <node .*/> (but of <node .*><tag
*/></node>)

> with a much simpler pipeline. Something of this form might do the
> job:
> 
> osmosis \
>   --rx input.osm \
>   --tf reject-relations \
>   --simplify-ways epsilonMeters=N \
>   --used-node outPipe.0=WAYS \
>   \
>   --rx input.osm \
>   --tf reject-relations \
>   --tf accept-nodes amenity=* \

this is too narrow; what about a natural=peak? BUT: I do not want to go
the road of defining every tag I want. And I could not come up with any
way to filter for nodes that contain a <tag .*/>, appart from using
tagtransform to add a silly is_poi=yes and afterwards --node-key for
is_poi. All input welcome...

>   --tf reject-ways outPipe.0=POI \
>   \
>   --merge inPipe.0=WAYS inPipe.1=POI \

pipe WAYS may now contain nodes with tags that are in POI as well.
(because the node in question may be connected to the way and thus
passes --used-node.)
--merge would handle this. So if I do my "used-nodes" thing on input.osm
on the one hand and simplify-ways + used-node on the other, that might
work. 

>   --wx merged.osm
> 
> Hope this helps,

Will tell tomorow, thanks for your input!

Bye, Marcus

> On 12/07/2011 10:00 AM, MERIGHI Marcus wrote:
> >while trying to integrate various processing steps into a rather complex
> >pipeline I have run into troubles. Each step alone seems to work, even
> >more complex arrangements, but not all of them. (Go to bottom of message
> >(3) to see an working example with multiple invocations of osmosis.)
> >
> >The osmosis commands below (1) stop at "FINE: Waiting for task
> >1-read-xml to complete.", probably forever. CPU utilization goes up
> >first and then slowly down to zero, fstat does not show any read
> >activity on the input file (anymore).
> >I have tried to pin down at what point the processing hangs; everything
> >before "--derive-change" works, tested with "--write-null[-change]".
> >
> >The questions are:
> >1) Am I getting something fundamentally wrong about the way osmosis
> >    pipes work?
> >2) Is there any obvious mistake in my parameters?
> >3) Have I hit a bug?
> >
> >(BTW, basicly I am after simplifying ways; but --simplify-ways leaves
> >(now) unused nodes behind; getting rid of them by means of --used-node
> >removes poi-type nodes as well (not used in ways and relations).
> >Therefore I have to go the long way of diffing before- and after
> >--used-node, parse that for "used" (i.e., poi-type) nodes and merge.)
> >
> >Thanks in advance for any pointers!