#6087 closed defect (fixed)
Top level "fix warnings" in Validator can delete good information
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | blocker | Milestone: | |
Component: | Core validator | Version: | latest |
Keywords: | validator unnamed ways | Cc: |
Description
If a validator run results in some warnings which are automatically fixable, fixing all warnings at the top level will also "fix" unnamed highways by removing them altogether. But they shouldn't/can't be fixed this way. Clicking on that specific warning category greys out the "fix" button, as it should - it's just when all warnings are fixed at the top level (by clicking on the "Warnings" header first) that they are removed.
How to recreate (JOSM Version 3966):
Create a way with the tag of highway=residential, but don't give it a name. Then create a node in a different place with no tags, and then copy and paste it into the same position (zoom in to the limits of what JOSM allows to ensure it is pasted exactly in the same spot). When validator is run, it will give a few warnings, including "unnamed ways" which is not automatically fixable individually, and duplicate nodes and/or unconnected node warnings (depending on version of JOSM) which is fixable. If the fixable categories are clicked on and the "Fix" button selected, it works fine. But if the top-level "Warnings" is clicked on, and the "Fix" button clicked (which should fix all the fixable warnings but leave everything else alone), it not only fixes the duplicate nodes, but also "fixes" the newly created highway by removing it, which it shouldn't.
I consider this a significant priority since people who haven't noticed this behaviour (which category I have to place myself in until I discovered this) can easily accidentally delete unnamed, but otherwise completely valid ways by asking JOSM to "fix" issues that it can, without even realizing they've done so. A particularly nasty problem if you've downloaded a region to work on that others have spent time tracing out, but not naming, roads.
Attachments (1)
Change History (8)
comment:1 by , 14 years ago
Component: | Core → Core validator |
---|---|
Priority: | major → critical |
comment:2 by , 14 years ago
My method to reproduce (last tested in JOSM 3966):
- Download attached validatorfail.osm file (this is a minimal file to reproduce the bug, and is easily human readable in any text editor)
- Run Validator
- Click on "Warnings" category, then click "Fix" button
- Watch road disappear
comment:2 by , 14 years ago
My method to reproduce (last tested in JOSM 3966):
- Download attached validatorfail.osm file (this is a minimal file to reproduce the bug, and is easily human readable in any text editor)
- Run Validator
- Click on "Warnings" category, then click "Fix" button
- Watch road disappear
comment:3 by , 14 years ago
Priority: | critical → blocker |
---|
This also happens with latest.
The option is not even correct, because you can not solve all warning. It should only be offered if you can fix all but not only a few of the subcategories.
As it can delete lot of work unnoticed by the user it is a blocker for me.
I think this is critical if not even a blocker