[Imports] eHealth Africa Borno Smaller Settlements Import and Road Editing

Wed Mar 18 23:21:49 UTC 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Frederik:

I appreciate your comments, with which I generally agree.

My answers inline.

On 18/03/15 22:48, Frederik Ramm wrote:
> Rafael,
> 
> I have no opinion on your planned import - it sounds like robust 
> planning but I haven't reviewed in detail.
> 
> A general issue I have with HOT-driven imports is that sometimes,
> data will be quickly imported by non-local people and then
> considered complete and done, and the data won't be checked or kept
> current by anyone because the next activation is already going on
> elsewhere. I think that any import you perform also creates an
> obligation to keep the data current, or at least make sure that
> someone does. This is not an official requirement though, it's just
> something I occasionally see.

Yes. It's also my opinion that growing a local, active and permanent
OSM community should be always our goal. I really dislike the idea of
importing things just because those things aren't there. This is
specially true for developed world countries.

In other countries, when that community is very small or non-existent,
importing data gets more interesting, but still the goal is to grow
community, more than just growing "data".

Fortunately, although this is an import as others, the ngo providing
the data is also interested in not only in having their own data
imported to OSM, but also to keep the data updated. They are all the
time collecting new data on the field and correcting the data they
already have. Having these data updated and in good condition will
benefit them as anyone else who needs it, as it will be eventually the
case for humanitarian actors of this crisis.

As an example, I just updated yesterday the residential areas import
for Borno state, with some new polygons and some others that improve
the imported polygons last spring.

> 
> I would like to comment on your initial two paragraphs though:
> 
> On 03/18/2015 07:30 PM, Rafael Avila Coya wrote:
>> Northeast Nigeria has been affected for years now by a complex 
>> humanitarian crisis
> 
> [...]
> 
>> Baseline data (places, residential areas, administrative 
>> boundaries and buildings as well as road networks) over this
>> large affected region are needed
> 
> [...]
> 
> As harsh as it sounds, but whether or not there's a humanitarian 
> crisis, and whether or not data is needed, should never be factors 
> that decide whether an import is good to go or not.

And they aren't factors, and are not meant to be factors whatsoever.
As you say at the end of the email, I mentioned them without any
intention of making the import more important, or urgent or both. The
email I sent was mainly a copy&paste of the emails I sent to the
talk-ng and hot mailing lists. In fact, I was hesitating on keeping
that introduction, but finally I included it, as I thought it would be
informative that is part of the mapping effort of this activation.

> 
> Either you can show that your planned import fulfils the high
> demands that we rightly have, or you can't; a humanitarian crisis
> doesn't make a bad import good. And if data "is needed", it can
> still be mixed with OSM specially for actors in the field, on
> special tile servers, with special data sources - so that's not a
> compelling reason for an import either.

One (manual through the TM) import of health facilities in Kano state
was done by staff of eHealth Africa. The same for the health
facilities in Bauchi state. As the data was collected by themselves,
they might incorporate the data directly, as normal user mapping,
without contacting the imports list (correct me if I am wrong). But I
always suggest that all the imports should be consulted with HOT and
imports lists, for a number of reasons:

*having feedback on tagging and other issues
*getting external people involved too
*etc.

> 
> I know you only mentioned these things as a background and it's
> good that you did, and as I said I am not voicing an opinion on
> this particular import; I just wanted to make crystal clear that a
> HOT data import has to jump through the exact same hoops as any
> other import.

And it's crystal clear for me too. I hope I follow the rules to the
book, and if not, please tell me what to improve. Feedback is probably
the most important here.

Cheers,

Rafael.

> 
> Bye Frederik
> 
> 
> _______________________________________________ Imports mailing
> list Imports at openstreetmap.org 
> https://lists.openstreetmap.org/listinfo/imports
> 

- -- 
Twitter: http://twitter.com/ravilacoya

- --------------------------------

Por favor, non me envíe documentos con extensións .doc, .docx, .xls,
.xlsx, .ppt, .pptx, aínda podendoo facer,  non os abro.

Atendendo á lexislación vixente, empregue formatos estándares e abertos.

http://es.wikipedia.org/wiki/OpenDocument#Tipos_de_ficheros
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJVCgiDAAoJEB3niTly2pPQmuYP/0FczlH1UwRyYPnhrrvSFI9W
BC/kPpoN+PC61J5wrK0wStB/6Ctl7Yrq+aGRRqNeGBtMe691KuyWR/SIORYZjpP8
HBIlQ8fR3Z6MfWJUCitvNCsmLf6gIJfotoVIi7YegfOF5bQyJfSATo0OpN3hZwg8
GoWD3IxrpQV+EaXn9+he7RpP2PQzUp5tePypikJJo4SkX8ncKBBG9Xg3z82i4bVv
FZqIPEWRMF/aQHQRssBEEZz3vTnuKTmASRL0mm0iXjekTyq3H9WJDUlfqcnM0T9U
+WL8DZZ6ASTCTneRIrH/PEZW3CqDOo9jJFBMf8I48SzdS0bUDNagV59DQ6TLzxJh
ajdgU+HxkfXgr5cDPeVE24zaTxGxnGlTiRuneOlN3+quiLHvl56s3ktW6givivwW
aQccH0XIPpHfeNwjJK89NVS5IinyAAVOsfeqTkBhl9SpTdU6QR3lMe14jF966A+1
N/TbiwXMYEofU/k0QI6keGCV4eHgVuYO+YqW0TNDjibo0sxOH//DdsWWe1sLgusD
PdKPsbVPodvUgmeH70me8dD+L9TWOxbjSVpP6L1F2mjVAAjS7Hz/FqoYvHY1xeIU
wDEoB7boWR2TH9aXWHnX4QywtlYRift7fXEsthGZA/aAhuTY0rr0x3NQVUFfWmj7
BtwG3sVSzuM8t0HMbabj
=nXnS
-----END PGP SIGNATURE-----