Modify

Opened 6 days ago

Last modified 6 days ago

#17320 new enhancement

Allow boundary=* to share an OSM way with highway=*, waterway=* and other ways

Reported by: Hb--- Owned by: team
Priority: normal Milestone:
Component: Core validator Version: tested
Keywords: Cc:

Description (last modified by Hb---)

It is common that an administrative border runs in the middle of a waterway. But if a boundary and a waterway are tagged on the same OSM way, then the JOSM validator warns about "Overlapping ways".

This warning should not show up in case of waterways boundarys.

Attachments (1)

17320.patch (851 bytes) - added by GerdP 6 days ago.
add boundary to default ignore list for overlapping ways test

Download all attachments as: .zip

Change History (5)

comment:1 Changed 6 days ago by GerdP

Hmm, yes, I would go one step further: in my eyes this test should ignore all overlaps ways where an administrative boundary is involved.

Changed 6 days ago by GerdP

Attachment: 17320.patch added

add boundary to default ignore list for overlapping ways test

comment:2 Changed 6 days ago by naoliv

I actually like this warning to find duplicate ways. Is there a way to keep it, even if at informational level?

comment:3 Changed 6 days ago by GerdP

Yes, the patch just changes the default values for preference overlapping-ways.ignored-keys

comment:4 Changed 6 days ago by Hb---

Description: modified (diff)
Summary: Allow boundary=administrative and waterway=* tagged on the same wayAllow boundary=* to share an OSM way with highway=*, waterway=* and other ways

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to Hb---
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.