[OSM-dev] osmosis with completeWays option behaves strangely

Brett Henderson brett at bretth.com
Fri Jul 22 11:43:46 BST 2011


On Mon, Jul 4, 2011 at 3:45 AM, ant <antofosm at gmail.com> wrote:

> Hi all,
>
> I'm experimenting with osmosis boundig box operations in order to find out
> how completeWays, completeRelations and cascadingRelations behave. Comparing
> the outputs of bbox operations done with completeWays=yes and no,
> respectively, I found something weird. The completeWays output had two
> relations in it that were not there in the default output. I understood from
> the documentation that there should be extra nodes only.
>
> I did:
>
> osmosis --read-xml  file=bremen.osm --bounding-box bottom=53.129883
> left=8.481445 top=53.217773 right=8.569336 completeWays=no --write-xml
> file=nocompleteways
> osmosis --read-xml  file=bremen.osm --bounding-box bottom=53.129883
> left=8.481445 top=53.217773 right=8.569336 completeWays=yes --write-xml
> file=completeways
>
> diff nocompleteways completeways
>
> ...which gives a long list of nodes plus 2 relations, 20144 and 20614.
> Using osmosis 0.39.
> Note also that the bounding box covers an area not fully contained by the
> excerpt.
>

I haven't had a good look at the code, but I'm guessing that the inclusion
of additional nodes in the output means that additional relations are
detected.  In other words, the two relations you've found will probably
refer to nodes that are only selected due to completeWays being enabled.

Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20110722/14ecb748/attachment.html>


More information about the dev mailing list