Hi Ticker,
thanks, but the problem is not routable vs. non-routable, but that the
device seems to prefer to leave the cycleway for a longer footway
instead of staying on the shorter cycleway, which should additional have
a higher road_speed and a higher road_class.
And that it does not work here means either the tags on the ways are not
correct or there is an error in my style.
Something to debug for the next rainy day :)
Thorsten
Am 2024-08-30 17:21, schrieb Ticker Berkin:
Hi Thorsten
Thanks for testing this.
The routable line types are:
0x01 ... 0x13 highways
0x16 highway
0x1a ... 0x1b ferry
on newer garmin devices/Basecamp
0x2c ... 0x2f ?/Climbing path/Via Ferrata/Cable Car
Using these for non-routables can break routing nearby in some Garmin
software;
I've certainly seen this behaviour in Basecamp. The default style uses
the
correct routable/non-routable types for the context.
I've seen suggestions that 0x17 is routable. This is used by the
default style
as non-routable.
Routable types 0x08, 0x09, 0x0c, 0x1a and 0x1b and maybe 0x13 have
slightly
different behaviour - mainly relating to the navigation instructions
issued.
Regards
Ticker
On Fri, 2024-08-30 at 09:59 +0200, Thorsten Kukuk wrote:
Hi,
I tested that patch in BaseCamp and yesterday evening on a bicycle
tour.
Navigation instructions were good, I haven't seen any wrong hint, no
missing one and also no superfluous. Same result as I had already on
several other tours the last days with v5.
Great job, that patch is a big improvement!
With v6 I had some wired navigation instructions on one place when
when
I deviated from the route and it automatically guided me back. But
when
I did inspect the map today, there is a small, parallel path, could be
very well that the Garmin device wanted to route me via that way and
it
was not visible on the small display.
I couldn't reproduce that with a GPX track or BaseCamp. Need to check
the OSM data later, I assume wrong tags.
Or I need to switch the line types in my maps. It's really wired which
effect line types have on routing and navigation instructions.
So if you get flooded with useless navigation instructions, this could
also be the fault of using the wrong line type in your map...
Thorsten
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
