[Imports] WRI Congo Basin forestry tracks import

[Rafael Avila Coya]

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

Hi, Christoph:

Except for Cameroon, we unfortunately don't have any local OSM
community for any of the other 5 countries. We will try to involve
local people however difficult it is.

I did some tests with some random areas using the WRI data, and
disagree on that "zero" cases. In fact, in some cases of segments that
conflict with the OSM data, the WRI data corrects the OSM
counterparts. But I agree with you that many ways will have to be
corrected or traced again before uploading, and that's a huge job, so
one of the aims will be to involve as more volunteers as possible. I
think the effort is worth enough. Tracks in Africa (and generally all
around the world) don't get much attention as communication roads,
residential areas, health facilities or schools, but they are
nonetheless important, specially when they affect a very delicate area
as the Congo rainforest.

Cheers,

Rafael.

On 17/02/15 21:55, Christoph Hormann wrote:
> On Tuesday 17 February 2015, Rafael Avila Coya wrote:
>>> 
>>> My recommendation therefore would be to not use this data for
>>> an import but render a map layer from it that can be used as a
>>> hint by the mappers in the sense of 'look for a road here and
>>> if there is one map it based newer high resolution images'.
>> 
>> If this was an automatic import, I would also strongly recommend
>> not to do it. In any case, I wouldn't recommend any roads
>> automatic import anywhere nowadays.
>> 
>> But this will be a ***MANUAL*** import. And this means that
>> people involved in it will check the data correctness before it
>> actually upload it.
> 
> I read your import description, i am aware of that.
> 
> The reason for my recommendation is that there are exactly zero
> cases where using the original data directly leads to less work for
> the mapper here.  The data should not be uploaded without
> verification so it is only of use if higher resolution images are
> available and in that case it is less work to newly draw and tag
> the road than to adjust inaccurate and partly erroneous source
> data.
> 
>> If government gives rights for logging, if means it's for
>> forestry traffic, and that's exactly what we have in the wiki ( 
>> http://wiki.openstreetmap.org/wiki/Key:access ): "Only for
>> forestry traffic". I don't see your differentiation anywhere in
>> the Key:access wiki. Likewise for agricultural use.
> 
> I don't really want to get into a discussion on semantics here -
> from the information available so far access=forestry seem clearly
> wrong, especially considering this applies to all modes of
> transport.
> 
> If you are in contact with people and organizations in those
> countries a much more useful step would be to research and document
> the default access restrictions there on:
> 
> http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions
>
> 
- -- 
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/

iQIcBAEBAgAGBQJU49xHAAoJEB3niTly2pPQYOgP/05bTXQ89pmj0tw2IbsueDzW
PTYzirDIQVWvb/B18NngAt0ZpYoSTA3wedzkc+EyICB/iX5xgjtY9J8VJRGWuvp5
gtZEiOw8P1MZ+UDfO+H0mX3+VmpuTI33QtBMtE8/kZ2UDBDsk/lmFMVSVOd9c/W/
svw15jFTIpLSxts3NhnbgvrNQ4/mWctFapOKUKQjYjv9/mE8ANVa+4m7T80LXTY6
lTUI0DuX895TGgNpjIp+jCtX7H0rWivZ/yZTNpsvQRtb9liksusbq1+emiER/fDw
dzKLup3T+sws46Ri9G3Z15JrZSr8fkxQGyJqYrSks7MxZd9MuUl9oZE0UCGowMOd
H4lq7eOk0gaXQNLJPKDqRC9gnaI0Gvm9PkVyKeO1ICnPyQ/pmbUq9oIdTTteHOWI
Hu2TaUaO4fdWYHE5MveCjHRSsrekEhQBHu/g5mRgPNSOqL6q37SwCZJW5gqyaZ4j
85nObcwFfsNGg1HHqibBrpwU+suA5pVvPhbDmjqpCBAm7r62Cqu/2xoIetGFJJZq
ncRmn3SjSIXxHQO7M/a9ykGJM5nbPP1qsWP+Ntu019i4GZXip/FOeBfFunvdiUD3
503x/OZ+zjq5ob0YHTsr3jNkHTlJufAoewvHqJNq4jL/4DEJuPijmlrHC5lq0MrK
2NCOO65CDzt9YxvZkDWm
=gj8/
-----END PGP SIGNATURE-----