Modify ↓
Opened 3 years ago
Last modified 3 years ago
#22147 new enhancement
For waterway start node avoid "Way end node near other way" warning
Reported by: | Hb--- | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | tested |
Keywords: | template_report | Cc: |
Description
Even when one waterway begins in close proximity to another waterway the warning "Way end node near other way" should not appear.
The current rule produces to much false positives.
This rule seems unnecessary for waterways anyway because the end nodes of waterways are checked against the "Waterway ends without connection to another waterway or direction of the waterway is wrong." rule.
Attachments (0)
Note:
See TracTickets
for help on using tickets.
Please give examples for false positives.
I thought about this as well in areas where I mapped waterway=ditch using aerial image only, but I decided to keep the test as is because it is very unlikely that ditches end without a connection to other waterways, typically a short tunnel=culvert part is missing.
Besides that waterway=ditch is ignored by the test which produces the "Waterway ends without a connection ..." message.