- mkgmap-dev - The mkgmap lists

Commit: r1426: Revert back to using Properties rather than EnhancedProperties.
by svn commit 09 Dec '09

09 Dec '09

Version 1426 was commited by markb on 2009-12-09 11:08:22 +0000 (Wed, 09 Dec 2009) Revert back to using Properties rather than EnhancedProperties. I nearly removed this change from the original patch at the time because it didn't appear to do anything useful but sloth got the better of me. Wish I had now.

3 2

Commit: r1423: Tests did not compile due to change in StyledConvter, changed back.
by svn commit 09 Dec '09

09 Dec '09

Version 1423 was commited by steve on 2009-12-08 23:37:29 +0000 (Tue, 08 Dec 2009) Tests did not compile due to change in StyledConvter, changed back. Compiling .mp format maps caused a crash if a RouteParam is given. Crash stopped but there is probably a remaining bug.

2 1

Commit: r1425: Add mkgmap:unpaved=1 and mkgmap:ferry=1 to the default style.
by svn commit 09 Dec '09

09 Dec '09

Version 1425 was commited by marko on 2009-12-09 09:09:46 +0000 (Wed, 09 Dec 2009) Add mkgmap:unpaved=1 and mkgmap:ferry=1 to the default style.

1 0

--index crashes on an otherwise successfully rendered image
by Lambertus 09 Dec '09

09 Dec '09

Mkgmap sometimes crashes with when trying to build a gmapsupp including index using an existing (prerenderd) image. Exception in thread "main" java.lang.IndexOutOfBoundsException: Index: 32803, Size: 488 at java.util.ArrayList.rangeCheck(ArrayList.java:571) at java.util.ArrayList.get(ArrayList.java:349) at uk.me.parabola.imgfmt.app.lbl.LBLFileReader.readPoiInfo(LBLFileReader.java:354) at uk.me.parabola.imgfmt.app.lbl.LBLFileReader.<init>(LBLFileReader.java:71) at uk.me.parabola.imgfmt.app.map.MapReader.<init>(MapReader.java:80) at uk.me.parabola.mkgmap.combiners.MdrBuilder.onMapEnd(MdrBuilder.java:108) at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:369) at uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:124) at uk.me.parabola.mkgmap.main.Main.main(Main.java:122) zip warning: name not matched: gmapsupp.img This happens when trying to make a gmapsupp with the following Garmin image: http://planetosm.oxilion.nl/~lambertus/garmin/routable/18-11-2009/63240210.… It's reproducible with at least r1404 and r1387: java -Xmx2048M -jar mkgmap.jar --index --overview-mapname=63240000 --series-name='OSM World Routable' --latin1 --description='OSM World Routable' --product-id=3 --family-id=2000 --tdbfile --nsis --gmapsupp *324*.img If you remove the --index from the command then the IndexOutOfBoundsException exception does not occur. I don't know the Mkgmap verion used to render the source image, but it's pretty recent. If this version is needed then I'll look it up this evening. I hope someone can have a look at this. Thanks in advance.

3 9

Commit: r1424: Fix regression introduced in r1419.
by svn commit 09 Dec '09

09 Dec '09

Version 1424 was commited by markb on 2009-12-09 00:16:59 +0000 (Wed, 09 Dec 2009) Fix regression introduced in r1419. Oops, inserting a new value in the middle of RoadDef.ACCESS[] was the wrong thing to do. Moved it to the end.

1 0

Commit: r1422: Add support for disabling routing on unpaved roads and ferry routes.
by svn commit 08 Dec '09

08 Dec '09

Version 1422 was commited by markb on 2009-12-08 21:35:27 +0000 (Tue, 08 Dec 2009) Add support for disabling routing on unpaved roads and ferry routes. By default, ways are considered to be paved and not ferry routes Adding mkgmap:unpaved=yes/true/1 to a way will declare it to be unpaved and such ways will not be routed through if the GPS has been set to avoid unpaved roads. Similarly, tagging a way with mkgmap:ferry=yes/true/1 will cause it to be ignored for routing purposes if the GPS has been set to avoid ferry routes.

1 0

[PATCH v2] grok unpavedness
by Mark Burton 08 Dec '09

08 Dec '09

v2 - sans syntax error --------- Bloody typical, you wait around for ages hoping for a new routing capability to be added to mkgmap and then two come along on the same day. I've been trying to discover how unpavedness is encoded for at least 6 months. Every now and again, I return to think about it some more. Check and re-check the same old data structures. Very frustrating, no progress. Damn those cunning bastards at Garmin.... However, a month or two ago, I discovered that Table C contains more than just turn restrictions. I still don't know many of it's little secrets but, today, having exhausted all other possibilities, I finally twigged that Table C contains the key to understanding "unpavedness". Gotcha! The attached patch allows you to add either unpaved=yes/true/1 or paved=no/false/0 to a way and then it will be ignored for routing purposes when the GPS has been told to avoid unpaved roads. Not sure if those are the best tags to use - any thoughts? BTW - the unpaved road line type 0x0a has nothing to do with unpavedness, it's just a routable way that gets drawn as a dashed line (default rendering). Feedback, etc. Mark

3 2

[PATCH v2] grok unpavedness + ferry nature
by Mark Burton 08 Dec '09

08 Dec '09

v3 - turns out they handle ferry routes in a similar fashion as to unpaved roads so I've added support for avoiding them (when route=ferry tag is present) - untested here due to paucity of ferries in Cheshire but I have verified that the unpaved stuff still works. --------- v2 - sans syntax error --------- Bloody typical, you wait around for ages hoping for a new routing capability to be added to mkgmap and then two come along on the same day. I've been trying to discover how unpavedness is encoded for at least 6 months. Every now and again, I return to think about it some more. Check and re-check the same old data structures. Very frustrating, no progress. Damn those cunning bastards at Garmin.... However, a month or two ago, I discovered that Table C contains more than just turn restrictions. I still don't know many of it's little secrets but, today, having exhausted all other possibilities, I finally twigged that Table C contains the key to understanding "unpavedness". Gotcha! The attached patch allows you to add either unpaved=yes/true/1 or paved=no/false/0 to a way and then it will be ignored for routing purposes when the GPS has been told to avoid unpaved roads. Not sure if those are the best tags to use - any thoughts? BTW - the unpaved road line type 0x0a has nothing to do with unpavedness, it's just a routable way that gets drawn as a dashed line (default rendering). Feedback, etc. Mark

5 10

Change road_speed based on POIs
by Nakor 08 Dec '09

08 Dec '09

Hello, I remember some emails about changing road_speed based on POIS (lights, stops, bumps, ...) but I could not find them. Was this a patch or is this in mkgmap? If in mkgmap what is the commad-line option to activate it? Thanks, N.

1 0

Commit: r1421: Add barrier=border_control as an alias for amenity=border_control.
by svn commit 08 Dec '09

08 Dec '09

Version 1421 was commited by marko on 2009-12-08 09:43:38 +0000 (Tue, 08 Dec 2009) Add barrier=border_control as an alias for amenity=border_control.

1 0