[mkgmap-dev] gates

Wed Sep 25 19:11:09 BST 2019

Hi Ticker,

I agree that the rule should better be removed. There is another one right below it showing the same problem:
# Disable dead-end-checks for unaccessible oneways
highway=* & oneway=yes & (access=private | access=no) {add mkgmap:dead-end-check=false}
It doesn't cause trouble but I think it would be better to move that rule to a place where inc/access was already executed. I have a closer look tomorrow.

Regarding the gate: With --link-pois-to-ways the barrier is translated to a "no-through-route"-restriction. Such a restriction is ignored if it has no effect on routing, like in this case where the way doesn't allow any traffic mode.

Gerd

________________________________________
Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Mittwoch, 25. September 2019 19:53
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] gates

Hi

I agree that this rule is wrong and to express it correctly is
complicated, needing expansion of the composite transport modes
(vehicle, motor_vehicle, psv) and then testing of all the routable
modes (foot, bicycle, motorcar etc) to see if the global access= is
relevant.

There are only a couple of examples in the "British Isles" where this
rule causes a valid car right-of-way route to be deleted.

It is probably best to deleted the rule.

@gerd: I don't understand your remark in the osm forum:

> The problem is that Garmin allows to set a way point on a routable
> line with type 0x16 which doesn't allow any access. In my eyes this
> is an error in the Garmin software

is this relating to "barrier=..." logic in the default style 'points'
with option --link-pois-to-ways ?

Ticker

On Wed, 2019-09-25 at 08:44 +0000, Gerd Petermann wrote:
> Hi all,
>
> I've answered in the forum thread.
> While I think that there is nothing wrong in mkgmap for this
> particular gate I noticed another problem in the default style:
> The way https://www.openstreetmap.org/way/131440594 has tunnel=yes +
> access=no and is therefore not treated as a highway because of this
> rule
> in the lines file:
> # Hide unaccessible tunnels
> highway=* & tunnel=yes & (access=private | access=no) & foot!=* &
> bicycle!=* {delete highway; delete junction}
>
> This rule looks wrong, I think it would wrongly remove the highway
> tag from a way with
> highway=tertiary+tunnel=yes+access=no+motor_vehicle=yes
>
> Gerd
>
> ________________________________________
> Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag
> von lig fietser <ligfietser at hotmail.com>
> Gesendet: Dienstag, 24. September 2019 09:00
> An: Development list for mkgmap
> Betreff: [mkgmap-dev] gates
>
> Please have a look at this topic, seems barriers are not respected in
> the default style?
> https://forum.openstreetmap.org/viewtopic.php?id=67405
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev