- mkgmap-dev - The mkgmap lists

updated typ-file mkgmap default style
by Joris Bo 24 Jan '19

24 Jan '19

Hello Here is a new version of the typ * Attached also the translation table so far. If somebody likes to add different language, please sent me one Changes * Added white line to roundabout (turned out that not all highway-types were adding overlays so transparent was visually not working) * Fixed empty translations for Korean and Basque, Thx Nick * Modified German Translations: Thx to Ralf ! * Added Italian translations Thx to Lorenzo ! * Added Portuguese translations thx to Wesley ! * Added Polish translations Thx to Artur ! * Find out that it was cGpsMapper manual that states there is a maximum of 4 translations but I tested this one with 7 and so far it seems not to be a problem. * I’m still struggling with the codepage / polish special characters / utf8 / ascii / 1252. In this version the txt is ascii, making some Polish special characters to be (nicely but not wanted) replaced by their ‘normal’ equivalents. When using UTF-8 in combination with special chars , the txt looks fine but mkgmp.jar will fail creating the typ. I probably do something wrong. I keep testing together with Artur to see what can be done. * There are more comments from Michael which I not have studied yet More comments are welcome. Kind regards Joris Van: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> Namens Lorenzo Mastrogiacomi Verzonden: maandag 21 januari 2019 00:19 Aan: mkgmap-dev(a)lists.mkgmap.org.uk Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file Attached my italian translation too. Lorenzo Il giorno dom, 20/01/2019 alle 12.17 -0200, Wesley Martins ha scritto: Hello Joris, Attached is the portuguese translation. Added column for portuguese and sortorder column is intact. ;D Regards Wesley On Sat, Jan 19, 2019 at 9:08 AM Joris Bo <jorisbo(a)hotmail.com<mailto:jorisbo@hotmail.com>> wrote: Super Ralf, Danke! Habe es schon verarbeitet Gr Joris -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk>> Namens Ralf Kleineisel Verzonden: zaterdag 19 januari 2019 11:57 Aan: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk>> Onderwerp: Re: [mkgmap-dev] default style improvements / updated typ-file Hi, On 1/19/19 11:38 AM, Joris Bo wrote: > That’s very kind, thank you. > > Attached an excel with the exported translations up to r4262 > > Just add a column for any new language I just corrected a few issues in the german column. _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

5 4

Re: [mkgmap-dev] default style improvements / upated typ-file
by Joris Bo 21 Jan '19

21 Jan '19

