- mkgmap-dev - The mkgmap lists

Commit: r1151: Add support for extended type attributes.
by svn commit 27 Aug '09

27 Aug '09

Version 1151 was commited by markb on 2009-08-27 23:25:16 +0100 (Thu, 27 Aug 2009) Add support for extended type attributes. See comment near the top of ExtTypeAttributes.java for an explanation of what is implemented and how to specify the attribute values.

1 0

Commit: r1150: Add support for 'except' tag in turn restrictions.
by svn commit 27 Aug '09

27 Aug '09

Version 1150 was commited by markb on 2009-08-27 23:25:11 +0100 (Thu, 27 Aug 2009) Add support for 'except' tag in turn restrictions. Doesn't appear to work for emergency vehicles or foot traffic.

1 0

how to qlandkarte or qlandkartegt
by Robert Joop 27 Aug '09

27 Aug '09

speaking of sea polygons and the numerous test builds... i'm a little confused as on which program to use (to view the result without copying it to a garmin GPSr) and how - qlandkarte or qlandkartegt (which recently appeared in debian sid), and which files to load (or import?), single tile .img (from mkgmap), gmapsupp.img or the .tdb from mkgmap, or the gmapsupp.img from gmt (as the linux gmaptool is named). what works best for you? for example it seems that i can load a tile in qlandkarte, but loading a second tile does not make it appear. any hints very much appreciated! due to the strange behaviour of qlandkarte (or me not using them properly?), i always copy the final gmapsupp.img to my GPSr... thank you, rj

3 3

[Fwd: [PATCH v4a] sea polygons]
by Christian Gawron 27 Aug '09

27 Aug '09

Sorry, I replied to Robert instead of the list. Best wishes Christian

8 20

Commit: r1149: Raise an error if you give a --style-file argument and the location is a file that does not
by svn commit 27 Aug '09

27 Aug '09

Version 1149 was commited by steve on 2009-08-27 16:17:55 +0100 (Thu, 27 Aug 2009) Raise an error if you give a --style-file argument and the location is a file that does not exist.

1 0

options: description
by Valentijn Sessink 27 Aug '09

27 Aug '09

Steve, list, This may be a better description of --description, it sort of warns for the description that splitter puts in the args file. Best regards, Valentijn -- Durgerdamstraat 29, 1507 JL Zaandam; telefoon 075-7074579

3 8

[PATCH v5] - support for extended type attributes
by Mark Burton 27 Aug '09

27 Aug '09

