Am Samstag, 25. Oktober 2014, 09:31:33 schrieb Gerd Petermann:
> if I got it right, the idea is to use the prefixed tags
> like mkgmap:bicycle only in the finalize section.
> So that would include also the setaccess and addaccess actions.
>
> Don't know if the current rules in inc\access are meant
ate: Sat, 25 Oct 2014 09:19:40 +0200
> From: ligfiet...@online.nl
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Problematic routing on road_class=3 ferry routes
> for hikers
>
> Problem here is that mkgmap:bicycle=no is overruled by bicycle=yes
> later in th
Problem here is that mkgmap:bicycle=no is overruled by bicycle=yes
later in the access rules, imho there is an issue in the styles.
So I have to add set bicycle=no motorcar=no etc if I use set access no
which I find a bit unlogical.
___
mkgmap-dev maili
r solution?
Gerd
> Date: Wed, 22 Oct 2014 16:04:30 +0200
> From: ligfiet...@online.nl
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Problematic routing on road_class=3 ferry routes
> for hikers
>
> More improvements:
> It seems setaccess=no is not the co
More improvements:
It seems setaccess=no is not the correct command (?), so I changed it into
setaccess no
Then it turns out that in the finalize section mkgmap notice the tag
bicycle=yes and converts it into mkgmap:bicycle=yes, so it somehow switches the
bicycle access flag back off (means acce
> route=ferry & foot!=no {set foot_ferry=yes; set foot=no; add
> mkgmap:ferry=1 } [0x1b road_class=3 road_speed=0 resolution 19
> continue with_actions]
> route=ferry & foot_ferry=yes {setaccess=no; set foot=yes} [0x1b
> road_class=0 road_speed=0 resolution 23]
Oops, I forgot something. Above r
Gerd wrote:
> I tried
> route=ferry & (motorcar=no | motor_vehicle=no | foot=yes & access=no |
> foot=yes & vehicle=no) {add mkgmap:ferry=1} [0x1b road_class=0
> road_speed=0 resolution 23]
> route=ferry {add mkgmap:ferry=1} [0x1b road_class=3 road_speed=0
> resolution 19]
>
> but this still doesn
; To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Problematic routing on road_class=3 ferry routes
> for hikers
>
> Thanks Gerd,
>
> I forgot a few other combinations:
> access=no & foot=yes
> vehicle=no & foot=yes
>
> Of course if cars AND pe
Thanks Gerd,
I forgot a few other combinations:
access=no & foot=yes
vehicle=no & foot=yes
Of course if cars AND pedestrians are allowed, routing will still be
problematic in hiking mode, but with these rules we can eliminate the problems
on foot/bike ferries.
Also note that in bicycle mode thi
Hi Minko,
thanks, I've committed that as r3337.
Gerd
> Date: Mon, 20 Oct 2014 13:15:25 +0200
> From: ligfiet...@online.nl
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] Problematic routing on road_class=3 ferry routes
> for hikers
>
> Y
Yes Gerd, I already noticed ;-)
One addition, maybe set this extra rule for non-car ferries to resolution 23
instead of 19, so it renders at the same level as cycle and footways.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkg
Hi Minko,
I think it is in inc/water_lines
Gerd
ligfietser wrote
> In the Belgium OSM forum someone reported that in the hiking profile ferry
> connections are avoided.
> http://forum.openstreetmap.org/viewtopic.php?id=26980
>
> I noticed in Basecamp that the road_class=3 might be the reason f
Oops. I forgot it was set in the water_lines ;-)
https://github.com/openstreetmap/mkgmap/blob/master/resources/styles/default/inc/water_lines
So I suggest to add
route=ferry & (motorcar=no | motor_vehicle=no) {add mkgmap:ferry=1} [0x1b
road_class=0 road_speed=0 resolution 19]
before this existi
In the Belgium OSM forum someone reported that in the hiking profile ferry
connections are avoided.
http://forum.openstreetmap.org/viewtopic.php?id=26980
I noticed in Basecamp that the road_class=3 might be the reason for this (=main
highways).
In the internal routing routines of the Garmin Oreg
14 matches
Mail list logo