Hello, I modified the type-file up to Ticker's changes in build r4262. Latest changes can also be found on https://github.com/Jorisbo/Mkgmap-Mapnik-Style-Garmin It already reflects some new mapnik colors which will be first visible on www.openstreetmap.org in a couple of days The deltas I found after comparing Tickers changes are ======================================================= Added rendering for polygons 1) place=suburb [0x02 resolution 19] 2) # mop up any remaining water areas waterway=* & waterway!=no & area!=no {add name='${waterway|subst:"_=> "}'} [0x3b resolution 22] 3) natural=water & area_size() < 100000 [0x41 resolution 22] # Small Lake 4) dock=drydock [0x4c resolution 22] # might also have natural=water natural=water & water=lock [0x4c resolution 22 default_name 'Lock'] Added rendering for lines 5) highway=raceway | highway=gallop {add name='${highway}'} [0x30 resolution 23] Some changes to be considered? ======================================================= Different kinds of public transport are mapped to the same symbol. For now I choose the arbritary bus_station as the most common Line 106: amenity=bus_station [0x2f08 resolution 23] Line 126: amenity=ferry_terminal [0x2f08 resolution 22] Line 206: railway=station [0x2f08 resolution 22] Line 207: (public_transport=platform & rail=yes) | railway=halt [0x2f08 resolution 23] Different kinds of roads mapped to the same linetype, especially cycleways deserve there on linetype I think Line 190: highway=bridleway [0x07 road_class=0 road_speed=0 resolution 23] Line 197: highway=service & service=parking_aisle [0x07 road_class=0 road_speed=1 resolution 24] Line 198: highway=service & (service=alley | service=driveway) [0x07 road_class=0 road_speed=0 resolution 23] Line 199: highway=service [0x07 road_class=0 road_speed=2 resolution 22] Line 201: highway=cycleway [0x07 road_class=0 road_speed=1 resolution 23] Line 214: highway=turning_loop | highway=turning_circle | highway=layby | highway=escape | highway=emergency_bay [0x07 road_class=0 road_speed=0 resolution 24] Add different (non-routable) linetype for highway = construction instead of converting them to a routable footway (0x16) Any comments, please let me know, Kind regards Joris -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: vrijdag 11 januari 2019 10:30 Aan: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] default style improvements Hi Gerd Here is summary of the changes: A few minor layout tidy-ups Add GBR section to inc/access_country Do aeroway=runway/taxiway/taxilane as lines unless marked as area=yes and show these lines even when also a highway Ignore more highways when abandoned/disused/demolished Ignore more highway tags that are not suitable for routing Convert highway=steps/corridor/stepping_stones/elevator/escalator/platform to footway with bicycle=no and remove later test for steps Convert highway=crossing/virtual to path Don't convert footway to cycleway, but more rules to convert path to footway/cycleway/bridleway Add footway around man_made=pier even if area=yes Fix common bad tagging for highway= by converting to the presumed values Put routable path around highway=pedestrian closed areas; squares/plazas often don't have other routing joining all entry/exit ways. Similarly for footway. Then continue to allow any polygon processing Handle some rarer highway types by converting to more generic type Show any other water lines Removed all the {set cityxx/tmp:city}, & cityxx/tmp:city!=yes, continue with_actions bits from place=city/town... Group the rules amenity=restaurant/fast_food, cuisine= to clarify, simplify and show better how it relates Garmin "Food & Drink" search and add some more cuisines. One effect of this is that amenity=fast_food,cuisine=pizza/grill moves to the "Fast Food" category. The other effect is that an element that is both a Restaurant and a Lodging now shows as Lodging rather than Restaurant For leisure=* where sport might be involved, show the sport if no name available Show canal/lock as 0x6505 (Water Features>Canal) Show aeroway=runway/taxiway/taxilane as polygon only if marked as area=yes Increase resolution that amenity=cafe/fast_food/restaurant polygons show at Show place=suburb Alternative rule to show highway=pedestrian as square/plaza unless explicit area=no. highway=footway show as square/plaza if explicit area=yes Don't assume any other closed highway is parking area, just services/rest_area Show more historic=* Show drydock, canal & lock differently from standard natural=water, and use a different code for small lakes Show any other water area Show all man_made=* unless explicit area=no Regards Ticker On Fri, 2019-01-11 at 06:13 +0000, Gerd Petermann wrote: > Hi Ticker, > > please, can you summarize the changes implemented with this patch? > Need this for the svn commit message. > > Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

3 3

Re: [mkgmap-dev] default style improvements
by EthnicFood IsGreat 21 Jan '19

21 Jan '19

> Date: Mon, 21 Jan 2019 07:09:30 +0000 > From: Ticker Berkin <rwb-mkgmap(a)jagit.co.uk> > To: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Subject: Re: [mkgmap-dev] default style improvements > > Hi > > Here is a patch to change some TYPE element numbers in > default/polygons: > > 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" > > Regards > Ticker Ticker, as a frequent user of Mkgmap, I want to commend you for all the thought you've put into trying to make the output better. Mark

1 0

Re: [mkgmap-dev] default style improvements / updated typ-file
by Joris Bo 21 Jan '19

21 Jan '19