v5 - added support for facility (point type 0x010903) and also now catches and reports exceptions incurred during processing of attributes. A facility point can have a mkgmap:xt-facilities attribute which is a bitmask made from these values: 0x000001 boat ramp 0x000002 drinking water 0x000004 restrooms 0x000008 picnic area 0x000010 campground 0x000020 marina 0x000040 fuel 0x000080 marine supply 0x000100 bait and tackle 0x000200 groceries 0x000400 restaurant 0x000800 water/electric hook-up 0x001000 boat/motor rental 0x002000 guide service 0x004000 lodging 0x008000 dump station 0x010000 handicap accessible ------------------------ v4 - no functional change, just reworked slightly to improve efficiency. I've tested this stuff with noddy examples but as I don't expect anyone is in a great rush to use it big time, we will have to wait to see what issues emerge (from the deep?) Anyway, as all of this code should have no effect on map elements without extended types, I reckon it should be safe to commit. So unless anyone has any problems with that, I shall commit it later this week and then at least it's there for people to dabble with. If you do try it out, please report results. --------------------------- v3 - more tweaks to lights + lines & areas "morse" light type now takes the morse letter to flash, e.g. "morse A" lights can be tagged as having a "racon" (you'll have to google it like I did!) by setting mkgmap:xt-racon to yes. Depth areas (type 0x0103xx) can have the depth attribute and lines 0x010105 to 0x010107 (contour, overhead cable, bridge) can have height. There is a new mkgmap:xt-style attribute that takes a 16 bit value. The bottom 4 bits specify a colour and bits 8-14 specify a line style. See the cgpsmapper manual for the supported colours and styles. As an example, a value of 0x3004 means red line like this +++++++ This can be used on lines with types 0x0104xx, 0x0105xx and 0x0106xx. You can also use the xt-style (colour part only) attribute on points of type 0x010500 which are labels with coloured text. The point's name tag is shown on the map in the colour you specify. Could be useful. There's still a bit more that could be done on on the light flash sequence encoding but as it's rather unlikely that anyone will every want to use that, I'm not bothering for the moment. So, the job is pretty much done. As usual, all feedback is welcome. -------------------------- v2 - moving swiftly on. Added support for lights and reworked a few things. mkgmap:xt-foundation-colour is now just mkgmap:xt-colour mkgmap:xt-light-colour has been replaced with mkgmap:xt-light (more on this below) mkgmap:xt-light-type is now just mkgmap:xt-type Light colour, range (in nm) and angle is now specified with the mkgmap:xt-light tag - the values are just separated with commas, and only the colour is required for simple lights. All angles are in degrees. So, for example: mkgmap:xt-light=red (a red light) mkgmap:xt-light=red,5 (... visible at up to 5 nm) mkgmap:xt-light=red,5,172 (... sector starts at 172 degrees) The sector start angle only makes sense if you have multiple lights defined (separate light defs with one of /;:) - for example: mkgmap:xt-light=red,5,172/green,5,230/unlit,,300 you can add a text note, international designator or local designator to a buoy or light with: mkgmap:xt-note=hello world mkgmap:xt-int-desig=ABC mkgmap:xt-local-desig=XYZ These show up in the POI properties window in mapsource. There is also: mkgmap:xt-height-above-foundation (a height) mkgmap:xt-height-above-datum (a height) mkgmap:xt-leading-angle (an angle) you can now specify multiple period values to give a flash sequence but, unfortunately, it only encodes 2 values at the moment, the encoding for more than 2 values is yet to be discovered. The full range of light colours is now supported: "unlit", "red", "green", "white", "blue", "yellow", "violet", "amber" So, lights, buoys, obstructions are now fairly well catered for so it's probably time to look at lines and areas. ------------------------------------------------ Yo Landlubbers, Here's the first cut at encoding support for extended type attributes. This is mostly concerned with marine entities like (wreck depths, buoy types, light types, colours, etc.) As there is quite a lot of it and I haven't sussed it all out yet, I thought it would make sense to post patches as I go along so that people can try it out and find the bugs sooner rather than later. The attribute values are supplied as special tags with a mkgmap:xt- prefix. So, for example, mkgmap:xt-depth=40.6m specifies the depth of something (in metres). This first tranche supports: Point types 0x0102xx (buoys/beacons) can have: mkgmap:xt-foundation-colour (a colour name from list FC below) mkgmap:xt-light-colour (a colour name from list LC below) mkgmap:xt-light-type (a type name from list LT below) mkgmap:xt-period (optional period in secs (not limited to integer) Point types 0x0103xx (entities with depth/height) and 0x0104xx (obstructions) mkgmap:xt-depth (a depth with optional units (ft or m) default is m) mkgmap:xt-height (alias for, and mutually exclusive to, xt-depth) mkgmap:xt-position (an optional position from list P below) These attributes are turned into a sequence of bytes that are embodied in the map object. For testing purposes you can also specify those bytes explicitly as a sequence of hex digits using the mkgmap:xt-extra-bytes tag but you won't want to use that unless you are working on attribute value encoding (like me!) Next up will be lights which I understand how to encode except for multiple lights and angles - still working on that. Then will come lines and areas. All feedback welcome. BTW a good source of info is the cgpsmapper manual which is readily available on the net. It has a chapter on marine types. --------------------------------- List FC "red", "green", "yellow", "white", "black", "black-yellow", "white-red", "black-red", "white-green", "red-yellow", "red-green", "orange", "black-yellow-black", "yellow-black", "yellow-black-yellow", "red-white", "green-red-green", "red-green-red", "black-red-black", "yellow-red-yellow", "green-red", "black-white", "white-orange", "orange-white", "green-white" List LC "unlit", "red", "green", "white", There is possibly some more light colours but I don't yet know how to encode them so we should stick with these for the moment. List LT "fixed", "isophase", "flashing", "group flashing", "composite group flashing", "occulting", "group occulting", "composite group occulting", "long flashing", "group long flashing", "morse", "quick", "group quick", "group quick and long flashing", "interrupted quick", "very quick", "group very quick", "group very quick and long flashing", "interrupted very quick", "ultra quick", "interrupted ultra quick", "fixed and occulting", "fixed and group occulting", "fixed and isophase", "fixed and flashing", "fixed and group flashing", "fixed and long flashing", "alternating", "alternating occulting", "alternating flashing", "alternating group flashing" The morse type takes a letter argument but I don't know how to encode that yet. List P "unknown", "doubtful", "existence doubtful", "approximate", "reported"

3 2

ant test supposed to work?
by Simon Josefsson 26 Aug '09

26 Aug '09

