Hi Ticker, reg no-arcs-first.patch: It only has an effect when you use --x-no-force-end-nodes-routing-nodes and I am not sure yet about its effects. I have to do more testing of the special case reported by Felix. I've not yet understood how to avoid the special case which crashes NodCheck. A single node without arcs will still produce this crash. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Montag, 13. Juli 2020 09:51 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Bad routing on eTrex and MapSource Hi Gerd That's a shame, thanks for all the investigating. This is normally only a problem at the start & end of journeys. Is "no-arcs-first.patch" going to become part of trunk? Ticker On Mon, 2020-07-13 at 05:43 +0000, Gerd Petermann wrote:
Hi Ticker,
I think we have to live with this problem. I found the same error with original Garmin demo maps, e.g. "Topo Deutschland" from 2010 tile 16608746.img. MapSource calculates a big detour, Basecamp doesn't. Inverted route is short in both programs: 1. Rheinstraße 0 m 0:00:00 N53.01308 E8.77969 2. Get on Rheinstraße and drive north 0 m 0 m 0:00:00 0:00:00 180° grid N53.01308 E8.77969 3. Turn right onto Neckarstraße 13 m 13 m 0:00:01 0:00:01 17° grid N53.01317 E8.77973 4. Turn right onto Ahrstraße 32 m 19 m 0:00:08 0:00:09 99° grid N53.01315 E8.78001 5. Ahrstraße 44 m 12 m 0:00:13 0:00:22 180° grid N53.01306 E8.78005
I did not find a route restriction or oneway road which would explain this.
Gerd
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev