- mkgmap-dev - The mkgmap lists

Commit r4143: merge from angles branch
by svn commit 31 Mar '18

31 Mar '18

Version mkgmap-r4143 was committed by gerd on Sat, 31 Mar 2018 merge from angles branch Improvements to WrongAngleFixer. - Remove spikes from roads where rounding to Garmin units creates them. - Try harder to avoid overlapping road segments where in OSM they build an angle but the rounding places them on top of each other. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4143

1 0

Bug in Road Merging - actually doubling roads.
by Felix Hartmann 30 Mar '18

30 Mar '18

I just noticed that mkgmap sometimes creates a lot more routable roads for a certain stretch than actually defined in the style-file. https://www.openstreetmap.org/way/130665733 should be only once as a routable line in my map, however it ends up 6 times! Once is correct, but 5 iterations are actually the way from the south (3 times) and the way from the East (2 times). Now each of these ways should be created that often, however it should not overlay into this short stretch of way. While doubling up ways can be beneficial for routing, having a way more than 5 times on top of each other let's Garmin devices crash on routing over them. Also it leads to detours - as it will not always route straight from the Way from South to the Way going to the West, but follow along after the intersection for 4.3m until hitting up north, then reversing and finally going to the way in the West. I've uploaded the tile here: https://openmtbmap.org/gmapsupp_copied.img I'm pretty sure that with other style-files - the way will also be copied past the intersection and end up too often in the map for that 4.3m stretch... I kinda guess it is related to it being so short - that place has some remarkable micro-mapping detail. Or is this really expected? If needed I can try to create a reduced style to only create that problem - but I think the bug should be obvious. -- Felix Hartman - Openmtbmap.org & VeloMap.org Schusterbergweg 32/8 6020 Innsbruck Austria - Österreich

6 81

angles branch
by Gerd Petermann 30 Mar '18

30 Mar '18

Hi all, I did not hear about any problems so I'd like to merge the branch to trunk tomorrow. I think it improves the map in a few cases, but may need a bit more CPU time. Please let me know if you think I should better wait. Gerd

2 1

Error in my style with Version mkgmap-r4136
by lasemax 29 Mar '18

29 Mar '18

Who can help me. Since Version mkgmap-r4136 i get a error with my style. Error in style: Error: (points:179): Invalid rule expression: $mkgmap:admin_level2!=DEU & $name:en=$name:de The error is in Line 179 and this is the code before and after error: 176: # Naming 177: mkgmap:admin_level2=DEU & name:de=* { set name='${name:de}' } 178: mkgmap:admin_level2!=DEU & name:en=* { set name='${name:en} (${name:de})' } 179: mkgmap:admin_level2!=DEU & name:en=$name:de { set name='${name:en}' } 180: mkgmap:admin_level2!=DEU & name:de=* & name:en!=* & name!=$name:de { set name='${name} ${name:de})' } With my last Version mkgmap-r4125 is all ok and this code works. -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

3 4

Garmin directing to connected crossing roads
by Harri Suomalainen 27 Mar '18

27 Mar '18

I've noticed locations where my Garmin gives directions to use crossing street (like small service roads) when routing through a single route. A good example is unclassified "Juurakkotie" at https://www.openstreetmap.org/#map=18/60.29121/24.99298 (I'm using current data from Geofabric extracts and the road has not changed recenty and it is verified to be as straight as josm makes it) When Garmin routes through it from west to east, it tells multiple times to go the the service, to the service, ...about 4 times or so (and I think only twice when routing from east to west). Map line is straight through Juurakkotie (ie no routing through yards). (Not sure what word garmin uses exactly in different languages to the road type it suggests taking to, but it varies from device to another anyway) My style has following lines: # To avoid routing through service roads highway=service { set access=destination } # Low road class definition for service highway=service [0x07 road_class=0 road_speed=2 resolution 24] # Higher road class for unclassified highway=unclassified [0x08 road_class=2 road_speed=3 resolution 22] # and in finalize-section access=destination { set mkgmap:throughroute=no; set access=yes } I see no reason why it should consider the connecting routes something one should go to and instruct so. (My style also should make service type road avoided anyway for routing if possible). I've occationally noticed this kind of behaviour with my old Nuvi 755 also (currently using Drivesmart 61). (Getting multiple turn to..turn to..turn to.. instractions repeated is quite annoying when it happens) I wonder if this is some kind of "feature" of Garmin or some kind of bug in stored road geometry or if this is something to deal with my style. I compile map with following options --max-jobs=8 --link-pois-to-ways --add-pois-to-areas --reduce-point-density=3 --merge-lines --reduce-point-density-polygon=1 --drive-on=right --country-name=FINLAND --country-abbr=FIN --area-name=Finland --latin1 --code-page=1252 --generate-sea=multipolygon,extend-sea-sectors,close-gaps=2000,floodblocker" --location-autofill=is_in --x-housenumbers --housenumbers --process-destination --process-exits This kind of behaviour has existed for years and currently I'm using latest mkgmap-dev. I run into it only occationally and when I do it is repeatable in the locations. Chears, Harri

