February 2009 - mkgmap-dev - The mkgmap lists

Commit: r908: Sort NOD 3 entries - Robert Vollmert.
by svn commit 19 Feb '09

19 Feb '09

Version 908 was commited by markb on 2009-02-19 00:42:23 +0000 (Thu, 19 Feb 2009) Sort NOD 3 entries - Robert Vollmert.

1 0

Not much progress on inter-tile routing yet
by Mark Burton 18 Feb '09

18 Feb '09

Not much too report after spending quite a few hours on this last night. I am trying to understand why some inter-tile connections are good and a lot are bad. I have tried moving points around and rounding coordinates and stuff like that but with no knowledge gained about from the fact that it appears you can zero the bottom 2 bits of the lat/lon values in the nod3 record and it doesn't stop a good inter-tile connection from working. If you zero 3 bits, that stops it being usable. I have tried limiting the size of the NOD3 section to 16 entries, it made no difference. I shall work some more on it tonight. Cheers, Mark

2 4

Encoding problem with splitter
by Carlos Dávila 18 Feb '09

18 Feb '09

Running splitter I get an error related with encoding: java -Xmx750M -jar splitter.jar ../JOSM/peninsula.osm Error opening or reading file com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence. Total time 37s Any hint? Cheers Carlos

2 2

pink line doesn't draw correctly
by Johann Gail 18 Feb '09

18 Feb '09

Hello, I have just discovered a new failure of drawing of the pinky line. I have compiled s small section of a map with mkgmap-nod (latest R881) to an img file. Routing works correctly, the text messages describes the correct way. But the pink line makes an jump to the end of the street. The streets contains only 5 and 7 nodes, so they shouldn't be to long. I've attached a screenshot of my etrex. The route should start at the bottom middle, go upwards, turn right, turn left, go on top of the screen. Instead it makes an jump to the end of the horizontal street. I've merged in R877 from the trunk, but there was no difference. I've tried to move around different nodes of the horizontal street a little to see the effect. There was no change.

7 40

[PATCH] NumberFormat in Splitter
by Johann Gail 18 Feb '09

18 Feb '09

OK, my previous patch has been tested and worked. But to minimize further risk of locale problems I would prefer the following patch: Index: src/uk/me/parabola/splitter/SubArea.java =================================================================== --- src/uk/me/parabola/splitter/SubArea.java (Revision 21) +++ src/uk/me/parabola/splitter/SubArea.java (Arbeitskopie) @@ -25,6 +25,7 @@ import java.util.Formatter; import java.util.Iterator; import java.util.List; +import java.util.Locale; import java.util.Map; import java.util.zip.GZIPOutputStream; @@ -105,13 +106,11 @@ writer.append("<?xml version='1.0' encoding='UTF-8'?>\n"); writer.append("<osm version='0.5' generator='splitter'>\n"); - Formatter fmt = new Formatter(writer); - fmt.format("<bounds minlat='%f' minlon='%f' maxlat='%f' maxlon='%f'/>\n", - Utils.toDegrees(bounds.getMinLat()), - Utils.toDegrees(bounds.getMinLong()), - Utils.toDegrees(bounds.getMaxLat()), - Utils.toDegrees(bounds.getMaxLong())); - fmt.flush(); + writer.append("<bounds minlat="+Utils.toDegrees(bounds.getMinLat())); + writer.append(" minlon="+Utils.toDegrees(bounds.getMinLong())); + writer.append(" maxlat="+Utils.toDegrees(bounds.getMaxLat())); + writer.append(" maxlon="+Utils.toDegrees(bounds.getMaxLon())); + writer.append("/>\n"); } public void finishWrite() {

3 3

Commit: r907: Fix error in previous commit.
by svn commit 18 Feb '09

18 Feb '09

Version 907 was commited by robert on 2009-02-18 16:02:51 +0000 (Wed, 18 Feb 2009) Fix error in previous commit.

1 0

Commit: r906: Change handling of oneway/dirindicator.
by svn commit 18 Feb '09

18 Feb '09

Version 906 was commited by robert on 2009-02-18 14:57:24 +0000 (Wed, 18 Feb 2009) Change handling of oneway/dirindicator. The DirIndicator-field in .mp-files now corresponds to Polyline.FLAG_DIR, while the flags in NET and NOD both correspond to oneway-ness.

2 1

Commit: r905: Option documentation fix: --code-page
by svn commit 18 Feb '09

18 Feb '09

Version 905 was commited by robert on 2009-02-18 11:30:37 +0000 (Wed, 18 Feb 2009) Option documentation fix: --code-page

1 0

Commit: r868: Implement routing for .osm input files.
by svn commit 18 Feb '09

18 Feb '09

Version 868 was commited by steve on 2009-02-09 22:15:14 +0000 (Mon, 09 Feb 2009) Implement routing for .osm input files. -Mark Burton

13 55

Interesting partial success when inter-tile routing
by Mark Burton 17 Feb '09

17 Feb '09

I have managed to route across a tile boundary but the route that was taken was not optimal, it took a much longer route than necessary. Further investigation showed that the "obvious" road to take did not join across the boundary of the tiles but the road that was used must have joined across the boundary. I was routing from west to east and I could route right up to the boundary OK but if I wanted to be on the eastern side of the boundary, the routing was done via other roads and so it reached the destination coming from the east. So, is it just a matter of making the coordinates match better? If so, how do we do that? Rounding? Anyone have any ideas? Cheers, Mark

1 1