Hi Felix,
good luck!
it is hard to say that a value is not causing problems, as it is not
easy to find all routing problems in a map, not talking about
different maps for different areas of the world.
Whenever you change the value you might see an
improvement in one or two places combined with
new errors somewhere else.
With current implementations use this rule:
The smaller the value, the smaller the optical
errors like zig-zag-ways, the higher the value,
the more likely small ways like steps are completely
removed, thus allowing to route over steps.
Gerd
Date: Thu, 3 Oct 2013 11:50:32 +0200
From: extremecarver@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] Commit: r2724: Make sure that remove-short-arcs with no argument is evaluated with the default value (5.0)
my problems were on older versions - about 7 weeks ago if I remember
correctly. Unsetting 5.4 to nothing (or 0.0) fixed it.
I would have to retest which is the biggest value not causing
probs...
On 03.10.2013 11:35, Gerd Petermann
wrote:
Hi Felix,
yes, the merging of nodes that happens when short arcs are
removed is likely to cause errors, that's why I'd prefer to
find alternatives.
Still I think that you should use --remove-short-arcs=0 if you
want a value
of 0.
Gerd
P.S. Did you already try r2725 from the mergeroads branch, with
or without the value 5?
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev