[Imports] WRI Congo Basin forestry tracks import

Rafael Avila Coya ravilacoya at gmail.com
Mon Feb 16 20:29:09 UTC 2015


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

Hi, Christoph:

Thanks for your input. I answer inline.

On 16/02/15 21:03, Christoph Hormann wrote:
> On Monday 16 February 2015, Rafael Avila Coya wrote:
>> 
>> This is a call for comments on the import of WRI data (forestry 
>> tracks only, with very few plantation (agricultural) tracks) for
>> 6 countries in the Congo Basin (Cameroon, Equatorial Guinea,
>> Central African Rep. (CAR), Gabon, Dem. Rep. of Congo (DRC) and
>> Republic of Congo).
> 
> I could not find any information in your documentation on the
> origin and production process for the source data.  This would be
> essential information to assess if this data is suitable for OSM.

Original data is in shapefile format. I've put the original files in
osm format to make it easier to open in JOSM. I can give you access to
the shapefiles if you need so.

The original files are given to me directly by the WRI staff.

> 
> What is the basis of applying highway=track and in some cases also
>  surface=unpaved to all elements? Do the source data specifications
>  match those on
> https://wiki.openstreetmap.org/wiki/Tag:highway%3Dtrack

It's clear that ALL forestry tracks are unpaved in Africa, specially
in that area. Even most of trunk national roads are unpaved, and
sometimes impassable during part of the year.

All these highways are tracks, as they are used for forestry, not for
connection purposes. If they were any connecting way, it would be
corrected. Remember that this import will be manual, and go through a
validation process. It has more of mapping than importing.

> 
> Do these roads really all have legal use restrictions, i.e. is it 
> forbidden to use them except for forestry/agriculture?  Otherwise 
> access tags are not appropriate.

I suppose so. Most of the tracks just lead nowhere except for logging
purposes. Even if it was allowed to drive on them, it would be useless
except for staff involved in logging activities. The same applies to
the few agricultural tracks.

> 
> Your import workflow description does not seem to contain any 
> instructions how to handle intersections of roads with other
> features, in particular waterways.

Good point. I will add this to the workflow.

Cheers,

Rafael.

- -- 
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/

iQIcBAEBAgAGBQJU4lMJAAoJEB3niTly2pPQePEP/0jv52xjW4VV78PdQJMFrc1J
RnEugf/c2gYbNqHF/Gwb5LyDa8i1fcjuRo004+uXayEqJe+w6s+rcXB2SqQ92GhY
CgsUHbsIgX8B/4CiNqYs0Sy08dTYZkHkq+hKbjT/umTjVWOntbdxsslh98KYDC98
3bkvnePyl3ye2hglNqLiN6+OVW08aolaOJRz3iWRBP1K19ZRLvXcIWrkxE4WzlIH
cVEqOkdFcp9zOHhThas+X2/onYpOfHqXh4J7G0Vypwpd1Jzz32AfktZmZ+HKzGZp
6giQblSk8SSPOYltPYaTrefWtMaI6PQLYs+tPsAaneJS1APlhRNG/dGKt3yWfE+0
e6zllpboo5sXeOv/pdD4mYPbAq2jh4vLtqk5RVbxN69bZnt0VAkH2Wjp8e5eqS4Y
cOr2VxO7zqrxrjx1YU7meBUo+eYueIHAbU3rmaxWDwtExbQCEmgyhgGCng2zx3WQ
r22loddqgNOiAKlJytt1k06u50eRo2cWUxIOxklXO7gMBQc7NRnCpSZul+6z7F4C
XZEUe8PfhlxzcKd6F+AYWhnj4FZxicFBMi3E+2s5G7pOjjLA3KmBZBwf0mzH0of4
47zDl7UzALoVTtb0xAQSMf+Kt3J2dm9XqVt0wPuMGGB6eRIF/sE2eci4lIHrI6GL
WeIbzH9Z5P3ZAgk8HPpC
=M620
-----END PGP SIGNATURE-----



More information about the Imports mailing list