Hi Gerd Thanks for investigating this. As the eTrex routing seems to work (maybe it is more similar to Mapsource than Basecamp) I'll persist with island removal. Looking at display:NetCheck errors, it looks like the RoadDef.netFlags bit: RoadDef: public static final int NET_FLAG_ADDRINFO = 0x10; display: private static final int RD_HAS_STREET_ADDRESS_INFO = 0x10; and/or nodeCountInner isn't getting set correctly when island-removal happens to the road. Ticker On Thu, 2019-11-21 at 10:00 +0000, Gerd Petermann wrote:
Hi Ticker,
I think we have two different problems here. I can reproduce the errors with display tool even with very small input files and it seems that it existed in almost all versions of the NET-no-NOD branch :-( I have no idea why I didn't see it in various tests before. These problems disappear when I change the code so that the first and last node in a road are always routing nodes. (as it was before r4300) Maybe display tool simply expects this and searches for nodes which don't exist? On the other hand I can reproduce the routing problems with Basecamp (4.7.1), but not with MapSource. And the problems in Basecamp do not disappear when I change the code to add the nodes again, they seem to depend on option --check-routing-island-len only. I always thought that Garmin uses the same routing algo in Mapsource and Basecamp, but at least 4.7.1 shows that I am wrong.
So, for now, I'd say that option --check-routing-island-len should not be used :(
Gerd