Opened 2 years ago
Last modified 16 months ago
#5867 reopened defect
No longer possible to fix dupe nodes
| Reported by: | NE2 | Owned by: | NE2 |
|---|---|---|---|
| Priority: | major | Component: | Core validator |
| Version: | Keywords: | validator | |
| Cc: |
Description
Load ways 15017070 and 15067773 and run the validator. Rather than "railway duplicated nodes" there's now an entry for "duplicate nodes in two un-closed ways" and the fix button is grayed out.
Attachments (0)
Change History (9)
comment:1 Changed 21 months ago by simon04
- Component changed from Core to Core validator
comment:2 Changed 21 months ago by simon04
- Resolution set to needinfo
- Status changed from new to closed
comment:2 Changed 21 months ago by simon04
- Owner changed from team to NE2
- Status changed from new to needinfo
comment:3 Changed 20 months ago by simon04
See #4445.
comment:4 Changed 20 months ago by stoecker
- Status changed from needinfo to closed
comment:5 Changed 20 months ago by NE2
How about letting me know that you need a new example (which is trivial to find yourself: http://tools.geofabrik.de/osmi/debug.html?view=routing_non_eu&lon=-97.93506&lat=37.41729&zoom=6&opacity=0.98)?
comment:6 Changed 20 months ago by stoecker
- Resolution needinfo deleted
- Status changed from closed to reopened
comment:7 Changed 16 months ago by NE2
- Priority changed from normal to major
Bumping up to major. If I convert a shapefile to .osm using gpsbabel, I get a bunch of dupe nodes. I can't find any way to fix the bloody things!
comment:8 Changed 16 months ago by NE2
I've since found a few very hackish ways involving merging a layer with itself. But it shouldn't be so hard to do something so simple.



Way 15017070 doesn't exist any more. Please provide new test data or close the ticket if it is not relevant any more.