February 2009 - mkgmap-dev - The mkgmap lists

About routing options, Mapsource and speed limit
by David 23 Feb '09

23 Feb '09

The option "route" in a file called with -c option does not work for me. I have to launch "java -enableassertions -Xmx512M -jar mkgmap.jar --net --route -c options.txt mymap.osm" if I want a routable map. Since someone set by default TDB v4, I can build routable map, thank you. It is like "--tdbfile=tdb-v4" did never work for me since revision 86x. I test the Ireland map with Mapsource and I observe strange results in route calculation : With shortest length selected : Major highways are systematically avoid despite I setup Mpasource with "choose major highways first". Major highways are used only with "choose minor roads" It seems to be an inversion bug with "shortest length" only. Moreover, the distance calculated is bigger (68.2km in 8h21min51s !!!) than when I choose the shortest time (62.4km in 8h18min11s !!!) The one way restriction on motorway for example is not taken in account. I did my tests on M4 motorway between Lucan and Tyrrelspass. Is it a hidden bug on speed limit with an incidence on one way ? On screenshots below, you can also see a hole on highway. I did not found anything wrong in data... Here are screenshots (there is no inversion between pictures): setup with "choose major highways first" (motorway M4 is in orange): Choose major highways first means minor roads ! Setup with "choose minor roads first" (the hole in the route should come from map data) : Choose major minor roads means highways first ! Wrong way in Mapsource : Mapsource doesn't drive on left ! Good way in Mapedit : Mapedit good route

3 4

Bug report: splitter.jar --split-file faulty
by Wolfgang v. Hansen 23 Feb '09

23 Feb '09

Hi, I hope this list is also the right place for bug reports on behalf of the tile splitter. It is unable to read negative values from the split-file, even if the automatically generated file is used. Here's a screen dump: g30xfffe9800 Bad number in areas list file Exception in thread "main" java.lang.NullPointerException at uk.me.parabola.splitter.AreaList.dump(AreaList.java:145) at uk.me.parabola.splitter.Main.readArgs(Main.java:122) at uk.me.parabola.splitter.Main.split(Main.java:80) at uk.me.parabola.splitter.Main.main(Main.java:67) -Wolfgang

2 1

Commit: r929: Typo in options (Jani Patanen)
by svn commit 23 Feb '09

23 Feb '09

Version 929 was commited by robert on 2009-02-23 19:16:49 +0000 (Mon, 23 Feb 2009) Typo in options (Jani Patanen)

1 0

Re: [mkgmap-dev] [PATCH] turn restrictions - alpha code for testing
by Mark Burton 23 Feb '09

23 Feb '09

Hi Jani, > > Only "well formed" turn restrictions are handled - i.e. the 'from' and 'to' > > ways must terminate at the 'via' node. > > Please specify bit more on "must terminate". Terminate as end or > terminate as ways contain the same node? Both of the ways must end at the 'via' node. > Example attached. The "to" way goes trough the "via" node. > Is this well formed or badly formed restriction? Badly formed. Quoting from the Wiki page: > The "from" and "to" members must start/end at the "via" node (see 1). > 1. If the way do not start/end at the "via"-node, split it! Cheers, Mark

1 0

arcs and links (terminology)
by Robert Vollmert 23 Feb '09

23 Feb '09

Hello, I'm half-way through rewriting nod.txt to use the terminology in mkgmap's routing code, and I'm looking for input regarding the naming of arcs and links. In the current version of nod.txt, I called any of the pointers between nodes "links", and called the "arcs" we're writing now "direct links", while the "links" we're not writing yet are called "indirect links". On the other hand, libgarmin uses arcs and links, and mkgmap's source code has just arcs for the moment. Consistency would be nice. Does anyone have a suggestion for a new term encompassing both arcs and links? I'm finding myself writing a lot of "arc/link", and distinguishing them as "direct something" vs. "indirect something" would make the text a lot clearer. What do you think of using the word "edge" (as in an edge of the routing graph)? arc = direct edge link = indirect edge If we ever want to write links, it would probably make sense to base RouteLink and RouteArc in a common superclass, which would also benefit from an umbrella term. Cheers Robert

2 1

Commit: r928: Restriction fixes (Mark) and documentation.
by svn commit 23 Feb '09

23 Feb '09

Version 928 was commited by robert on 2009-02-23 14:17:49 +0000 (Mon, 23 Feb 2009) Restriction fixes (Mark) and documentation.

1 0

[PATCH] - make NodDisplay cope with nodes that have no arcs
by Mark Burton 23 Feb '09

23 Feb '09

I discovered what the 0x40 bit in the node flags means - arcs are present. The attached patch makes NodDisplay do the right thing when no arcs are present and it also now prints offsets into the restrictions table (only small offsets handled at the moment). I have also changed RouteNode to only set that flag if arcs are present and will check that into the mkgmap trunk. Cheers, Mark

2 2

Commit: r927: Now sets the arcs flag (0x40) only when arcs are present.
by svn commit 23 Feb '09

23 Feb '09

Version 927 was commited by markb on 2009-02-23 12:41:05 +0000 (Mon, 23 Feb 2009) Now sets the arcs flag (0x40) only when arcs are present.

1 0

Commit: r926: Use correct number for available slots in a directory block.
by svn commit 23 Feb '09

23 Feb '09

Version 926 was commited by steve on 2009-02-23 00:32:49 +0000 (Mon, 23 Feb 2009) BRANCH: small_img Use correct number for available slots in a directory block. Appears to be OK for several different sized files now.

1 0

Commit: r925: Directory sizing works for small files. Probably by co-incidence.
by svn commit 23 Feb '09

23 Feb '09

Version 925 was commited by steve on 2009-02-23 00:17:08 +0000 (Mon, 23 Feb 2009) BRANCH: small_img Directory sizing works for small files. Probably by co-incidence.

1 0