April 2013 - mkgmap-dev - The mkgmap lists

Commit: r2581: print location of first point of a road in warning reg. non-routable type usage
by svn commit 28 Apr '13

28 Apr '13

Version 2581 was committed by gerd on Sun, 28 Apr 2013 print location of first point of a road in warning reg. non-routable type usage

1 0

problems with style-file option
by Gerd Petermann 27 Apr '13

27 Apr '13

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) --style-file=<path-to-single-file that is a zip (or jar) archive> 4) --style-file=<path-to-single-file with .style or .csv extension> a) no --style option b) --style=default c) --style=<any other style name> The combinations of these parms do not always give expected results. I tested this: a) copy the distributed styles to c:\mystyles b) create a copy of default in c:\mystyles\default_copy c) create a zip file c:\temp\mystyles.zip containing this directory d) create a zip file c:\temp\default_copy.zip containing directory default_copy and the corresponding files Results: D:\mkgmap\dist>java -jar mkgmap.jar --style-file=c:\mystyles e:\bremen\*.o5m gives error message "Could not open style c:\mystyles" I'd prefer that it would try to read directory default or that it detects the missing --style option. D:\mkgmap\dist>java -jar mkgmap.jar --style-file=c:\mystyles\xyz e:\bremen\*.o5m gives "Could not open style c:\mystyles\xyz" That's ok, maybe "style-file c:\mystyles\xyz doesn't exist" would be clearer? D:\mkgmap\dist>java -jar mkgmap.jar --style-file=c:\temp\mystyles.zip e:\bremen\*.o5m gives no error message, but used style contours_ft instead of default . That's not ok. java -jar mkgmap.jar --style=default --style-file=c:\temp e:\bremen\*.o5m gives "Could not open style default" That's ok. I did not yet try the variant 4) as this seems not to be documented very well and is probably not in use. Would it be ok to change mkgmap so that it works as I suggested? Ciao, Gerd

2 1

check-styles
by nwillink 27 Apr '13

27 Apr '13

Hi Gerd What a great tool ! Perhaps some suggestions. I keep various styles and --check-styles lists all the errors for each style. a) perhaps list the name of the style first then the possible errors? b) separate each style error list using an extra carriage return? c) perhaps enable checking on one style only using style=mystyle --check-styles? Another query: One of the errors concerns polygons : Warning: invalid type 0x3D00 for POLYGON in style file polygons, line 75 line 175 : landuse=pond [0x3D00 resolution 24] This polygon might be invalid using mkgmap but Garmin uses the 0x3000 to 0x3FFF+ for different water features. As I said, brilliant work! ..Nick -- View this message in context: http://gis.19327.n5.nabble.com/check-styles-tp5758614.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

3 8

Commit: r2579: simplify code: use readStyle were possible
by svn commit 27 Apr '13

27 Apr '13

Version 2579 was committed by gerd on Sat, 27 Apr 2013 simplify code: use readStyle were possible

1 0

how to add upload=false in the splitted OSM files
by maning sambale 26 Apr '13

26 Apr '13

Dear everyone, I am splitting a large OSM file using splitter.jar r202. The OSM data will be shared to others for comparing OSM tags in JOSM. I want to add the upload=false in every splitted file. Like this: <osm version="0.6" upload="false"> but the splitter only gives me this: <osm version='0.5' generator='splitter'> -- cheers, maning ------------------------------------------------------ "Freedom is still the most radical idea of all" -N.Branden wiki: http://esambale.wikispaces.com/ blog: http://epsg4253.wordpress.com/ ------------------------------------------------------

2 6

Commit: r2577: Add part function for styles.
by svn commit 25 Apr '13

25 Apr '13

Version 2577 was committed by wanmil on Thu, 25 Apr 2013 Add part function for styles. --Franco Bez

1 0

Commit: r2576: add type 0x16 to the list of routable line types
by svn commit 25 Apr '13

25 Apr '13

Version 2576 was committed by gerd on Thu, 25 Apr 2013 add type 0x16 to the list of routable line types

1 0

name-tag-list_v1.patch
by Gerd Petermann 24 Apr '13

24 Apr '13

Hi all, attached is a patch that removes the incomplete support for the name-tag-list parameter in the style options file. Please make sure that you specify this parameter on the command line or with a config file given in the -c option. If mkgmap finds the name-tag-list parameter in the style options file, it will print a warning to stderr. If I here no complains, I will commit this next monday. The compiled binary is here: http://files.mkgmap.org.uk/download/114/mkgmap.jar Ciao, Gerd

4 7

builtin-tag-list
by GerdP 24 Apr '13

24 Apr '13

Hi programmers, while looking at the name-tag-list option I wondered again why we have so many different ways to maintain the "usedTags" HashMap which is finally used to filter OSM data in class OsmHandler. 1)We have a list coded in /resources/styles/builtin-tag-list. The tags listed here can be found in the java sources, but not all tags used in the sources are listed. 2) Some sources use hard coded tag names and they have a method getUsedTags() to tell this fact to other routines. 3) Some hard coded tags are used in StyledConverter but they are added to the map in the RoutingHook, e.g. "access", "highway". I'd prefer to have a common way to keep the map up to date, and I think that the best solution is to add the tag names in the source where they are used (and if they are used). What was the idea behind the builtin-tag-list ? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/builtin-tag-list-tp5758284.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

2 3

New filter function trim
by Franco Bez 24 Apr '13

24 Apr '13

Hi all, I've written a new filter function called trim. It returns the first part of a value up to the first occurance of a separator. If the separator is not found it just returns the value. Example: maybe you have a values like this destination=München;Landsberg;Augsburg;Ammersee destination=Kaufbeuren;Neugablonz;Mauerstetten;Pforzen and you want just the first part "München", or "Kaufbeuren" '${destination|trim:;}' will do the trick. with destination=München/Landsberg/Augsburg/Ammersee destination=Kaufbeuren/Neugablonz/Mauerstetten/Pforzen use '${destination|trim:/}' Find attached the new TrimFilter.java a diff for ValueBuilder.java Ciao, Franco

6 12