[OSM-dev] osmconvert bounding polygon

[Stephan Knauss]

Hello Brad,

On 09.06.2021 00:50, Bradley Kleiboer wrote:
> I have encountered a bug with osmconvert (version 0.8.7) with regards to 
> cutting out a polygon (a .poly file) from map data.

Have you tried with a recent version?
http://m.m.i24.cc/osmconvert.c
// osmconvert 2020-03-31 14:20
#define VERSION "0.8.11"

the version you are using is more than four years old.
// osmconvert 2017-03-30 19:00
#define VERSION "0.8.7"

The diff is huge and it touches cutting code:
https://gitlab.com/osm-c-tools/osmctools/-/commit/3b8332f87f1fbef904b88676ab15cca676e353c3


If your issue still exists with a recent version then it would help to 
have some additional details of how exactly it is failing.


> After running the command there are small bits of map data outside of 
> the bounding polygon that are not removed and I was wondering if anyone 
> has seen this behaviour before.
> Here a sample of the command I am running:
> osmconvert \
>          --verbose \
>          --drop-author \
>          --drop-version \
>          --complex-ways \
>          --complete-ways \
>          --out-o5m \
>          -B=sample_polygon_file.poly \
>          -o=output_file.o5m \
>          input_file.pbf

How big are your files? Would it be possible to reproduce the problem if 
you only provide the area where unexpected data remains?

How far outside of the polygon is that remaining data? Is that data part 
of a polygon within the area or otherwise related?

As you did not mention, I put Markus on this mail to have him aware.
See help: "Please send any bug reports to marqqs at gmx.eu"


Stephan