Thanks both of you for putting me right !
r Nick
--
View this message in context:
http://gis.19327.n5.nabble.com/mkgmap-and-route-restrictions-tp5800402p5800533.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.
___
mkgmap-dev
Nick,
designation= public_footpath is not enough, you should add foot=yes or
foot=designated to the OSM data.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
ate: Fri, 21 Mar 2014 03:28:10 -0700
> From: o...@pinns.co.uk
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] mkgmap and route restrictions
>
> Hi Gerd
>
> yes, I didn't use the default style - apologies for having lead you up the
> 'garden pa
Hi Gerd
yes, I didn't use the default style - apologies for having lead you up the
'garden path'
It does have 'designation= public_footpath' which should allow pedestrians?
Thanks for your Time
r
Nick
--
View this message in context:
http://gis.19327.n5.nabble.com/mkgmap-and-route-restrict
sides that I see no restriction relation in that area,
so it is also not related to that.
Gerd
> Date: Thu, 20 Mar 2014 11:23:27 -0700
> From: o...@pinns.co.uk
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] mkgmap and route restrictions
>
> Hi Gerd
>
>
Hi Gerd
This might be related:
http://www.openstreetmap.org/#map=17/50.60751/-3.60074
If I take the maroon route I am routed correctly via Highlands Park- which
is private but designation=foot
In fact its parsed correctly as it shows my blue walking sign half way.
However, if I click on Colway L
Hi WanMil,
WanMil wrote
>> Hi all,
>>
>> looking at the 4 node restrictions I think I found a general bug in
>> mkgmap:
>>
>> Both with polish (.mp) format and with OSM data we compute the
>> routing nodes for which the restriction shoud be applied.
>> In a second step we compute the arcs between
Hi all,
looking at the 4 node restrictions I think I found a general bug in mkgmap:
Both with polish (.mp) format and with OSM data we compute the
routing nodes for which the restriction shoud be applied.
In a second step we compute the arcs between these nodes.
In this 2nd step we ignore the in
Hi all,
looking at the 4 node restrictions I think I found a general bug in mkgmap:
Both with polish (.mp) format and with OSM data we compute the
routing nodes for which the restriction shoud be applied.
In a second step we compute the arcs between these nodes.
In this 2nd step we ignore the in