[OSM-talk] Admin borders/separate database

[Simon Poole]

Two remarks:

- I believe that the border matches geographic features is a bit of a
red herring. There are all kinds of different practices over the world
(here for example the borders are very very often drawn not to coincide
with roads, and will run parallel to them at some distance to avoid
fights over who is responsible for maintenance) and I don't think that
using any single one of them is going to help the discussion. In the end
generally geographic features tend to change slowly so ignoring such
linkage is probably not a problem in reality. What is clear that a
novice user does not expect that refining am unrelated feature will
change of break an admin boundary.

- I do not see how filters in editors do anything more to this issue
than make it worse, particularly in the case when the border has been
merged with an other object. Do you make the object immutable? Or do you
simply hide the fact that you are now potentially breaking something (as
JOSM does)?

Simon