Version 2736 was committed by gerd on Sat, 05 Oct 2013
fix routing errors: coordPOI_v2.patch + small changes in javadoc
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi all,
I think I understand now most of the miracles related to
short arcs and I am pretty sure that we can solve
the known problems without adding source complexity.
1) In 2009 Mark Burton added the
remove-short-arcs option with r1049.
2) With r1060 he added the option to pass a parameter
El 05/10/13 11:56, GerdP escribió:
Hi all,
I think I understand now most of the miracles related to
short arcs and I am pretty sure that we can solve
the known problems without adding source complexity.
1) In 2009 Mark Burton added the
remove-short-arcs option with r1049.
2) With r1060 he
Version 2737 was committed by gerd on Sat, 05 Oct 2013
don't print debug output to stdout
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd,
Just tried it with my Benelux cyclemap.
I couldnt find any specific routing bugs that were solved but I didnt see any
differences in routing with previous mkgmap versions either.
One particular routing error that still bugs me is that pedestrians can't cross
tile borders (Basecamp)
Hi Minko,
Just tried it with my Benelux cyclemap.
I couldnt find any specific routing bugs that were solved but I didnt see any
differences in routing with previous mkgmap versions either.
Thanks for testing :-)
Does that mean you find routing errors with value 0 that you cannot explain
with
Hi Henning,
I still have this on my todo list. The messages seem
to occur when creating the overview map. Maybe
it is an error in mkgmap.
Will I be able to reproduce the problem with the files from
https://github.com/aighes/RadReiseKarte
?
Gerd
Date: Sat, 14 Sep 2013 19:39:51 +0200
From:
Hi Gerd
I couldnt find any specific routing bugs that were solved but I
didnt see any differences in routing with previous mkgmap versions
either.
Thanks for testing :-)
Does that mean you find routing errors with value 0 that you cannot
explain with the OSM input data? If yes, d like to
well for me it's a bit more complicated, because I often run checks on
the set values (and whether they were set because of physical
inabilities or legal). Therefore I already run one set of alternative
name scheme for access values - but the branch meant I needed to
ammend/change about 500
I was using the merge-roads with Steve's patch. My internet currently is
so slow, I need about 5 hours to download 500MB - so actually it might
be broken again, I cannot really check.
Maybe I was wrong about that the bug first appeared in the merge-roads
branch. I just know 4-5 month ago it
On Wed, Sep 25, 2013 at 02:25:51PM +0100, Steve Ratcliffe wrote:
I often get names like
Shell: Shell (Shell) for fuel stations. The same happens to
restaurants, supermarkets, etc.
The tags name, operator and brand are often the same so I think they
should not all be used in the POI name.
Hi Gerd,
thanks for your answer.
Am 05.10.2013 16:10, schrieb Gerd Petermann:
Hi Henning,
I still have this on my todo list. The messages seem
to occur when creating the overview map. Maybe
it is an error in mkgmap.
Will I be able to reproduce the problem with the files from
12 matches
Mail list logo
