Re: [mkgmap-dev] check-styles

Hi Gerd I see what the problem is I had 0x3d00 for this polygon 'meaning' 0x3d Strangely, I have encountered subtypes for types 100 in some 'older' topo maps. However, 0x3d00 can only mean 0x3d as the highest polygon seems to be 0x1ff1f have tested: 0x03d (invalid) 0x03d0 (invalid)

Re: [mkgmap-dev] check-styles

Hi Nick, I see what the problem is I had 0x3d00 for this polygon 'meaning' 0x3d Strangely, I have encountered subtypes for types 100 in some 'older' topo maps. However, 0x3d00 can only mean 0x3d as the highest polygon seems to be 0x1ff1f Welll, a type 0x1 is an extended type.

[mkgmap-dev] Commit: r2579: simplify code: use readStyle were possible

Version 2579 was committed by gerd on Sat, 27 Apr 2013 simplify code: use readStyle were possible ___ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

[mkgmap-dev] Commit: r2580: - correct check-styles: overlays are not used for points and polygons

Version 2580 was committed by gerd on Sat, 27 Apr 2013 - correct check-styles: overlays are not used for points and polygons - separate code for check-styles and list-styles option, check only a single style if --style was used. ___ mkgmap-dev mailing

Re: [mkgmap-dev] check-styles

Afaik there is no way to write a sub type for lines or polygons, so we may change mkgmap to read 0x??00 as 0x?? when used with a line or polygon. I agree polygons with values 100 can’t have subtypes given the present typfiles please check: do you have an overlays file in your style? If

Re: [mkgmap-dev] check-styles

Hi Nick, okay. I've just committed r2580. I've implemented some of the cosmetic changes that you suggested, and - more important - fixed the error in the overlays handling. The binary is here: http://files.mkgmap.org.uk/download/115/mkgmap.jar Ciao, Gerd Date: Sat, 27 Apr 2013 01:14:54

Re: [mkgmap-dev] check-styles

Excellent Thanks again, Gerd have a nice w/e Nick From: GerdP [via GIS] Sent: Saturday, April 27, 2013 9:22 AM To: nwillink Subject: Re: check-styles Hi Nick, okay. I've just committed r2580. I've implemented some of the cosmetic changes that you suggested, and - more important - fixed

[mkgmap-dev] problems with style-file option

Hi all, while fixing a problem in the check-styles option I found (again) some issues regarding the --style-file and --style option. The current implementation in mkgmap r2580 allows the following: 1) no --style-file option 2) --style-file=path-to-directory 3)

Re: [mkgmap-dev] problems with style-file option

Hi Gerd I had the same problem in that mkgmap expected the full path name - hence my earlier question about it being able to check individual styles ..Nick -- View this message in context: http://gis.19327.n5.nabble.com/problems-with-style-file-option-tp5758739p5758758.html Sent from the

Re: [mkgmap-dev] mkgmap style: resolutuion and level vs. GARMIN device: zoom and map-detail settings

Hi Felix, do you happen to have a link to the map toolkit documentation ? The only documents I can find in the internet are http://www.maptk.dnsalias.com/MapTk/MapTk_en.pdf http://www.maptk.dnsalias.com/MapTk/MapTk_de.pdf There is some talk about levels, but not a single word about resolutions.

Re: [mkgmap-dev] Commit: r2578: tweaks to option --check-styles:

Am 26.04.2013 11:14, schrieb svn commit: - print all warnings to stdout (one was printed to stderr by mistake) Hi Gerd, would it be possible to print out also the osm-way-id? I get actually some reports, but my style is ok, so I would like to investigate why these reports occur. Henning

Re: [mkgmap-dev] Commit: r2578: tweaks to option --check-styles:

Hi Henning, please try r2580 first if you use an overlays file. The problem is detected at a stage were the OSM id is not known. I can try to report details like a name. We can also add the OSM id to all map elements with the cost of 8 additional bytes for each element. Ciao, Gerd Henning