Hello My previous typ had 2 bugs (No draworder for new lake 0x41) making lakes invisible and missing wilderniss hut Both are fixed in attached typ. There were also a couple of polygons and lines having a night color bitmap, for now I removed them and introduce them again if complete. There is help coming up from Michael to fill that gap. Feel free to send more findings Kind regards Joris -----Oorspronkelijk bericht----- Van: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> Namens Ticker Berkin Verzonden: maandag 14 januari 2019 12:24 Aan: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> Onderwerp: Re: [mkgmap-dev] default style improvements / upated typ-file Hi I agree the name change from mkgmap.txt to something else (no problem with mapnik.txt) is needed. I haven't been through this TYP in detail yet. Some of my previous comments still stands: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029103.html I'd like another, much, much simpler, TYP file for the default style also to be available. It would avoid re-defining representation that the typical Garmin device shows. In my next set of changes I'm planning to change quite a few TYPE numbers, many as suggested in this thread on 13-Nov-2018: http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029146.html but there will be some differences from this post. Some of these cover Joris's "changes to be considered". Some of the other suggestions I feel are too much for the default style but I will consider them. It will be a few days before I'm able to do anything in this area. We need some pointers in the documentation to the collection of TYP -files. Please can we have these TYP-files in "trunk". I think the "default -typ" branch it is a hindrance. Regards Ticker On Mon, 2019-01-14 at 06:51 +0000, Gerd Petermann wrote: > Hi Joris, > > I've replaced the default style in the typ branch by that from trunk > and added your typ with that. I hope that was right? > http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4263 > > I think about a move/rename of styles\default\typ.txt to typ > -files\mapnik.txt using the command svn move styles\default\typ.txt > typ-files\mapnik.txt > > Would that be okay for you? > > Reg. the other changes I hope that Ticker has an answer. > > Gerd > > ________________________________________ > Von: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> im Auftrag > von Joris Bo <jorisbo(a)hotmail.com> > Gesendet: Sonntag, 13. Januar 2019 12:11 > An: Development list for mkgmap > Betreff: Re: [mkgmap-dev] default style improvements / upated typ > -file > > Hello, > > I modified the type-file up to Ticker's changes in build r4262. > Latest changes can also be found on > https://github.com/Jorisbo/Mkgmap-Mapnik-Style-Garmin > It already reflects some new mapnik colors which will be first visible > on www.openstreetmap.org in a couple of days > > > The deltas I found after comparing Tickers changes are > ======================================================= > Added rendering for polygons > 1) > place=suburb [0x02 resolution 19] > 2) > # mop up any remaining water areas > waterway=* & waterway!=no & area!=no {add > name='${waterway|subst:"_=> "}'} [0x3b resolution 22] > 3) > natural=water & area_size() < 100000 [0x41 resolution 22] # > Small Lake > 4) > dock=drydock [0x4c resolution 22] # might also have > natural=water > natural=water & water=lock [0x4c resolution 22 default_name > 'Lock'] > > Added rendering for lines > 5) > highway=raceway | highway=gallop {add name='${highway}'} > [0x30 resolution 23] > > > Some changes to be considered? > ======================================================= > Different kinds of public transport are mapped to the same symbol. > For now I choose the arbritary bus_station as the most common > Line 106: amenity=bus_station [0x2f08 resolution 23] > Line 126: amenity=ferry_terminal [0x2f08 resolution 22] > Line 206: railway=station [0x2f08 resolution 22] > Line 207: (public_transport=platform & rail=yes) | > railway=halt [0x2f08 resolution 23] > > Different kinds of roads mapped to the same linetype, especially > cycleways deserve there on linetype I think > Line 190: highway=bridleway [0x07 road_class=0 road_speed=0 > resolution 23] > Line 197: highway=service & service=parking_aisle [0x07 > road_class=0 road_speed=1 resolution 24] > Line 198: highway=service & (service=alley | > service=driveway) [0x07 road_class=0 road_speed=0 resolution 23] > Line 199: highway=service [0x07 road_class=0 road_speed=2 > resolution 22] > Line 201: highway=cycleway [0x07 road_class=0 road_speed=1 > resolution 23] > Line 214: highway=turning_loop | highway=turning_circle | > highway=layby | highway=escape | highway=emergency_bay [0x07 > road_class=0 road_speed=0 resolution 24] > > Add different (non-routable) linetype for highway = construction > instead of converting them to a routable footway (0x16) > > Any comments, please let me know, > Kind regards Joris > > > > -----Oorspronkelijk bericht----- > Van: mkgmap-dev <mkgmap-dev-bounces(a)lists.mkgmap.org.uk> Namens Ticker > Berkin > Verzonden: vrijdag 11 januari 2019 10:30 > Aan: Development list for mkgmap <mkgmap-dev(a)lists.mkgmap.org.uk> > Onderwerp: Re: [mkgmap-dev] default style improvements > > Hi Gerd > > Here is summary of the changes: > > A few minor layout tidy-ups > > Add GBR section to inc/access_country > > Do aeroway=runway/taxiway/taxilane as lines unless marked as area=yes > and show these lines even when also a highway > > Ignore more highways when abandoned/disused/demolished > > Ignore more highway tags that are not suitable for routing > > Convert > highway=steps/corridor/stepping_stones/elevator/escalator/platform to > footway with bicycle=no and remove later test for steps > > Convert highway=crossing/virtual to path > > Don't convert footway to cycleway, but more rules to convert path to > footway/cycleway/bridleway > > Add footway around man_made=pier even if area=yes > > Fix common bad tagging for highway= by converting to the presumed > values > > Put routable path around highway=pedestrian closed areas; > squares/plazas often don't have other routing joining all entry/exit > ways. Similarly for footway. Then continue to allow any polygon > processing > > Handle some rarer highway types by converting to more generic type > > Show any other water lines > > Removed all the {set cityxx/tmp:city}, & cityxx/tmp:city!=yes, > continue with_actions bits from place=city/town... > > Group the rules amenity=restaurant/fast_food, cuisine= to clarify, > simplify and show better how it relates Garmin "Food & Drink" search > and add some more cuisines. One effect of this is that > amenity=fast_food,cuisine=pizza/grill moves to the "Fast Food" > category. The other effect is that an element that is both a > Restaurant and a Lodging now shows as Lodging rather than Restaurant > > For leisure=* where sport might be involved, show the sport if no name > available > > Show canal/lock as 0x6505 (Water Features>Canal) > > Show aeroway=runway/taxiway/taxilane as polygon only if marked as > area=yes > > Increase resolution that amenity=cafe/fast_food/restaurant polygons > show at > > Show place=suburb > > Alternative rule to show highway=pedestrian as square/plaza unless > explicit area=no. highway=footway show as square/plaza if explicit > area=yes > > Don't assume any other closed highway is parking area, just > services/rest_area > > Show more historic=* > > Show drydock, canal & lock differently from standard natural=water, > and use a different code for small lakes > > Show any other water area > > Show all man_made=* unless explicit area=no > > Regards > Ticker > > On Fri, 2019-01-11 at 06:13 +0000, Gerd Petermann wrote: > > Hi Ticker, > > > > please, can you summarize the changes implemented with this patch? > > Need this for the svn commit message. > > > > Gerd > > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev > _______________________________________________ > mkgmap-dev mailing list > mkgmap-dev(a)lists.mkgmap.org.uk > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev(a)lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

