On 04/25/2011 07:57 AM, Serge Wroclawski wrote:
I rarely think adding something good to a bad idea but since we're
already down the rabbit hole...
On Mon, Apr 25, 2011 at 5:40 AM, Frederik Ramm<[email protected]> wrote:
Hi,
Jaak Laineste wrote:
What about following approach:
a) ban external source imports to the main database
b) create new separate solution (layer, server, API, whatever fits) for
all the imports.
I think that is the way forward. If your data has special requirements, then
put it in a special database, not in OSM. Do not abuse OSM as a vehicle for
non-crowdsourced (or even non-crowdsourcable) data.
I've been thinking that it might make sense for OSM to implement a
secondary databases set internally- a place where people can upload
datasets which might be appropriate for OSM, then use things like the
vector layer in PL2 to trace over them where it makes sense.
So, it's OK to trace over an administrative boundary displayed in PL2
and have that as part of OSM, but inserting it via API is not OK? Is
that correct? What's the rationale?
Cheers
_______________________________________________
Imports mailing list
[email protected]
http://lists.openstreetmap.org/listinfo/imports
