[talk-ph] On managing OSM-PH data import

[maning sambale]

Hi,

The planned Palawan road import gave  me a few realizations I think we
should look into, to easily manage bulk data import for the
Philippines.

For historical reasons (because there was no OSM-PH community back
then), I coordinated many data imports with help rom other OSMers like
MikeCollinson, IvanSanchez, etc.  All my imports have been roughly
documented in the wiki:
http://wiki.openstreetmap.org/wiki/WikiProject_Philippines/Data_import.
 My OSM username for data import: ph_import

I am certain that with the increasing popularity of OSM, more and more
dataholders will take notice and provide data.  I personally welcome
this for several reasons:
1. why do it again, when other institutions have already done it (in
some cases paid by my own tax);
2. by importing data, the community can expose problems with the data;
which the community can,
3. actively maintain and update

That being said, I also want data import activities to be
community-led as well.  Anybody, can do the data import provided that
we follow at the minimum, e.g. license-compatibility clause.

For my end, I will continue data hunting and import, following some
self-imposed protocols.
1. All planned imports will be announced to the list.
2. Data that will be imported will be provided to anyone willing to
evaluate the quality of the data via a public download link.  However,
if the data holder have expressed that the "raw" shouldn't be
distributed (due to some unfounded paranoia which I don't quite
understand since it will be added to OSM anyway) another means to
distribute data for evaluation will be made.
3. Community-consensus should be made before imports.
4. Another announcement will be made when consensus was achieved.
5. Another announcement after data import.

Is this OK with the community? Any other suggestions?
-- 
cheers,
maning
------------------------------------------------------
"Freedom is still the most radical idea of all" -N.Branden
wiki: http://esambale.wikispaces.com/
blog: http://epsg4253.wordpress.com/
------------------------------------------------------