Opened 9 years ago
Last modified 5 years ago
#11982 reopened enhancement
duplicated nodes which is not used in way or relation
Reported by: | didier2020 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core validator | Version: | tested |
Keywords: | duplicated nodes group | Cc: |
Description
validator detect other duplicated nodes (see jpg and osm file) as warning,
for this case , it must be error
Attachments (2)
Change History (9)
by , 9 years ago
Attachment: | Capture-3.png added |
---|
comment:1 by , 9 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
We use the error
severity very rarely, e.g., for coastline errors. For your example, warning
s are generated and the automatic fix works nicely.
comment:2 by , 9 years ago
may i insist ?
orphaned duplicated nodes with the same tag => warning
duplicated way with the same tag => errors
common nodes (without tag) of 2 ways => errrors (duplicated nodes)
comment:4 by , 9 years ago
cool !
as there is a lot of differents warnings, can i chose some do be in top of the list of warnings (mywarnings)
comment:5 by , 9 years ago
i've clone a backend and frontend of osmose to see that there is a lot of errors:
http://dev.osmose.frontend.dirif.info/fr/errors/?item=1230&class=3
comment:6 by , 5 years ago
So, what is an error and what needs an error level and what only a warning level ?
I am always ignoring interval
errors and warnings on bus_stops. And yes I get two warnings for the same issue. In my opinion interval
should never be an error. What does it damage ?
With geometry issues, I usually miss higher levels but in the end errors and warnings are not treated differently, atm.
comment:7 by , 5 years ago
Keywords: | group added |
---|
validator