#22815 closed defect (duplicate)
incorrect warning "overlapping identical landuse"
Reported by: | dieterdreist | Owned by: | dieterdreist |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | |
Keywords: | overlapping ways | Cc: |
Description (last modified by )
I got a warning about "overlapping identical landuse" when actually I had 2 landuse polygons sharing 1 way (via Multipolygon). There is no issue with such mapping, rather people should be encouraged to keep landuse polygons small, because it makes maintenance easier and makes it easier to refine the polygons with additional properties. If we encourage people to merge landuse polygons because they are of the same type and touching, we will loose way history (not really "lost", but becomes unaccessible during regular editing), and make it harder to add more detail (because these polygons will have to be split again).
I agree a real overlap would be a problem, but if they just touch, the warning is misleading and (IMHO) does more harm than good.
Example way 1154264886
Attachments (0)
Change History (8)
comment:1 by , 22 months ago
Description: | modified (diff) |
---|---|
Summary: | incorrect warning → incorrect warning "overlapping identitcal landuse" |
comment:2 by , 22 months ago
Summary: | incorrect warning "overlapping identitcal landuse" → incorrect warning "overlapping identical landuse" |
---|
comment:3 by , 22 months ago
Keywords: | overlapping ways added |
---|---|
Owner: | changed from | to
Status: | new → needinfo |
comment:4 by , 22 months ago
interesting, neither do I now. I created the ways and the relations and one of the validator warnings on upload was refering to this way, I right clicked "select" and then "3" to zoom to and it was this way that got selected.
comment:5 by , 22 months ago
Resolution: | → irreproducible |
---|---|
Status: | needinfo → closed |
I just tried with completely new objects (ways and relations) but still do not get the warning. Next time, please, create the bug report with Help -> Report Bug and attach a small example file. Thanks
Closing the ticket. Feel free to reopen if you have found an example.
comment:6 by , 22 months ago
I think this is a problem that was reported before and I also see it from time to time. The problem is caused by java method area.intersect()
which sometimes returns non-empty areas for perfectly correct (multi-)polygons because of rounding issues. I fear there's nothing we can do here.
comment:8 by , 22 months ago
Resolution: | irreproducible → duplicate |
---|
Marked as duplicate of #20054.
Thanks, this ticket was what I head in mind.
I do not get any warning about the way osmwww:way/1154264886
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!