June 2013 - mkgmap-dev - The mkgmap lists

overview map
by GerdP 04 Jun '13

04 Jun '13

Hi all, finally I've merged r2629 into trunk. A brief description of the changes: 1) new or changed options --overview-levels like levels, specifies additional levels that are to be written to the overview map. Counting of the levels should continue. Up to 8 additional levels may be specified, but the lowest usable resolution with MapSource seems to be 11. --remove-ovm-work-files If overview-levels is used, mkgmap creates one additional file with the prefix ovm_ for each map (*.img) file. These files are used to create the overview map. With option --remove-ovm-work-files=true the files are removed after the overview map was created. The default is to keep the files. --polygon-size-limits=limits code Allows to specify different min-size-polygon values for each resolution. Sample: --polygon-size-limits="24:12, 18:10, 16:8, 14:4, 12:2, 11:0" If a resolution is not given, mkgmap uses the value for the next higher one. For the given sample, resolutions 19 to 24 will use value 12, resolution 17 and 18 will use 10, and so on. Value 0 means to skip the size filter. Note that in resolution 24 the filter is not used. 2) Optimizations: - The polygon filter allows larger polygons. - SeaGenerator generates fewer "sea-only" and "land-only" polygons when precomp-sea is used. Both reduce the img size, esp. for maps containing large "sea only" areas. 3) Changes regarding styles: - The support for the out-aged map-features.csv file was removed - Level ranges can now use min-max or max-min - Usage of polygon type 0x4a will be flagged with --check-styles 4) Other changes - A few checks are performed regarding the plausibility of the given options and input files to help beginners. -- View this message in context: http://gis.19327.n5.nabble.com/overview-map-tp5763471.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

5 4

[Patch v1] overview map copyrights
by GerdP 03 Jun '13

03 Jun '13

Hi, the overview map should contain the copyright messages of all combined maps as well as the combined licence infos. Attached is a patch that implements this: overview_copyrights_v1.patch <http://gis.19327.n5.nabble.com/file/n5763803/overview_copyrights_v1.patch> A compiled binary is here: http://files.mkgmap.org.uk/download/128/mkgmap.jar @Steve: The copyright block in the *.tdb file is filled with the licence infos, not the copyrights. Should that also be changed? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-overview-map-copyrights-tp5763803.h… Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 2

Commit: r2640: Remove unmaintained/unused gui code.
by svn commit 03 Jun '13

03 Jun '13

Version 2640 was committed by steve on Mon, 03 Jun 2013 Remove unmaintained/unused gui code.

1 0

Commit: r2639: write_unclosed_shapes_v1.patch: Ignore closing last point of a shape when writing to the img file. This reduces the file size by ~ 2%.
by svn commit 03 Jun '13

03 Jun '13

Version 2639 was committed by gerd on Mon, 03 Jun 2013 write_unclosed_shapes_v1.patch: Ignore closing last point of a shape when writing to the img file. This reduces the file size by ~ 2%.

1 0

mkgmap javadoc
by GerdP 03 Jun '13

03 Jun '13

Hi programmers, I tried to fix the warning which are produced with ant javadoc A few ones are left, I don't know how to handle them: ... [javadoc] Constructing Javadoc information... [javadoc] Standard Doclet version 1.6.0_43 [javadoc] Building tree for all the packages and classes... [javadoc] D:\mkgmap\src\uk\me\parabola\imgfmt\app\mdr\Mdr5Record.java:119: warning - Tag @see:illegal character: "123" in "{@link #setMdr20set(int[])}" [javadoc] D:\mkgmap\src\uk\me\parabola\imgfmt\app\mdr\Mdr5Record.java:119: warning - Tag @see:illegal character: "64" in "{@link #setMdr20set(int[])}" [javadoc] D:\mkgmap\src\uk\me\parabola\imgfmt\app\mdr\Mdr5Record.java:119: warning - Tag @see: reference not found: {@link #setMdr20set(int[])} [javadoc] D:\mkgmap\src\uk\me\parabola\mkgmap\gui\AppLayout.java:61: warning - @noinspection is an unknown tag. [javadoc] D:\mkgmap\src\uk\me\parabola\mkgmap\gui\FileOptions.java:138: warning - @noinspection is an unknown tag. [javadoc] D:\mkgmap\src\uk\me\parabola\mkgmap\gui\MainFileList.java:223: warning - @noinspection is an unknown tag. [javadoc] Building index for all the packages and classes... [javadoc] Building index for all classes... [javadoc] Generating D:\mkgmap\doc\api\stylesheet.css... [javadoc] 6 warnings Gerd -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-javadoc-tp5763480.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 2

licence and copyright in overview map
by GerdP 02 Jun '13

02 Jun '13

Hi all, I am not sure what to use in the overview map (and how) option --copyright-message can be used to place a msg into each *.img file. This message is displayed in GPSMapEdit -> File -> Map Properties as "Copyright information", preceded by the text "PROGRAM LICENCED UNDER GPL V2" which is always added by mkgmap. option --license-file can be used to place license messages into each *.img file. MapSource displays these lines when you click on the Copyright button in the map manager (German : "Kartenproduktmanager") When reading *.img files, mkgmap r2636 cannot (yet) extract the data from the "--copyright-message", it can only extract the "--license-file" info. Reg. the overview map: r2636 places the "--license-file" info into the *.tdb file and into the place where the "--copyright-message" info would normally go. I would prefer to extract the "--copyright-message" from the ovm_*.img, but I don't know how complicated that is (at least it seems not simple), so for now I've committed r2637: evaluate options --license-file and --copyright-message when creating the overview map. @Steve: TreFileReader.getCopyrights() contains this comment: // TODO This needs the label section to work... Is this the right place to extract the data? I think it should better be placed in uk.me.parabola.imgfmt.app.map.MapReader as this has the labels ? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/licence-and-copyright-in-overview-map-tp5763… Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 4