2 4

Example of logging Echotags to file
by Joris Bo 27 Mar '18

27 Mar '18

Hello Does somebody have an example of logging the output of echotags to file rather then the command window. I tried a lot already like: java > c:\temp\log.txt The logfile is created but the log only shows basic info and not the Echotags info Thx in advance Joris

4 6

Commit r4141: fix possible "internal error: via way doesn't contain expected points"
by svn commit 26 Mar '18

26 Mar '18

Version mkgmap-r4141 was committed by gerd on Mon, 26 Mar 2018 fix possible "internal error: via way doesn't contain expected points" This happened when a RestrictionRelation was detected as invalid because a via way is not routable. Now such a relation is marked as invalid and therefore no integrety check is done. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4141

1 0

Current state of --dem-reuse option
by Carlos Dávila 26 Mar '18

26 Mar '18

Hi Gerd Have you done any further development of option --x-dem-reuse mentioned at http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q1/027951.html ?

2 1

Re: [mkgmap-dev] Error in my style with Version mkgmap-r4136
by Gerd Petermann 23 Mar '18

23 Mar '18

Hi lasemax, this seems to be an error in mkgmap. It doesn't print this message when you change the line 179 to name:en=$name:de & mkgmap:admin_level2!=DEU { set name='${name:en}' } I think it should handle both rules in the same way, but it doesn't. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag von lasemax <lasemax(a)byom.de> Gesendet: Donnerstag, 22. März 2018 09:32:36 An: mkgmap-dev(a)lists.mkgmap.org.uk Betreff: [mkgmap-dev] Error in my style with Version mkgmap-r4136 Who can help me. Since Version mkgmap-r4136 i get a error with my style. Error in style: Error: (points:179): Invalid rule expression: $mkgmap:admin_level2!=DEU & $name:en=$name:de The error is in Line 179 and this is the code before and after error: 176: # Naming 177: mkgmap:admin_level2=DEU & name:de=* { set name='${name:de}' } 178: mkgmap:admin_level2!=DEU & name:en=* { set name='${name:en} (${name:de})' } 179: mkgmap:admin_level2!=DEU & name:en=$name:de { set name='${name:en}' } 180: mkgmap:admin_level2!=DEU & name:de=* & name:en!=* & name!=$name:de { set name='${name} ${name:de})' } With my last Version mkgmap-r4125 is all ok and this code works. -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

2 1

TYP filename too long
by Ben Konrath 22 Mar '18

22 Mar '18

Hi, A user recently reported that my maps weren't able to be installed with BaseCamp (error: "The data was not successfully sent"). It turns out that name of the TYP file was too long; the MapSetToolkit program reported an error on the OpenMapChest registry entries: openmapchest.typ - 12+3 characters. After renaming the TYP file to omc.typ in a new build, transferring worked correctly. It would be nice if mkgmap truncated TYP file names that are too long. I think the maximum length is the old DOS standard of 8+3 characters. I'm using a relatively old version of mkgmap (3909) so this might already be fixed. But in case it's not, I thought I would report it. Thanks for all your hard work on mkgmap! Regards, Ben

2 1