March 2019 - mkgmap-dev - The mkgmap lists

Setting mapset-name?
by Andy Townsend 19 Mar '19

19 Mar '19

Hello, I'm in the process of moving some functionality from an old .osm processor into a mkgmap style, and I'd like to have both old and new styles on the device (a gpsmap64s) at the same time for comparison. Before I even got that far I couldn't find a way of changing the mapset name that is produced. The script I'm using is https://github.com/SomeoneElseOSM/mkgmap_style_ajt/blob/master/garmin_map_e… (be aware that that currently has some hardcoded paths in it). so I'm using "--gmapsupp" to create a ".img" file that I can copy to the device. ".../mkgmap/trunk/src/uk/me/parabola/mkgmap/combiners/GmapsuppBuilder.java" contains the default name of "OSM Map Set", and if I change the default there it does change the value I can see in the .img file. Despite that bit of code appearing to be reading an argument from somewhere, setting "--mapset name=" doesn't seem to work - mkgmap exits with "Invalid option: 'mapset-name'". Is there perhaps some order in which the arguments need to be applied? I've got one lot of input files (6*.osm.gz from splitter) some intermediate output files (6*.img) and then the final output from the --gmapsupp - gmapsupp.img, so it's not exactly clear what order would make sense. Best Regards, Andy

3 3

Having 2 mkgmap-generated files on one device at once
by Andy Townsend 18 Mar '19

18 Mar '19

Following on from the other question about setting the mapset name, the other problem is just having both files on the device at once. Both .img files were created using mkgmap using the --gmapsupp parameter. I have an existing "gmapsupp.img", and I've renamed the new test one that I am creating to "ajt2supp.img" and have also tried setting the description of it via '--description="AJT2D" '. Setting the description works, in that if that's the only mkgmap-generated map on the device that's the description I see from the maps available from "select map". However, if I have both the old "gmapsupp.img" and the new "ajt2supp.img"on the device I only see "OSM Street Map" (the old description), not "AJT2D". I'm guessing it's some other name or perhaps the argument order that's the problem. I've tried other name settings such as --family-id=3 --product-id=44 --mapname=63240002 --product-version=2 --series-name="AJT2S" --family-name="AJT2F" --area-name="AJT2A", as well as --description="AJT2D", but to no avail. Best Regards, Andy

4 4

Possible Indexing Problem
by Manfred Haiduk 10 Mar '19

10 Mar '19

Hi all last week i was playing around building new maps with mkgmap 4282 and the default style. Building smaller maps, i.e Nordrhein Westfalen, i don't see any problems but the last map i tried out was complete germany. And now it seems, that my device (GPSMAP 276Cx) will stuck while searching POIs or Adresses. Today i changed the image to be load onto the device and created it from MapSource instead the one build by mkgmap. The functionality is better, but even not 100%. My question for now is, is there a possibility to extract the index data out of the img File to check it on the PC and eventually modify the data ?

2 3

Commit r4283: document special case with relative path for option input-file given in a config file like template.args
by svn commit 08 Mar '19

08 Mar '19

Version mkgmap-r4283 was committed by gerd on Fri, 08 Mar 2019 document special case with relative path for option input-file given in a config file like template.args http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4283

1 0

mkgmap -c problem (relative paths)
by Ranko Jaksic 07 Mar '19

07 Mar '19

Hello, I use config files with mkgmap and define input-files using relative paths. Example from my config file "osm-options": mapname: 80100003 input-file: data/80100003.osm.pbf This works well when the config file is in the same directory where mkgmap is started. When invoked with "-c osm-options" mkgmap finds my input file just fine. To tidy up my environment I moved all my config files into a config subdirectory. Now when I invoke mkgmap with "-c config/osm-options" I get the following error: SEVERE (Main): .\config\data\80100003.osm.pbf: file .\config\data\80100003.osm.pbf doesn't exist It appears that mkgmap interprets my relative paths relative to the config file location, and not (as I expected) the mkgmap cwd! This seems to be a bug since the description for -c states: "The options are included as arguments of the executed command as if they had been specified on the command line." I tested using the latest r4282 on Windows. Regards, Ranko

3 5

Commit r4282: fix problem introduced with r4278: --remove-ovm-work-files stopped to work when --output-dir option is used to specify a different directory
by svn commit 04 Mar '19

04 Mar '19