6 12

Hide tunnels and other features in basecamp 3D mode
by Joris Bo 14 Jan '19

14 Jan '19

Hello I added the DEM / Hillshading to my maps. If I set basecamp to show in 3d you get very nice results ! Thx for all the work done there. Is there an option to tag certain elements to be hidden in (basecamp) 3D modus? For example the Mont Blanc Tunnel goes straight up to the to the top 😊 [cid:image001.png@01D4AB26.4D264E50]

2 1

Street names abreviated on screen but complete in speech?
by muralito＠montevideo.com.uy 14 Jan '19

14 Jan '19

Hello. It's possible to have mkgmap compile the street name abreviated for text labels and address of POI (and other on-screen uses), and keeps the name as it is in OSM so the garmin device speechs the complete sound? It could help a lot with long names in spanish language, eg "Av."->"Avenida", and several other words. Regards, M.

2 1

Commit r4262: improve default style (defaultStyleTidy3e.patch by Ticker Berkin with small modifications)
by svn commit 11 Jan '19

11 Jan '19

Version mkgmap-r4262 was committed by gerd on Fri, 11 Jan 2019 improve default style (defaultStyleTidy3e.patch by Ticker Berkin with small modifications) A few minor layout tidy-ups Add GBR section to inc/access_country Do aeroway=runway/taxiway/taxilane as lines unless marked as area=yes and show these lines even when also a highway Ignore more highways when abandoned/disused/demolished Ignore more highway tags that are not suitable for routing Convert highway=steps/corridor/stepping_stones/elevator/escalator/platform to footway with bicycle=no and remove later test for steps Convert highway=crossing/virtual to path Don't convert footway to cycleway, but more rules to convert path to footway/cycleway/bridleway Add footway around man_made=pier even if area=yes Fix common bad tagging for highway= by converting to the presumed values Put routable path around highway=pedestrian closed areas; squares/plazas often don't have other routing joining all entry/exit ways. Similarly for footway. Then continue to allow any polygon processing Handle some rarer highway types by converting to more generic type Show any other water lines Removed all the {set cityxx/tmp:city}, & cityxx/tmp:city!=yes, continue with_actions bits from place=city/town... Group the rules amenity=restaurant/fast_food, cuisine= to clarify, simplify and show better how it relates Garmin "Food & Drink" search and add some more cuisines. One effect of this is that amenity=fast_food,cuisine=pizza/grill moves to the "Fast Food" category. The other effect is that an element that is both a Restaurant and a Lodging now shows as Lodging rather than Restaurant For leisure=* where sport might be involved, show the sport if no name available Show canal/lock as 0x6505 (Water Features>Canal) Show aeroway=runway/taxiway/taxilane as polygon only if marked as area=yes Increase resolution that amenity=cafe/fast_food/restaurant polygons show at Show place=suburb Alternative rule to show highway=pedestrian as square/plaza unless explicit area=no. highway=footway show as square/plaza if explicit area=yes Don't assume any other closed highway is parking area, just services/rest_area Show more historic=* Show drydock, canal & lock differently from standard natural=water, and use a different code for small lakes Show any other water area Show all man_made=* unless explicit area=no http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4262

