Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread Russ Nelson
On Mar 14, 2009, at 11:31 AM, Sam Vekemans wrote: +1 for that!!! Er, 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

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread MP
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

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread Russ Nelson
I'm not sure I wrote clearly enough, because it seems like you didn't understand what I said. Everything that someone might want to add to the map should, if imported, actually BE in the map, not in a separate database or separate layer. Every editor should show this data to a user when

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread Cartinus
On Sunday 15 March 2009 17:42:26 Russ Nelson wrote: Every editor should show this data to a   user when they go to edit.  Otherwise, if there are things that are   available to a map renderer but not to an editor, how will the editor   know that the things are in the map already? Of course

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread Donald Allwright
Of course the editor should show everything available, but that doesn't mean it couldn't be stored in separate databases or displayed in separate layers. It just needs smarter software. Maybe we could get round this by keeping it all in one database, but adding a separate tag to denote where

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread Russ Nelson
On Mar 15, 2009, at 1:02 PM, Cartinus wrote: On Sunday 15 March 2009 17:42:26 Russ Nelson wrote: Every editor should show this data to a user when they go to edit. Otherwise, if there are things that are available to a map renderer but not to an editor, how will the editor know that the

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread Russ Nelson
On Mar 15, 2009, at 1:27 PM, Donald Allwright wrote: Maybe we could get round this by keeping it all in one database, but adding a separate tag to denote where the data come from? Anyone could use this tag to filter only the data they want, or to remove data from a particular source.

Re: [OSM-talk] Bulk import as a data layer (like gpx currently is)

2009-03-15 Thread andrzej zaborowski
2009/3/15 Russ Nelson r...@cloudmade.com: On Mar 15, 2009, at 1:27 PM, Donald Allwright wrote: Maybe we could get round this by keeping it all in one database, but adding a separate tag to denote where the data come from? Anyone could use this tag to filter only the data they want, or to