Handling of refs
by WanMil 02 Jun '13

02 Jun '13

Hi, I tried to remove the name from motorway_links and other _links. My first approach was simple: highway=motorway_link { delete name } This changed nothing! Mmmh, I looked into the source code and observed that the action { name 'abc' } is different to { set name='abc' } After using { name 'abc' } it is not possible to remove or to change the name using the style. So I changed all rules to { set name='abc' } This improved things a bit but the refs were still displayed. Then I noticed that there is a lot of automatic name handling in the StyledConverter: The ref is composed of the tags mkgmap:display_name, ref, int_ref, nat_ref and reg_ref. If there is no name set the composed ref is used as name. So the final rule to remove the name from the motorway_link is highway=motorway_link { delete name; delete mkgmap:display_name; delete ref; delete ref; delete int_ref; delete nat_ref; delete reg_ref } I think this is not very intuitive?! Without having a look into the source code I would have never been able to remove the name. I wonder if it would be better to implement these hard coded rules within the style so anybody can see what happens and can easily influence the naming: 1. Create a new mkgmap tag mkgmap:ref which is used to set the ref field in the garmin map. Without setting mgkmap:ref the ref field will be empty. This makes mkgmap:display_name superfluous. Another advantage is that the ref, nat_ref etc. tags can be removed from the builtin-tag-list. 2. Set the name using the tag mkgmap:name. Remove the { name 'abc' } action. This might be controversial and requires changes in all styles. What do you think? WanMil

5 8

GPSMapEdit warnings
by GerdP 01 Jun '13

01 Jun '13

Hi programmers, when I open an img file produced with mkgmap and look at File -> Message log I see several warnings, see below. I guess a few of the listed problems are simply blowing up the img file a little bit, but the first ones seem to be real errors? Gerd Loading data from file 'E:\Garmin\velomap\niedersachsen\66550012.img'... WARNING: Unexpected format of input data. Unexpected position of POI. It will be ignored. WARNING: Unexpected format of input data. Unexpected position of POI. It will be ignored. ... WARNING: Unexpected format of input data. NodeID=840552 is not identified. WARNING: Unexpected format of input data. NodeID=840574 is not identified. WARNING: Unexpected format of input data. External node 840563 lost at (S127°44.9414' E10°32.3181'). WARNING: Unexpected format of input data. External node 840541 lost at (S127°44.9414' E10°32.3246'). WARNING: Unexpected format of input data. External node 840585 lost at (S127°44.9414' E10°32.3426'). WARNING (offset 23494h): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 234B9h): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 2351Ah): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 25E45h): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 25E8Fh): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 26F5Ch): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 26F68h): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 2700Ah): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 27039h): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 27052h): Some points are repeating in the polyline/polygon. The repeating points are removed. WARNING (offset 21BDBh): Polygon element has zero area. It will be ignored. WARNING (offset 21BDBh): Object does not contain any point. The object will be ignored. WARNING (offset 63FB0h): Polygon element has zero area. It will be ignored. WARNING (offset 63FB0h): Object does not contain any point. The object will be ignored. WARNING (offset 8BBBCh): Polygon element has zero area. It will be ignored. WARNING (offset 8BBBCh): Object does not contain any point. The object will be ignored. WARNING (offset B2C27h): Polygon element has zero area. It will be ignored. WARNING (offset B2C27h): Object does not contain any point. The object will be ignored. WARNING (offset 2AA1C0h): Polygon element has zero area. It will be ignored. WARNING (offset 2AA1C0h): Object does not contain any point. The object will be ignored. 35 warning(s). Load time is 4.55 s. -- View this message in context: http://gis.19327.n5.nabble.com/GPSMapEdit-warnings-tp5763678.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0

Download page has only old mkgmap versions
by Thorsten Kukuk 01 Jun '13

01 Jun '13

Hi, http://www.mkgmap.org.uk/download/mkgmap.html lists mkgmap-r2620 as newest version. Does the current code not build or why is it not updated? If we announce the version with overview support, it should be downloadable somewhere ;) Thanks, Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)

2 1

[Patch v1] write unclosed shapes
by GerdP 01 Jun '13

01 Jun '13

Hi all, while testing the overview map code, I noticed that it is not necessarey to write closed shapes (first = last point). Within mkgmap however, we sometimes detect a shape by testing this. So, I think it is a good idea to ignore the obsolete last point while writing to and add it (if needed) when reading from an img file. This reduces run time a little bit and the size of the img files is ~ 2% smaller. Attached patch implements this, the binary is here: http://files.mkgmap.org.uk/download/127/mkgmap.jar write_unclosed_shapes_v1.patch <http://gis.19327.n5.nabble.com/file/n5763674/write_unclosed_shapes_v1.patch> Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Patch-v1-write-unclosed-shapes-tp5763674.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

1 0