> One thought that occurs to me is that there will be many, disparate groups > wishing to use OSM to plan stuff, only a very small proportion of which > would eventually become reality. I'm not sure if it would be appropriate > to add these features to the main OSM database. >
I would also agree that it is probably not appropriate to add addition (non-real) data to the main database, as it will make the editor view significantly more cluttered and confused. At present they can achieve the same effect using off line file and merging layers before rendering. To make the process more smooth maybe some (or all) of the following can be implemented: 1) Enable the render to use multiple '.osm' files for rendering, automatically merging or laying onto the output. 2) Enable map-edit tools to handle seperate database connections (on different) layers presumably with different logins. Easier in JOSM I assume, can't even think how Potlatch would cope with this. 3) The use of relations to group proposals together, possibly with some for of automatic cloning of ways/nodes when altered in one proposal but not another. Cheers, Simon _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
