<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Jorus</p>
<p>Great job!</p>
<p>Just to be a pain, all (I think) your elements have a one
character text string for Basque and Korean:<br>
</p>
<p>ie</p>
<p>String5=0x09, <br>
String6=0x24, <br>
</p>
<p>Perhaps you had big plans for translating labels into Basque or
Korean ;)</p>
<p>r</p>
<p>Nick<br>
</p>
<div class="moz-cite-prefix">On 16/01/2019 18:56, Joris Bo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:AM6PR04MB498196EF92B3CB88B1AE8F76AF820@AM6PR04MB4981.eurprd04.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML - vooraf opgemaakt Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;}
span.HTML-voorafopgemaaktChar
{mso-style-name:"HTML - vooraf opgemaakt Char";
mso-style-priority:99;
mso-style-link:"HTML - vooraf opgemaakt";
font-family:"Consolas",serif;
color:black;}
span.E-mailStijl21
{mso-style-type:personal-reply;
font-family:"Arial",sans-serif;
font-weight:normal;
font-style:normal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Hello<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US">Thx
Nick<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">Attached both issues changed<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">@Ticker<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">It was not easy to address a good polygon color
for [0x1e] used for ‘historic’<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">historic=* & historic!=no &
historic!=yes & boundary!=* {add
name='${historic|subst:"_=> "}'} [0x1e resolution 21]<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">“Historic” can be used on almost anything from
park to building to museum and ruins.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">After a compare on ‘Luxembourg’ I decided that
‘building’ is the most common occurrence.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">So I choosed the arbritrary color ‘grey’<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">Maybe you could consider to use poi’s instead
of polygons for historic.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">If somebody likes a different color, give me a
hint.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">Kind regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB">Joris<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;mso-fareast-language:EN-US"
lang="EN-GB"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:35.4pt"><b>Van:</b>
mkgmap-dev <a class="moz-txt-link-rfc2396E" href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a>
<b>Namens </b>osm@pinns<br>
<b>Verzonden:</b> dinsdag 15 januari 2019 22:01<br>
<b>Aan:</b> <a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<b>Onderwerp:</b> Re: [mkgmap-dev] default style
improvements / updated typ-file<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:35.4pt"><o:p> </o:p></p>
<p style="margin-left:35.4pt">Hi Jorus<o:p></o:p></p>
<p style="margin-left:35.4pt">You have a draworder for 0x1e
without a matching polygon.<o:p></o:p></p>
<p style="margin-left:35.4pt">(Also, to have 0x53 sharing the
same draworder as 0x4b might depending on your map be
problematic)<o:p></o:p></p>
<p style="margin-left:35.4pt">r<o:p></o:p></p>
<p style="margin-left:35.4pt">Nick<o:p></o:p></p>
<div>
<p class="MsoNormal" style="margin-left:35.4pt">On 15/01/2019
20:51, Joris Bo wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre style="margin-left:35.4pt">Hello<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">My previous typ had 2 bugs (No draworder for new lake 0x41) making lakes invisible and missing wilderniss hut<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Both are fixed in attached typ.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">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.<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Feel free to send more findings<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Kind regards<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Joris<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">-----Oorspronkelijk bericht-----<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Van: mkgmap-dev <a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" moz-do-not-send="true"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a> Namens Ticker Berkin<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Verzonden: maandag 14 januari 2019 12:24<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Aan: Development list for mkgmap <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" moz-do-not-send="true"><mkgmap-dev@lists.mkgmap.org.uk></a><o:p></o:p></pre>
<pre style="margin-left:35.4pt">Onderwerp: Re: [mkgmap-dev] default style improvements / upated typ-file<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Hi<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">I agree the name change from mkgmap.txt to something else (no problem with mapnik.txt) is needed.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">I haven't been through this TYP in detail yet. Some of my previous comments still stands:<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> <a href="http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029103.html" moz-do-not-send="true">http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029103.html</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">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. <o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">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:<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> <a href="http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029146.html" moz-do-not-send="true">http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2018q4/029146.html</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt">but there will be some differences from this post.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">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.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">It will be a few days before I'm able to do anything in this area.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">We need some pointers in the documentation to the collection of TYP -files.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Please can we have these TYP-files in "trunk". I think the "default -typ" branch it is a hindrance.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Regards<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Ticker<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">On Mon, 2019-01-14 at 06:51 +0000, Gerd Petermann wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre style="margin-left:35.4pt">Hi Joris,<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">I've replaced the default style in the typ branch by that from trunk <o:p></o:p></pre>
<pre style="margin-left:35.4pt">and added your typ with that. I hope that was right?<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4263" moz-do-not-send="true">http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4263</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">I think about a move/rename of styles\default\typ.txt to typ <o:p></o:p></pre>
<pre style="margin-left:35.4pt">-files\mapnik.txt using the command svn move styles\default\typ.txt <o:p></o:p></pre>
<pre style="margin-left:35.4pt">typ-files\mapnik.txt<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Would that be okay for you?<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Reg. the other changes I hope that Ticker has an answer.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Gerd<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">________________________________________<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Von: mkgmap-dev <a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" moz-do-not-send="true"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a> im Auftrag <o:p></o:p></pre>
<pre style="margin-left:35.4pt">von Joris Bo <a href="mailto:jorisbo@hotmail.com" moz-do-not-send="true"><jorisbo@hotmail.com></a><o:p></o:p></pre>
<pre style="margin-left:35.4pt">Gesendet: Sonntag, 13. Januar 2019 12:11<o:p></o:p></pre>
<pre style="margin-left:35.4pt">An: Development list for mkgmap<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Betreff: Re: [mkgmap-dev] default style improvements / upated typ <o:p></o:p></pre>
<pre style="margin-left:35.4pt">-file<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Hello,<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">I modified the type-file up to Ticker's changes in build r4262.<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Latest changes can also be found on<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="https://github.com/Jorisbo/Mkgmap-Mapnik-Style-Garmin" moz-do-not-send="true">https://github.com/Jorisbo/Mkgmap-Mapnik-Style-Garmin</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt">It already reflects some new mapnik colors which will be first visible <o:p></o:p></pre>
<pre style="margin-left:35.4pt">on <a href="http://www.openstreetmap.org" moz-do-not-send="true">www.openstreetmap.org</a> in a couple of days<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">The deltas I found after comparing Tickers changes are <o:p></o:p></pre>
<pre style="margin-left:35.4pt">=======================================================<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Added rendering for polygons<o:p></o:p></pre>
<pre style="margin-left:35.4pt">1)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> place=suburb [0x02 resolution 19]<o:p></o:p></pre>
<pre style="margin-left:35.4pt">2)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> # mop up any remaining water areas<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> waterway=* & waterway!=no & area!=no {add <o:p></o:p></pre>
<pre style="margin-left:35.4pt">name='${waterway|subst:"_=> "}'} [0x3b resolution 22]<o:p></o:p></pre>
<pre style="margin-left:35.4pt">3)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> natural=water & area_size() < 100000 [0x41 resolution 22] # <o:p></o:p></pre>
<pre style="margin-left:35.4pt">Small Lake<o:p></o:p></pre>
<pre style="margin-left:35.4pt">4)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> dock=drydock [0x4c resolution 22] # might also have <o:p></o:p></pre>
<pre style="margin-left:35.4pt">natural=water<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> natural=water & water=lock [0x4c resolution 22 default_name <o:p></o:p></pre>
<pre style="margin-left:35.4pt">'Lock']<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Added rendering for lines<o:p></o:p></pre>
<pre style="margin-left:35.4pt">5)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> highway=raceway | highway=gallop {add name='${highway}'}<o:p></o:p></pre>
<pre style="margin-left:35.4pt">[0x30 resolution 23]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Some changes to be considered?<o:p></o:p></pre>
<pre style="margin-left:35.4pt">=======================================================<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Different kinds of public transport are mapped to the same symbol.<o:p></o:p></pre>
<pre style="margin-left:35.4pt">For now I choose the arbritary bus_station as the most common<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 106: amenity=bus_station [0x2f08 resolution 23]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 126: amenity=ferry_terminal [0x2f08 resolution 22]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 206: railway=station [0x2f08 resolution 22]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 207: (public_transport=platform & rail=yes) | <o:p></o:p></pre>
<pre style="margin-left:35.4pt">railway=halt [0x2f08 resolution 23]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Different kinds of roads mapped to the same linetype, especially <o:p></o:p></pre>
<pre style="margin-left:35.4pt">cycleways deserve there on linetype I think<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 190: highway=bridleway [0x07 road_class=0 road_speed=0 <o:p></o:p></pre>
<pre style="margin-left:35.4pt">resolution 23]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 197: highway=service & service=parking_aisle [0x07<o:p></o:p></pre>
<pre style="margin-left:35.4pt">road_class=0 road_speed=1 resolution 24]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 198: highway=service & (service=alley |<o:p></o:p></pre>
<pre style="margin-left:35.4pt">service=driveway) [0x07 road_class=0 road_speed=0 resolution 23]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 199: highway=service [0x07 road_class=0 road_speed=2 <o:p></o:p></pre>
<pre style="margin-left:35.4pt">resolution 22]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 201: highway=cycleway [0x07 road_class=0 road_speed=1 <o:p></o:p></pre>
<pre style="margin-left:35.4pt">resolution 23]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"> Line 214: highway=turning_loop | highway=turning_circle | <o:p></o:p></pre>
<pre style="margin-left:35.4pt">highway=layby | highway=escape | highway=emergency_bay [0x07<o:p></o:p></pre>
<pre style="margin-left:35.4pt">road_class=0 road_speed=0 resolution 24]<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Add different (non-routable) linetype for highway = construction <o:p></o:p></pre>
<pre style="margin-left:35.4pt">instead of converting them to a routable footway (0x16)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Any comments, please let me know,<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Kind regards Joris<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">-----Oorspronkelijk bericht-----<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Van: mkgmap-dev <a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" moz-do-not-send="true"><mkgmap-dev-bounces@lists.mkgmap.org.uk></a> Namens Ticker <o:p></o:p></pre>
<pre style="margin-left:35.4pt">Berkin<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Verzonden: vrijdag 11 januari 2019 10:30<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Aan: Development list for mkgmap <a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" moz-do-not-send="true"><mkgmap-dev@lists.mkgmap.org.uk></a><o:p></o:p></pre>
<pre style="margin-left:35.4pt">Onderwerp: Re: [mkgmap-dev] default style improvements<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Hi Gerd<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Here is summary of the changes:<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">A few minor layout tidy-ups<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Add GBR section to inc/access_country<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Do aeroway=runway/taxiway/taxilane as lines unless marked as area=yes <o:p></o:p></pre>
<pre style="margin-left:35.4pt">and show these lines even when also a highway<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Ignore more highways when abandoned/disused/demolished<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Ignore more highway tags that are not suitable for routing<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Convert<o:p></o:p></pre>
<pre style="margin-left:35.4pt">highway=steps/corridor/stepping_stones/elevator/escalator/platform to <o:p></o:p></pre>
<pre style="margin-left:35.4pt">footway with bicycle=no and remove later test for steps<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Convert highway=crossing/virtual to path<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Don't convert footway to cycleway, but more rules to convert path to <o:p></o:p></pre>
<pre style="margin-left:35.4pt">footway/cycleway/bridleway<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Add footway around man_made=pier even if area=yes<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Fix common bad tagging for highway= by converting to the presumed <o:p></o:p></pre>
<pre style="margin-left:35.4pt">values<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Put routable path around highway=pedestrian closed areas; <o:p></o:p></pre>
<pre style="margin-left:35.4pt">squares/plazas often don't have other routing joining all entry/exit <o:p></o:p></pre>
<pre style="margin-left:35.4pt">ways. Similarly for footway. Then continue to allow any polygon <o:p></o:p></pre>
<pre style="margin-left:35.4pt">processing<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Handle some rarer highway types by converting to more generic type<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show any other water lines<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Removed all the {set cityxx/tmp:city}, & cityxx/tmp:city!=yes, <o:p></o:p></pre>
<pre style="margin-left:35.4pt">continue with_actions bits from place=city/town...<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Group the rules amenity=restaurant/fast_food, cuisine= to clarify, <o:p></o:p></pre>
<pre style="margin-left:35.4pt">simplify and show better how it relates Garmin "Food & Drink" search <o:p></o:p></pre>
<pre style="margin-left:35.4pt">and add some more cuisines. One effect of this is that <o:p></o:p></pre>
<pre style="margin-left:35.4pt">amenity=fast_food,cuisine=pizza/grill moves to the "Fast Food"<o:p></o:p></pre>
<pre style="margin-left:35.4pt">category. The other effect is that an element that is both a <o:p></o:p></pre>
<pre style="margin-left:35.4pt">Restaurant and a Lodging now shows as Lodging rather than Restaurant<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">For leisure=* where sport might be involved, show the sport if no name <o:p></o:p></pre>
<pre style="margin-left:35.4pt">available<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show canal/lock as 0x6505 (Water Features>Canal)<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show aeroway=runway/taxiway/taxilane as polygon only if marked as <o:p></o:p></pre>
<pre style="margin-left:35.4pt">area=yes<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Increase resolution that amenity=cafe/fast_food/restaurant polygons <o:p></o:p></pre>
<pre style="margin-left:35.4pt">show at<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show place=suburb<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Alternative rule to show highway=pedestrian as square/plaza unless <o:p></o:p></pre>
<pre style="margin-left:35.4pt">explicit area=no. highway=footway show as square/plaza if explicit <o:p></o:p></pre>
<pre style="margin-left:35.4pt">area=yes<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Don't assume any other closed highway is parking area, just <o:p></o:p></pre>
<pre style="margin-left:35.4pt">services/rest_area<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show more historic=*<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show drydock, canal & lock differently from standard natural=water, <o:p></o:p></pre>
<pre style="margin-left:35.4pt">and use a different code for small lakes<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show any other water area<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Show all man_made=* unless explicit area=no<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Regards<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Ticker<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">On Fri, 2019-01-11 at 06:13 +0000, Gerd Petermann wrote:<o:p></o:p></pre>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<pre style="margin-left:35.4pt">Hi Ticker,<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">please, can you summarize the changes implemented with this patch?<o:p></o:p></pre>
<pre style="margin-left:35.4pt">Need this for the svn commit message.<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">Gerd<o:p></o:p></pre>
</blockquote>
<pre style="margin-left:35.4pt"><o:p> </o:p></pre>
<pre style="margin-left:35.4pt">_______________________________________________<o:p></o:p></pre>
<pre style="margin-left:35.4pt">mkgmap-dev mailing list<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" moz-do-not-send="true">mkgmap-dev@lists.mkgmap.org.uk</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" moz-do-not-send="true">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt">_______________________________________________<o:p></o:p></pre>
<pre style="margin-left:35.4pt">mkgmap-dev mailing list<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" moz-do-not-send="true">mkgmap-dev@lists.mkgmap.org.uk</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" moz-do-not-send="true">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><o:p></o:p></pre>
</blockquote>
<pre style="margin-left:35.4pt">_______________________________________________<o:p></o:p></pre>
<pre style="margin-left:35.4pt">mkgmap-dev mailing list<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" moz-do-not-send="true">mkgmap-dev@lists.mkgmap.org.uk</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" moz-do-not-send="true">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><o:p></o:p></pre>
<p class="MsoNormal" style="margin-left:35.4pt"><br>
<br>
<o:p></o:p></p>
<pre style="margin-left:35.4pt">_______________________________________________<o:p></o:p></pre>
<pre style="margin-left:35.4pt">mkgmap-dev mailing list<o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" moz-do-not-send="true">mkgmap-dev@lists.mkgmap.org.uk</a><o:p></o:p></pre>
<pre style="margin-left:35.4pt"><a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" moz-do-not-send="true">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><o:p></o:p></pre>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
mkgmap-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mkgmap-dev@lists.mkgmap.org.uk">mkgmap-dev@lists.mkgmap.org.uk</a>
<a class="moz-txt-link-freetext" href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a></pre>
</blockquote>
</body>
</html>