Hi Gerd (I started writing this before your next post arrived) Assuming I understand the resultant behaviour correctly concerning the 2nd change: I'm against the idea not having NODs for terminal roads becoming the default. It may not have obvious effects in heavily built up areas, but elsewhere, a reasonably proportion of places that someone might wish to navigate to are reached by a single track/driveway. The entrance to this access road will rarely be the closest point a road. Sometimes it is even a different road! Ticker On Sat, 2019-10-12 at 10:28 +0100, svn commit wrote:
Version mkgmap-r4300 was committed by gerd on Sat, 12 Oct 2019 BRANCH: NET-no-NOD experimental code to reduce NOD size (option --routable) - don't add a route node for the ends of roads when they are not connected to other roads -don't write NOD info for roads which are not connected to other roads and which do not have boundary nodes Wanted effect: smaller NOD size Problem of 2nd change: Routing at those roads behaves different, large detours may be calculated instead of a straight line which clearly says: routing problem new option --x-all-roads-to-nod can be used to get the old behaviour (with a larger NOD)
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4300 _______________________________________________ mkgmap-svn mailing list To unsubscribe send an mail to mkgmap-svn-leave@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-svn