May 2020 - mkgmap-dev - The mkgmap lists

Commit r4499: fix is_in() style function. isPointInShape_v3.patch by Ticker Berkin, modified
by svn commit 23 May '20

23 May '20

Version mkgmap-r4499 was committed by gerd on Sat, 23 May 2020 fix is_in() style function. isPointInShape_v3.patch by Ticker Berkin, modified http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4499

1 0

PolishMapDataSource.checkType()) invalid type 0x5400 for POLYGON
by Vadim 23 May '20

23 May '20

Good day or night! :) I am surprised, but the MkGmap does not understand this definition of TYPE like this: [POLYGON] Type=0x05400 but works fine with Marine types: [POLYGON] Type=0x10F01 Yes, I know that I can divide this long record into three parts: [POLYGON] Type=0x54 Subtype=0x00 Marine=N But it is a little inconvenient. :( When working with a TYPE file: [_polygon] Type=0x05400 such an error does NOT occur! By the way, cGPSmapper works well with both TYPE recording options. -- Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html

3 9

Commit r4498: Now really allow to use e.g. type 0x0e00 instead of 0x0e for polyline in polish input (*.mp)
by svn commit 23 May '20

23 May '20

Version mkgmap-r4498 was committed by gerd on Sat, 23 May 2020 Now really allow to use e.g. type 0x0e00 instead of 0x0e for polyline in polish input (*.mp) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4498

1 0

Extra leading character after assiging highway shield
by Joris Bo 23 May '20

23 May '20

Hi, For a long time I have seen a leading (space like?) character in front of $Ref which is not there in the osm source. Today I have been chasing the thing trying to finally solve my style-bug, but now I get stuck thinking it looks like the highwayshield assignment is adding it. I studied the manuals around the addlabel command and the mkgmap:label:1 fields but I'm not sure if it is a known side effect I think I can easily fix it after the assignment. I switched to the default style and find the same behavior. [cid:image002.jpg@01D6307A.E3391280] In the finalize section of lines the highway shields are calculated The yellow stuf is my debug comment, the green stuf is the default style, the blue stuf is the echotags result #--------- DEBUG highway = * {set jba1 = '$(mkgmap:label:1)' ; set jba2 = '$(mkgmap:label:2)' ; set jba3 = '$(ref)' ; set jba4 = '$(name)' } #------------------ Jba1=empty = mkgmap:label:1 Jba2=empty = mkgmap:label:2 jba3=N184 = $ref jba3=Luitenant Lippenslaan = $name # Display highway shield for mayor roads if they have a ref and make them searchable by their name (highway=motorway | highway=trunk) & ref=* {name '${ref|highway-symbol:hbox}'; addlabel '${name}'} highway=primary & ref=* {name '${ref|highway-symbol:box}' ; addlabel '${name}'} (highway=secondary | highway=tertiary) & ref=* {name '${ref|highway-symbol:oval}'; addlabel '${name}'} #--------- DEBUG highway = * {set jbb1 = '$(mkgmap:label:1)' ; set jbb2 = '$(mkgmap:label:2)' ; set jbb3 = '$(ref)' ; set jbb4 = '$(name)' } #------------------ I pasted a picture because it visualize the hidden character suddenly appear in front of mkgmap:label:1 [cid:image006.png@01D6307A.E3391280] name=* {name '${name}'} highway=* & ref=* & highway!=motorway & highway!=trunk & highway!=primary & highway!=secondary & highway!=tertiary {addlabel '${ref}'} highway = * & osmid() = 272407046 {echotags 'looking for prefix'}

2 2

Commit r4497: Allow to use e.g. type 0x0e00 instead of 0x0e for polyline in polish input (*.mp)
by svn commit 23 May '20

23 May '20

Version mkgmap-r4497 was committed by gerd on Sat, 23 May 2020 Allow to use e.g. type 0x0e00 instead of 0x0e for polyline in polish input (*.mp) Forgot that in the previous change. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4497

1 0

Commit r4496: Allow to use e.g. type 0x5400 instead of 0x54 for polygons in polish input (*.mp)
by svn commit 22 May '20

22 May '20

Version mkgmap-r4496 was committed by gerd on Fri, 22 May 2020 Allow to use e.g. type 0x5400 instead of 0x54 for polygons in polish input (*.mp) We did that already for special type 0x4b00. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4496

1 0

Commit r4495: isin.patch: allow to use '*' as a value in the is_in style function
by svn commit 21 May '20

21 May '20

Version mkgmap-r4495 was committed by gerd on Thu, 21 May 2020 isin.patch: allow to use '*' as a value in the is_in style function http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4495

1 0

Routing Issue with Garmin Edge 830
by Stephan Warzecha 21 May '20

21 May '20

Hello, I am sorry but I have a question better called problem. my new Garmin Edge 830 ist crashing down, sometimes during navigation. I askes this question here because garmin told me that the map must be the problem. I am working with mkgmap since many years and I built "my own" map form my devices. At my old Garmin Vista Hcx the maps working without problem, also on MapSource and Basecamp. I checked the line file more than hunderet times again and again. Yesterday I produced the map only with "route" option and default style which is comming with mkgmap. The map that was built has the same problem. I used differnt typ-files to crosscheck if the problem comes from typ-file but no success. I also tried older versions of mkgmap, the same no success. I will try to explain what the problem is: Mostly ways, taged with highway=track and tracktype=grade4, are affected. They are part oft he map, and there is no problem while routing on MapSource, BaseCamp, Vista usw., but if I create the same route on the garmin edge 830, the route is built without any problems, but the violet line (route) has interruptions. Whenever I had such a part oft he way in a route the device is crashing down while driving the route. This ist the rule wich is used to create the line for tracktype=grade 4 highway=track & tracktype=grade4 {setaccess 'yes'; set mkgmap:unpaved=yes} [0x11 road_class=0 road_speed=1 resolution 23] I also tried it with different way types (0x01 - 0x12, 0x0e 0x0f etc) also I tried differnt spped and road classes. Next step was to try with all Tracks as the same line, like this... highway=track & tracktype=* {setaccess 'yes'; set mkgmap:unpaved=yes} [0x11 road_class=0 road_speed=1 resolution 23 Routing on all ways was possible, but the garmin routing line is broken at the ways, which was tracktype 4 before. Now I have no idea what is happening, the device can´t know that the line was a tracktype4, all tracks hast he same name and options. I will add some pictures to explan what im trying to explain, with my terrible english ;0)) An example route with MapSource: [cid:image005.png@01D62D1F.128DFE60] The same on Garmin Device Edge 830: [cid:image004.png@01D62D1F.D9B56C30] Same Route with my layout in Mapsource: [cid:image008.png@01D62D22.39C3CE80] And at the Edge 830: [cid:image007.png@01D62D20.3DFCCF30] Now the funny things: *Garmin Map is working, *If I delete a affeccted way in Openstreetmap and map it new, also only with 2 Tags like this: [cid:image009.png@01D62D21.72342900] ...the mistake is gone. I din´t "correct" the shown example yet. But I got this Problem all over whole germany, there must be an error. Maybe this is a personal probelm or mistake, but maybe that others has the same problems. If there is any information what Iam doing wrong or something else, please let me kown. There are so many hours Iam searching for a solution. The maps are built with extract from geofabrik, germany file splittet with splitter. I used the newest stable versions. Also the is more information you need, please lt me know. Viele Grüße / Best Regards Stephan Warzecha Logistic and Workplace Services | Logistic Support| Problem Manager Logistic Support T +49 (0) 6026 9762-6120 | F +49 (0) 6026 9762-6504 | stephan.warzecha(a)dpd.de<mailto:stephan.warzecha@dpd.de> DPD Deutschland GmbH Stockstädter Straße 10, 63762 Großostheim, Deutschland | dpd.de<http://www.dpd.de/> Besuchen Sie uns auf Facebook<http://www.facebook.com/dpdindeutschland>, Instagram <https://www.instagram.com/dpd.de/> und Twitter<http://twitter.com/dpd_de>. [cid:image002.gif@01D14D54.6725B0D0] Sitz der Gesellschaft: Aschaffenburg | Registergericht: Aschaffenburg HRB 8887 Geschäftsführung: Eric Malitzke (CEO), Dirk Müller, Thomas Ohnhaus, Andreas Reß [signature_304297842]

