When thinking about maintaining boundary imports, there is a further complication in that many boundaries follow other features - that are already mapped with varying degrees of precision.
I can see a case for handling boundaries differently since the OS boundary data is "definitive" - in the sense that it doesn't have a physical existence on the ground, and the OS has responsibility for maintaining it in future. But there are bound to be conflicts where a boundary follows a stream, or another physical feature that has been mapped from GPS, or other sources. Would there be some way of protecting imported boundary data, and subsequently importing updates - while allowing this data to be combined with other features that still need to be edited?
_______________________________________________ Talk-GB mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-gb
