Modify ↓
Opened 5 years ago
Closed 3 years ago
#20707 closed enhancement (wontfix)
Tunnel on suspicious object not thrown for riverbank
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core validator | Version: | |
| Keywords: | suspicious combination tunnel riverbank | Cc: |
Description
When a water area (tagged natural=water) is combined with tunnel=*, the validator throws a "suspicious tag combination" warning. However, this same warning is not reported on riverbank objects (tagged waterway=riverbank).
Test case attached to demonstrate the behavior
Attachments (1)
Change History (6)
by , 5 years ago
| Attachment: | tunnel_suspicious_object.osm added |
|---|
comment:1 by , 5 years ago
| Keywords: | suspicious combination tunnel riverbank added |
|---|---|
| Priority: | minor → normal |
| Type: | defect → enhancement |
comment:3 by , 3 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
With r18519, I believe this can be closed. Do you (@zelonewolf) concur?
comment:4 by , 3 years ago
I agree, this is no longer necessary now that waterway=riverbank is deprecated
comment:5 by , 3 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | needinfo → closed |
Note:
See TracTickets
for help on using tickets.



Test case demonstrating the problem.