logo separator

[mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

From Gerd Petermann gpetermann_muenchen at hotmail.com on Tue Jul 7 11:19:02 BST 2020

Hi Ticker,

regarding order of roads: Yes, seems also to be related to the crash reported by Felix. It seems that a routing island like that including way 37139575 can cause invalid NOD data. Problem disappears when I use Steves patch just for this one way, it also disappears when I change the order of this way and the connected way 37139614 so that way 37139614 is processed first. Still investigating...


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap at jagit.co.uk>
Gesendet: Dienstag, 7. Juli 2020 11:11
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Routing problem on Garmin Oregon/edge with default style (and other styles)

Hi Gerd

I've been trying to pin down another routing problem that shows on
MapSource and eTrex 30x & HCx, but not BaseCamp. It also happens on an
old version I have (r42950) which is pre NET-no-NOD.

When you were looking at some of the problems I was having with NET-no
-NOD, changing the order of roads affected routing errors I was

However, most problems were only demonstrated in BaseCamp, where having
a lineType that should be routable but isn't (because of the NOD
removal or explicitly using one) makes a non-routable area around the

It would be handy if you updated the NET-no-NOD branch to the latest


On Tue, 2020-07-07 at 08:38 +0000, Gerd Petermann wrote:
> Hi all,
> I am back home and started to look at the data. I assume the special
> case with way https://www.openstreetmap.org/way/27866666/history#map=
> 16/40.4820/-3.9354 is that it is not connected to other roads in both
> end nodes AND that is is connected to multiple other roads between
> the ends. I guess I didn't think of this case before.
> I can reproduce the crash with NodCheck when I create a map for
> 64130028.osm.pbf using only the option --route, but up to now I was
> not able to reproduce it with a smaller input file just containing
> the area around the special way, so there might be a 2nd problem...
> Gerd

mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk

More information about the mkgmap-dev mailing list