Hi Thomas,
there should be no need to handle this in the style rules, the tag is handled
by java code.
Gerd
Von: mkgmap-dev im Auftrag von Thomas
Morgenstern
Gesendet: Mittwoch, 25. September 2019 22:21
An: Development list for mkgmap
Betreff:
Hi, i found some highways tagged with 'oneway=*-*1'. It means, the
highway is accessible in the wrong direction. Question 1: does the
default style change that ? I found no string in the style including
oneway=-1 . Question 2: or do mkgmap change the direction automatically
without any needs in
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
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
Hi Manfred,
No idea. I cannot reproduce the result with the default style in Mapsource. I
tried with vehicle car as well as with cycling or pedestrian, I never get the
long detour.
Can you reproduce it with Mapsource? If yes, please provide more details about
the routing settings.
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
Hi
The Tertiary road has an incline of -12 degrees.
Perhaps it's avoiding steep hills?
Regards
Nick
On 24/09/2019 20:58, DD8KQ wrote:
Hi
may be that somebody has an idea why the routing of my gpsmap 276Cx is
so crude. I'm using almost the standard style to build my own garmin
maps. And as
Version mkgmap-r4292 was committed by gerd on Wed, 25 Sep 2019
Fix problem with long roads producing the error message "internal error? The
nodeCount doesn't match value calculated by RoadNetWork"
Problem was introduced with r4291
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap=4292
