[OSM-talk] Osmosis running forever with completeWays=yes?

Frederik Ramm frederik at remote.org
Sun Feb 1 21:55:31 GMT 2009


    (f'up set to osmosis-dev)

Karl Newman wrote:
> Anyway, the tee can choke things up with all the temporary files. It would
> be nice to be able to share the stored node and ways files between tee
> tasks, but I haven't created that infrastructure yet.

It would be even better to have an extended --bp task that somehow takes 
a list of disjoint polygons and uses some kind of point location 
algorithm to determine which node belongs to which polygon. The 
rationale being of course that with the classic --bp/--tee approach, 
each node is duplicated n times and tested against each of the polygons 
which is a waste of time, especially with a large input file and many 
polygons (e.g. split up the US into counties or so).

Does the task and stream model that osmosis uses theoretically support 
tasks where the number of output streams they create is not fixed, but 
dependent on their parameters? So that e.g. a "bp file=a.poly 
file=b.poly" (or "bp files=a.poly,b.poly") creates two entity streams 
and so on?


Frederik Ramm  ##  eMail frederik at remote.org  ##  N49°00'09" E008°23'33"

More information about the talk mailing list