Well, I thought we would have one layer per each mass import (so you can look at what was imported) - one layer for TIGER import, one layer for AND import, etc ... and the data would ge trimported both in that special layer and in ordinary layer, where everybody can edit it.
In future, we can have layers even at different servers not operated by OSM (for things that are not exactly within scope of OSM map), like layers with wifi hotspots, etc ... Technically, these layers will merely redirect to another server. Martin > Errrrr, no. Anything that someone might ADD to the map should be, if > imported, in the same place. Otherwise, someone will fire up their > editor, not see the data that already been imported, and start to add > it. No better way to piss off a volunteer than to waste their time. > > Yes, there are problems with this approach. We need to solve them, > not run away from them. We'll just create worse problems if we try to > avoid solving this problem. We ALREADY have to deal with it with the > TIGER import. Neither that data, nor the edits made to it, are going > to be exiled from the database into this proposed "bulk import data > layer". > > -- > Russ Nelson - http://community.cloudmade.com/blog - > http://wiki.openstreetmap.org/wiki/User:RussNelson > r...@cloudmade.com - Twitter: Russ_OSM - > http://openstreetmap.org/user/RussNelson > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk > _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
