[talk-ch] boundary and river node merge

tnk at gmx.net tnk at gmx.net
Fri Aug 3 12:19:38 CEST 2012

Hi Simon,

On 03.08.2012 11:30, Simon Poole wrote:
> Please DON'T merge, in fact please do not merge ANYTHING with boundaries from the SwissTopo import.

Could we make an exception for boundary stones like this one


or should I remove it and create a separate node for it?

> - merging the data increases the probability of editing errors impacting the boundaries by a gigantic amount

The biggest source of boundary errors IMHO is their bad visibility in most editors. I don't know how often I find nodes of highways, landuse and other stuff stuck to boundaries. If you don't pay attention and detach these nodes before moving them, off goes your boundary. And there won't even be an visible error, except if you regularly run a bot that checks for shared nodes on boundary ways.

I'm wondering if this kind of DO NOT TOUCH information wouldn't be better kept in a different layer alltogether, at least as some kind of a backup that can be restored on a regular basis. 


More information about the talk-ch mailing list