I'm guessing that if you remove all the (superfluous) NHD:xxx tags, they
will then become duplicate nodes in waterways, which I think can still
be fixed in JOSM.
On Sun, 2012-05-20 at 19:42 -0400, Nathan Edgars II wrote:
> http://www.openstreetmap.org/browse/way/136738748
> http://www.openstreet
On 5/20/2012 8:22 PM, James Umbanhowar wrote:
I'm guessing that if you remove all the (superfluous) NHD:xxx tags, they
will then become duplicate nodes in waterways, which I think can still
be fixed in JOSM.
Nope - removed all but waterway=* and I have the same problem. I've
noticed "boundary
It looks like many of these are at the ends of ways; perhaps whip up a
quick JOSM plugin that'll look for thee conditions on ways with NHD tags;
perhaps intersected with what the current validator returns; and just fix
em
Then perhaps fix the importer as well.
On Sun, May 20, 2012 at 8:35 PM
On 5/20/2012 9:02 PM, the Old Topo Depot wrote:
It looks like many of these are at the ends of ways; perhaps whip up a
quick JOSM plugin that'll look for thee conditions on ways with NHD
tags; perhaps intersected with what the current validator returns; and
just fix em
The "just fix em" is w
On 5/20/2012 7:42 PM, Nathan Edgars II wrote:
I'm creating waterway relations for major rivers and came across this
import, which has a whole bunch of dupes. I run the JOSM validator and
all it gives is "Duplicate nodes in two un-closed ways - Duplicated
nodes" with a grayed-out Fix button.
Thi
5 matches
Mail list logo
