Opened 2 years ago
Closed 21 months ago
#5954 closed enhancement (fixed)
Validator: please issue WARNING or ERROR for wrong coastline direction
| Reported by: | skela | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Component: | Core validator |
| Version: | tested | Keywords: | validator, coastline |
| Cc: |
Description
Currently, Validator checks coastline direction (land on the left side, sea on the right side of the line) only in the INFO level, which is not enabled by default.
Errors in coastline data can make rendering tools such as mkgmap --generate-sea misbehave seriously. In my humble opinion, the correctness of modified natural=coastline ways should be checked on every upload.
Attachments (0)
Change History (6)
comment:1 Changed 2 years ago by stoecker
- Resolution set to wontfix
- Status changed from new to closed
comment:2 Changed 2 years ago by skela
Sorry, I fail to see what is error-prone about checking that an island defined as a single way with natural=coastline has the right direction.
On a related note, the coastline checks already seem to take the bounding box into account. I no longer see bogus complaints about unclosed coastline when the unclosed end is outside the bounding box.
comment:3 Changed 2 years ago by bastiK
- Resolution wontfix deleted
- Status changed from closed to reopened
stoecker: can you elaborate?
comment:4 Changed 2 years ago by stoecker
In general there have been too many warnings causing the info level. Maybe we can extract one warning into a higher level, but this needs testing.
comment:5 Changed 22 months ago by simon04
- Component changed from Core to Core validator
Do we expect loads of false positives when raising "Reversed coastline: land not on left side" to the warning level?
comment:6 Changed 21 months ago by simon04
- Resolution set to fixed
- Status changed from reopened to closed
In [4505/josm]:



The info level means that there are many false positives. Checking coastline is very error-prone, so we can't raise the level.