1 0

Commit r4261: don't treat amenity=shelter + shelter_type=public_transport like other shelters
by svn commit 07 Jan '19

07 Jan '19

Version mkgmap-r4261 was committed by gerd on Mon, 07 Jan 2019 don't treat amenity=shelter + shelter_type=public_transport like other shelters http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4261

1 0

Not-equal compare bug?
by Harri Suomalainen 05 Jan '19

05 Jan '19

Using mkgmap-r4260 I tried several variations to make a rule match when some tag does not exist: Line: ( highway!=* | oneway!=*) { deletealltags } Error in style: Error: (lines:12): Invalid rule expression: $highway!=*| $oneway!=* Similar error is given when comparing expression with this line: oneway!=* { deletealltags } Tt seems != works fine but only if there is an equal comparision first like in this line that gives no error: highway=* & oneway !=* { deletealltags } Do I missunderstand something or is this a bug? I think I tried some other use case while back and I got similar errors when it started with != comparision first. This may not be a very new issue. Chears, Harri

5 8

splitter, mapid
by brad 03 Jan '19

03 Jan '19

One thing I think I missed, is that each tile on a garmin device needs a unique mapid. A different family-id and mapname for each gmap is not sufficient. Does this sound correct? I'd been downloading US states from Geofabrik, creating maps with unique family-id, mapname, every name & id that seemed important, (with mkgmap) but when I put them on the Garmin they all wouldn't show up. Only when I went back to the splitter step & used a different mapid did they all show up. Sometimes I'm not too good at reading directions, did I overlook this someplace? Brad

5 13