February 2009 - mkgmap-dev - The mkgmap lists

YATTLE (yet another tile-too-large exception)
by Wolfgang v. Hansen 26 Feb '09

26 Feb '09

Just found this one. Decreasing tile size makes it go away. Requires sensible error message. -Wolfgang Exception in thread "main" java.lang.AssertionError: NET 1 offset too large at uk.me.parabola.imgfmt.app.net.RoadDef.writeRgnOffsets(RoadDef.java:24 4) at uk.me.parabola.imgfmt.app.net.NETFile.writePost(NETFile.java:64) at uk.me.parabola.mkgmap.build.MapBuilder.makeMap(MapBuilder.java:155) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:87) at uk.me.parabola.mkgmap.main.MapMaker.makeMap(MapMaker.java:53) at uk.me.parabola.mkgmap.main.Main.processFilename(Main.java:150) at uk.me.parabola.mkgmap.CommandArgs$Filename.processArg(CommandArgs.jav a:329) at uk.me.parabola.mkgmap.CommandArgs.readArgs(CommandArgs.java:119) at uk.me.parabola.mkgmap.main.Main.main(Main.java:91)

1 0

[PATCH v3] turn restrictions
by Mark Burton 26 Feb '09

26 Feb '09

Folks, Here's the current code - not much different from the previous versions, just a few tweaks to some diagnostics and avoid NPEs here and there. Unless some bad problems show up, or anyone has any issues with the implementation, I shall be looking to commit this to the trunk in a day or two. Cheers, Mark

2 3

Commit: r935: Added support for processing turn restrictions.
by svn commit 25 Feb '09

25 Feb '09

Version 935 was commited by markb on 2009-02-25 22:06:57 +0000 (Wed, 25 Feb 2009) Added support for processing turn restrictions. Only "well formed" turn restrictions are handled - i.e. the 'from' and 'to' ways must terminate at the 'via' node. Multiple 'via' nodes are not supported and neither are 'via' Ways. The "except", "day_on/off", "hour_on/off" tags are ignored. The --ignore-turn-restrictions option can be used to disable the feature.

1 0

Commit: r934: Sets extra bit in a header field that (magically) enables turn restrictions.
by svn commit 25 Feb '09

25 Feb '09

Version 934 was commited by markb on 2009-02-25 22:06:52 +0000 (Wed, 25 Feb 2009) Sets extra bit in a header field that (magically) enables turn restrictions.

1 0

Commit: r933: Added addRestriction() to implement the low-level details of creating a turn restriction.
by svn commit 25 Feb '09

25 Feb '09

Version 933 was commited by markb on 2009-02-25 22:06:49 +0000 (Wed, 25 Feb 2009) Added addRestriction() to implement the low-level details of creating a turn restriction.

1 0

Commit: r932: Added getArcTo() and getArcFrom() to locate arc to/from some other node.
by svn commit 25 Feb '09

25 Feb '09

Version 932 was commited by markb on 2009-02-25 22:06:46 +0000 (Wed, 25 Feb 2009) Added getArcTo() and getArcFrom() to locate arc to/from some other node.

1 0

Commit: r931: Added toString() to improve diagnostic messages.
by svn commit 25 Feb '09

25 Feb '09

Version 931 was commited by markb on 2009-02-25 22:06:42 +0000 (Wed, 25 Feb 2009) Added toString() to improve diagnostic messages.

1 0

Commit: r930: Make pubs appear in Entertainment->Bar/Nightclub find category.
by svn commit 25 Feb '09

25 Feb '09

Version 930 was commited by markb on 2009-02-25 20:45:09 +0000 (Wed, 25 Feb 2009) Make pubs appear in Entertainment->Bar/Nightclub find category.

1 0

Duplicated POI's in overlapping areas.
by Carlos Dávila 25 Feb '09

25 Feb '09

I shared one of my mkgmap maps with another osmer who lives just in the area where two tiles overlap and he has detected poi's are duplicated in that area e.g. if you search a petrols station it appears twice. Regards Carlos

2 2

elevation/depth point in *.osm & *.mp
by David 25 Feb '09

25 Feb '09

As I was trying to compile an old map with mkgmap, I discovered that elevation spots (0x6300) were wrong. They should be converted in the same manner as contour lines. Now the question is : which tags define depth and elevation spots in OSM format (an elevation spot is not always a named peak) ? Here is the patch for both depth and elevation spots : Index: PolishMapDataSource.java =================================================================== --- PolishMapDataSource.java (revision 929) +++ PolishMapDataSource.java (working copy) @@ -261,6 +261,12 @@ Coord co = makeCoord(value); setResolution(point, name); point.setLocation(co); + /* if it is depth spot (0x6200) or elevation spot (0x6300), then fix units if required */ + if ((point.getType() == 0x6200) || + (point.getType() == 0x6300)){ + fixPointElevation(); + } + } } @@ -282,7 +288,7 @@ if ((polyline.getType() == 0x20) || (polyline.getType() == 0x21) || (polyline.getType() == 0x22)) { - fixElevation(); + fixPolylineElevation(); } setResolution(polyline, name); @@ -318,7 +324,7 @@ * The elevation needs to be in feet. So if it is given in meters then * convert it. */ - private void fixElevation() { + private void fixPolylineElevation() { if (elevUnits == 'm') { String h = polyline.getName(); try { @@ -333,6 +339,21 @@ } } + private void fixPointElevation() { + if (elevUnits == 'm') { + String h = point.getName(); + try { + // Convert to feet. + int n = Integer.parseInt(h); + n *= METERS_TO_FEET; + point.setName(String.valueOf(n)); + + } catch (NumberFormatException e) { + // ok it wasn't a number, leave it alone + } + } + } + /** * Called for each command in a POLYGON section. There will be a Data * line consisting of a number of co-ordinates that must be separated out

1 0