Am 05.11.2013 14:49, schrieb Jochen Topf: > So we have bad data in OSM and you want to fix it by making it harder to > correct. Somehow I don't follow your argument... :-) > > While I do agree that it would be nice to have some kind of "layering" feature > that allows us to aggregate date from different databases, this is a huge > undertaking. It is much more than just adding a different database and let > users change the API URL in their editors. How would you handle the ID spaces > for instance. And it is totally unclear how things that are supposed to be > changed together (think borders following a river or road) are to be handled. > > I suggest we keep the one database and think about how to improve the editors > where needed. The JOSM filtering feature for instance is great to keep things > "pseudo-separate". +1 and I would like to combine it: JOSMs filtering feature is a really great starting point but it could be extended by a "layering filter view" which - defines layers by filters where one at a time can be selected for editing - provides a preset system to allow people to select the "border layer" or the "water layer" or the "highway/road/path infrastructure layer" in an abstract way without having to fiddle around with tag-specific filtering syntax on his own.
Nevertheless there should be some warning structure wether someone changes a highway while moving a node of the boundary "layer" which is connected to both (highway and boundary), so it's not that simple to do, but it's possible and would be a great extension for the future - in JOSM as well as in other editors. regards Peter _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
