logo separator

[mkgmap-dev] [Patch] unpaved roads

From Carlos Dávila cdavilam at orangecorreo.es on Thu Feb 9 13:02:05 GMT 2017

I would interpret that the other way round. If surface=paved, concrete, 
... treat it as paved, no matter what tracktype is. I think tracktype is 
very often misinterpreted by mappers, and wiki doesn't clarify it much 
either. Additionally, tracktype>1 may be an old tag placed before track 
was paved, in the same way that you can find a lot of 
highway=residential, tertiary, etc + tracktype=*

El 09/02/17 a las 11:25, lig fietser escribió:
> My OFM will mark them as unpaved. The combination of track and grade3 
> counts more than the surface. I think the current default rules assign 
> them also as unpaved. Your patch v3 too, is that correct?
> ------------------------------------------------------------------------
> Gerd wrote:
> And what about combinations of surface meaning paved with tracktype?
> The wiki says "Usually ... " or "Almost always an unpaved track" for most
> tracktype values.
> I see quite a lot of ways with
> highway=track & surface=concrete:lanes & tracktype=grade3
> in my Niedersachsen:
> http://overpass-turbo.eu/s/lNI
> I think those are not unpaved, no matter how nice it is to cycle on 
> them;-)
> Gerd

More information about the mkgmap-dev mailing list