4 3

IS_IN tag - value as regular expression or wildcard
by Joris Bo 21 May '20

21 May '20

Hello I try to use the IS_IN function with regular expression or wildcard, but I get style-errors or false. When testing against the exact value it works perfectly. Is there a method for testing against building = * instead of building = yes ? On the same object I have the following results #leisure = pitch & is_in(building, *, all_in_or_on) = true {set debug0 = true} Style conversion error leisure = pitch & is_in(building, '.*', all_in_or_on) = true {set debug1 = true} false leisure = pitch & is_in(building, '\*', all_in_or_on) = true {set debug2 = true} false leisure = pitch & is_in(building, '*', all_in_or_on) = true {set debug3 = true} false leisure = pitch & is_in(building, '(.*)', all_in_or_on) = true {set debug4 = true} false leisure = pitch & is_in(building, '(\*)', all_in_or_on) = true {set debug5 = true} false leisure = pitch & is_in(building, '(*)', all_in_or_on) = true {set debug6 = true} false leisure = pitch & is_in(building, yes, all_in_or_on) = true {set debug7 = true} true mkgmap:cache_is_in_POLYLINE_building_(*)_all_in_or_on=false mkgmap:cache_is_in_POLYLINE_building_(.*)_all_in_or_on=false mkgmap:cache_is_in_POLYLINE_building_(\*)_all_in_or_on=false mkgmap:cache_is_in_POLYLINE_building_*_all_in_or_on=false mkgmap:cache_is_in_POLYLINE_building_.*_all_in_or_on=false mkgmap:cache_is_in_POLYLINE_building_\*_all_in_or_on=false mkgmap:cache_is_in_POLYLINE_building_yes_all_in_or_on=true Many thx in advance, Kind Regards Joris jorisbo(a)hotmail.com<mailto:jorisbo@hotmail.com>

3 5

Commit r4494: fix some sonarlint issues, simplify code (no change in output expected)
by svn commit 21 May '20

21 May '20

Version mkgmap-r4494 was committed by gerd on Thu, 21 May 2020 fix some sonarlint issues, simplify code (no change in output expected) http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4494

1 0