Version mkgmap-r4282 was committed by gerd on Mon, 04 Mar 2019 fix problem introduced with r4278: --remove-ovm-work-files stopped to work when --output-dir option is used to specify a different directory http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4282

1 0

mkgmap Version r4278
by Manfred Haiduk 04 Mar '19

04 Mar '19

Hi all just thinking about as if i missed something. The option "remove-ovm-work-files" seems to do not work anymore, is it a bug or a new feature ? -- Best regards ##################################################### Manfred Haiduk, Zum Fischbach 9, D-52393 Hürtgenwald Germany e-mail mhaiduk(a)t-online.de #####################################################

2 1

Commit r4281: improve default style points, patch by Ticker Berkin:
by svn commit 02 Mar '19

02 Mar '19

Version mkgmap-r4281 was committed by gerd on Sat, 02 Mar 2019 improve default style points, patch by Ticker Berkin: Changes are: Always use 0x2f0c instead of 0x4e00 for amenity=toilet. 0x4e00 isn't findable. 0x2f0c is "Other:Rest Area/Tourist Info". add: tourism=resort [0x2b04 resolution 24] This is searchable under the "Lodgings" > "Resort" category on some devices Use 0x3200 instead of 0x660f for barrier=bollard barrier=...etc. 0x660f is "Land Features:Pillar" and so they all show in FIND, making searching for nearby features less useful. 0x3200 is a small point, that can be labeled with the type of barrier http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4281

1 0

Commit r4280: improve default style polygons, patch by Ticker Berkin:
by svn commit 02 Mar '19

02 Mar '19

Version mkgmap-r4280 was committed by gerd on Sat, 02 Mar 2019 improve default style polygons, patch by Ticker Berkin: Changes are: 0x17, which shows as "Park" in green, is currently used for these OSM objects: park, playground, common, garden, greenfield, meadow, grass, village_green, square/plaza Keep this mapping for leisure=park, playground Use 0x15 for landuse=village_green Use 0x1c for landuse=meadow, grass, greenfield, farmland Use 0x1d for leisure=common Use 0x20 for leisure=garden Use 0x25 for square/plaza Use 0x26 instead of 0x10 for landuse=farmyard 0x26 was unused. 0x10 is used landuse=residential Use 0x26 instead of 0x4e for landuse=farm Use 0x12 instead of 0x08 for landuse=retail 0x12 was unused. 0x08 is "Shopping Center" Use 0x12 instead of 0x05 for highway=services ie consider it a retail area - it normally includes shops, parking, fuel, eating places etc and isn't just a "Parking Lot". Someone suggested this change a few months ago but I can't remember who. Use 0x22 instead of 0x1e for historic=... 0x22 was unused. 0x1e is "Park" add natural=tundra [0x52 resolution 18] This is a standard Garmin type add natural=beach | natural=sand [0x53 resolution 20] This is Garmin type, sometimes labeled "Flat" or Sandbank,tidal/mud flat and the change was suggested by Nick / Minko on 27-Sep-2018 Use 0x0f instead of 0x0c for landuse=commercial 0x0f was unused. 0x0c is "Industrial Complex" Use 0x11 instead of 0x04 for military=danger_area This often covers a large area of other mixed use, and rendering it with partially transparent is much more informative Use 0x23 instead of 0x13 for amenity=... Use 0x24 instead of 0x13 for man_made=... 0x23 & 0x24 were unused. 0x13 is now just used for building Use 0x21 instead of 0x1f for tourism=... 0x21 was unused. 0x1f is "Park" http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4280

1 0

Commit r4279: improve default style lines, patch by Ticker Berkin:
by svn commit 02 Mar '19

02 Mar '19

Version mkgmap-r4279 was committed by gerd on Sat, 02 Mar 2019 improve default style lines, patch by Ticker Berkin: Changes are: Use 0x30 for leisure=track instead of treating it like a footpath. 0x30 was introduced in the last set of changes as the code for various sports tracks (gallop, raceway) Use 0x0b (Road) instead of 0x06 as the "hint" portion of a *_link. 0x0b was unused. 0x06 is used for highway=minor & highway=unclassified Use 0x11 instead of 0x07 for highway=cycleway 0x11 was unused. 0x07 is Alley and is used for bridleway, service... Use 0x17 for various linear barriers and also man_made=breakwater Use 0x1a for car ferries, 0x1b for other ferries. At the moment 0x1b is used for all ferries Use 0x26 instead of 0x10a02 for intermittent steam & drain http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4279

1 0