I tried out my usual set of rules - could not notice any difference in autorouting results. Also more complicated routes needing around 25 seconds to calculate where exactly identical and took identical time to calculate. Visual I did not notice a difference - but then did not look very hard to find differences. Size decrease is modest compared to other changes... On Wed, 5 May 2021 at 19:04, Felix Hartmann <extremecarver@gmail.com> wrote:
Actually when I think about it - reversing the direction for waterways should be done anyhow - there is no waterway that flows in opposite direction. Cliff lines most likely the same. And for lines that are off center - that doesn't matter as long as all resulting lines are reversed. It would actually be better as otherwise at one point the right side jumps to the left and this could be prevented.
Yes oneway roads (plus all copies created from it via continue) - those you cannot merge.
On Wed, 5 May 2021 at 18:47, Felix Hartmann <extremecarver@gmail.com> wrote:
will that patch also work on the low resolution branch, or only against trunk?
On Wed, 5 May 2021 at 18:05, Gerd Petermann < GPetermann_muenchen@hotmail.com> wrote:
Hi all,
up to now RoadMerger doesn't merge (combine) two roads if the have different directions. This is OK for oneway roads but I see no need for this with other roads. The attached patch changes this. It has an influence on file size (safes a few KB in each tile) and very likely also on routing, hopefully to the better/faster. It also reduces zig-zagging in the low-res-opt branch.
Strangely enough almost all was already implemented, so maybe WanMil (the original author) tried that before and found a reason not to do it. Will search the archives later...
Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- Felix Hartman - Openmtbmap.org & VeloMap.org
-- Felix Hartman - Openmtbmap.org & VeloMap.org
-- Felix Hartman - Openmtbmap.org & VeloMap.org