[OSM-talk] Boundary editing (was Zero tolerance on imports)

Ed Avis eda at waniasset.com
Sun Mar 6 21:09:06 GMT 2011


Toby Murray <toby.murray <at> gmail.com> writes:

>Basically, there is ALWAYS a node whenever one TIGER feature crosses
>another, regardless of what kind of feature it is. This leads to
>duplicate nodes sitting on top of each other which the various
>validators complain about. So people tend to merge them to appease the
>validator which is often not the right thing to do. For example, I've
>been working in the Kansas City area a lot, expanding roads to dual
>carriageways. When a boundary is merged with a road and I move the
>carriageway, the boundary is now wrong and must be un-merged and
>re-centered between the carriageways.

Perhaps the answer is to remove some of the spurious nodes which were
automatically added, when they are at the intersection of two straight lines
(in other words, when removing the node would not change the path of any ways
that currently include it).

Certainly having duplicate nodes on top of each other is asking for trouble.
If there's no need for a node to be there, better not to have it.

Of course, such a cleanup of bogus TIGER nodes would itself be a bulk edit and
would need to be checked very carefully and perhaps tried on a small area first.

-- 
Ed Avis <eda at waniasset.com>




More information about the talk mailing list