July 2014 - mkgmap-dev - The mkgmap lists

How to remove an index from an existing map
by Bernhard Hiller 04 Jul '14

04 Jul '14

Whenever more than one map exists on an Oregon, the indices of all those maps are used for POI search reagrdless if the maps are "enabled" or not. When the areas of maps do overlap, several POIs are listed twice (or even more often depending on the number of maps). Since I use some POI codes differently from the standard (combined with my own "language pack"), this leads to even more confusion. Hence I'd like to know if - and how - and index can be removed from an existing map. In case that the gmapsupp.img file is created from precompiled tiles (e.g. VeloMap), is it possible to change the commandline such that the gmapsupp won't contain an index (no, just omitting the --index option does not do the trick, despite a file size of 330 MB vs. 337 MB fro Bavaria)?

4 6

Address boundary rules for South Africa
by Ben Konrath 03 Jul '14

03 Jul '14

Hi, Here's a patch to add address boundary rules for South Africa. Thanks, Ben

2 3

Unicode maps showing locked or not found on GPS units
by Felix Hartmann 02 Jul '14

02 Jul '14

Hi, could some people please test with their maps using unicode on their GPS (--code-page=65001) and maybe also report FID (family-ID) used for maps. I have the problem that some users report the maps show up as locked! (maps created with mkgmap version 3300 as of June 18) So far problematic: Garmin GPSMaps 64 - FID 6371 - sent from Mac OSx Basecamp/Map Install. Garmin Edge 1000 - FID=6531 - sent via?? Works as tested below ( sent via Mapsource, Mapinstall (Windows) and gmapsupp.img created by mkgmap.jar (java 1.7 windows) ): Garmin Oregon 600 - FID 6365 works... Garmin etrex 30 - FID 6365, works... Works without problems as long as no code-page other than latin1 characters are in the map AND is sent via Mapsource or MapInstall (Windows) - does not work if gmapsupp.img created by mkgmap! Problems - even German Umlauts (ÖÄÜ or "french" accents like é) are not displayed correctly anymore (instead split into two funky looking characters). Therefore for old units --latin1 is still the better option for old devices for most european countries. Garmin Vista HCx - FID=6365 So it's clear that there is something wrong in the way mkgmap.jar creates gmapsupp.img for maps with Unicode - though it does work for newer devices with full unicode support. Mind though I did not check on the unit itself if cyrillic or arrabic script is actually working. BTW 2. -- It would be great if there is a short-code like --latin1 for unicode too! E.g. --unicode instead of --code-page=65001, just for simplicity... -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org

3 10

Routing speeds on Oregon 600/400
by Bernhard Hiller 01 Jul '14

01 Jul '14

Chapter 4.6.5 of the style manual shwos a table with road speeds and its corresponding "highest speeds". I created a small test map with roads of ca. 100 km length of all 5 road_types and added speed limits which translate into the 8 different road_speed codes with the current (v3310) default style. Following table shows my car navigation results on an Oregon 600 with current firmware (3.90): Roadspeed Distance Time Speed Simulationspeed 7 99,9 00:53:27 112,14 254 6 99,7 00:56:41 105,53 130 5 100 01:00 100,00 100 4 99,5 01:16 78,55 90 3 100 01:34 63,83 70 2 99,9 02:03 48,73 50 1 99,6 03:06 32,13 30 0 100 06:09 16,26 16 The "Speed" is calculated by dividing the distance to destination by the time to destination; the "Simulationspeed" is the speed shown on the device when you select the simulation option. The speeds do not depend on the road_type value. The speeds for classes 0, 1, 2, 3, and 7 are multiples of 10mph. When using a different routing type (e.g. pedestrian), the simulation speed did not change (i.e. a pedestrian "walking" at 50 km/h...), but the calculated time to destination changed (i.e. a pedestrian was doing ca 5 km/h, a cyclist ca. 25 km/h). With an Oregon 400 with old firmware (4.20), values are slightly different: Roadspeed Distance Time Speed Simulationspeed 7 99,9 00:45:20 132,22 129 6 99,7 00:51:51 115,37 113 5 100 00:56 105,63 103 4 99,5 01:07 89,10 87 3 100 01:32 65,22 64 2 99,9 02:03 48,73 48 1 99,5 03:06 32,10 32 0 100 10:16 9,74 9 The main difference is in faster speed for higher road_speed types, but lower simulation speed. This means that Garmin uses different speeds for calculating the time to destination between different device types! I hope this information helps the creators of maps, and helps to clarify questions on why this route was taken instead of that...

1 0

Commit: r3313: Add address boundary rules for South Africa.
by svn commit 01 Jul '14

01 Jul '14

Version mkgmap-r3313 was committed by steve on Tue, 01 Jul 2014 Add address boundary rules for South Africa. -Ben Konrath

1 0

Commit: r3312: Add --unicode option as abbreviation for --code-page=65001.
by svn commit 01 Jul '14

01 Jul '14

Version mkgmap-r3312 was committed by steve on Tue, 01 Jul 2014 Add --unicode option as abbreviation for --code-page=65001.

1 0