In building other java applications, I'm used to checking that the build is sane by invoking 'ant test'. This fails for me with mkgmap. Is this a known problem, or something I can fix? /Simon jas@mocca:~/src/mkgmap$ ant Buildfile: build.xml prepare: [mkdir] Created dir: /home/jas/src/mkgmap/build/classes compile: [javac] Compiling 271 source files to /home/jas/src/mkgmap/build/classes [javac] Note: /home/jas/src/mkgmap/src/uk/me/parabola/mkgmap/general/RoadNetwork.java uses or overrides a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] Note: Some input files use unchecked or unsafe operations. [javac] Note: Recompile with -Xlint:unchecked for details. build: [copy] Copying 35 files to /home/jas/src/mkgmap/build/classes dist: [mkdir] Created dir: /home/jas/src/mkgmap/dist [mkdir] Created dir: /home/jas/src/mkgmap/dist/doc/api [jar] Building jar: /home/jas/src/mkgmap/dist/mkgmap.jar [copy] Copying 8 files to /home/jas/src/mkgmap/dist/doc [copy] Copying 34 files to /home/jas/src/mkgmap/dist BUILD SUCCESSFUL Total time: 3 seconds jas@mocca:~/src/mkgmap$ ant test Buildfile: build.xml prepare: compile: build: build-test: [mkdir] Created dir: /home/jas/src/mkgmap/build/test [javac] Compiling 28 source files to /home/jas/src/mkgmap/build/test [javac] /home/jas/src/mkgmap/test/func/lib/RangeMatcher.java:16: package org.hamcrest does not exist [javac] import org.hamcrest.BaseMatcher; [javac] ^ [javac] /home/jas/src/mkgmap/test/func/lib/RangeMatcher.java:17: package org.hamcrest does not exist [javac] import org.hamcrest.Description; [javac] ^ [javac] /home/jas/src/mkgmap/test/func/lib/RangeMatcher.java:26: cannot find symbol [javac] symbol: class BaseMatcher [javac] public class RangeMatcher extends BaseMatcher<Integer> { [javac] ^ [javac] /home/jas/src/mkgmap/test/func/lib/RangeMatcher.java:46: cannot find symbol [javac] symbol : class Description [javac] location: class func.lib.RangeMatcher [javac] public void describeTo(Description description) { [javac] ^ [javac] /home/jas/src/mkgmap/test/func/SimpleTest.java:70: cannot access org.hamcrest.Matcher [javac] class file for org.hamcrest.Matcher not found [javac] assertThat("RGN size", size, new RangeMatcher(138300)); [javac] ^ [javac] /home/jas/src/mkgmap/test/func/SimpleTest.java:108: cannot find symbol [javac] symbol : method assertThat(java.lang.String,int,func.lib.RangeMatcher) [javac] location: class func.SimpleTest [javac] assertThat("RGN size", size, new RangeMatcher(2762)); [javac] ^ [javac] /home/jas/src/mkgmap/test/func/route/SimpleRoute.java:56: cannot find symbol [javac] symbol : method assertThat(java.lang.String,int,func.lib.RangeMatcher) [javac] location: class func.route.SimpleRoute [javac] assertThat("RGN size", size, new RangeMatcher(141999)); [javac] ^ [javac] /home/jas/src/mkgmap/test/func/route/SimpleRoute.java:84: cannot find symbol [javac] symbol : method assertThat(java.lang.String,int,func.lib.RangeMatcher) [javac] location: class func.route.SimpleRoute [javac] assertThat("RGN size", size, new RangeMatcher(2787)); [javac] ^ [javac] 8 errors BUILD FAILED /home/jas/src/mkgmap/build.xml:100: Compile failed; see the compiler error output for details. Total time: 1 second jas@mocca:~/src/mkgmap$

2 4

Commit: r1148: Better ferry behaviour.
by svn commit 26 Aug '09

26 Aug '09

Version 1148 was commited by steve on 2009-08-26 21:43:14 +0100 (Wed, 26 Aug 2009) Better ferry behaviour. - Valentijn Sessink

1 0

"board ferry" mystery not a mystery after all
by Valentijn Sessink 26 Aug '09

26 Aug '09

Hello list, The current ferry routes don't tell me to board the ferry (I've written about that before). However, if I use ferry type 0x1b instead of 0x1a, my Garmin Nüvi shows a nice boat icon on the track, it tells me to "board ferry". The other behaviour so far seems identical to type 0x1a. So I would kindly recommend the attached one-bit (it's even the least significant one) patch, changing the ferry route type from 0x1a to 0x1b. Best regards, Valentijn -- Durgerdamstraat 29, 1507 JL Zaandam; telefoon 075-7074579

1 0