<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Peat Faerie on Medium]]></title>
        <description><![CDATA[Stories by Peat Faerie on Medium]]></description>
        <link>https://medium.com/@peatfaerie?source=rss-7f0cd3b05fa7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*q84XqoChe7hqe2Hr.jpg</url>
            <title>Stories by Peat Faerie on Medium</title>
            <link>https://medium.com/@peatfaerie?source=rss-7f0cd3b05fa7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 13:33:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@peatfaerie/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to create a tile grid overlay for the Garmin Edge based on VeloViewer unexplored tiles]]></title>
            <link>https://peatfaerie.medium.com/how-to-create-a-tile-grid-overlay-for-the-garmin-edge-based-on-veloviewer-unexplored-tiles-5b36e7c401bd?source=rss-7f0cd3b05fa7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b36e7c401bd</guid>
            <category><![CDATA[veloviewer]]></category>
            <category><![CDATA[garmin-edge]]></category>
            <category><![CDATA[tile-explorer]]></category>
            <dc:creator><![CDATA[Peat Faerie]]></dc:creator>
            <pubDate>Sun, 20 Dec 2020 22:22:01 GMT</pubDate>
            <atom:updated>2021-02-08T21:01:04.428Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p>This is a short HOWTO on creating a map overlay for the Garmin Edge default map, containing an unexplored tile grid downloaded from <em>VeloViewer</em>.</p><p>All it takes is three simple steps:</p><ol><li>Download the grid of unexplored tiles from <a href="https://veloviewer.com/"><em>VeloViewer</em></a></li><li>Convert the downloaded KML file to the OSM format using <a href="https://www.gpsbabel.org/"><em>GPSBabel</em></a></li><li>Generate a transparent map layer with a tile grid in a Garmin compatible format with <a href="http://www.mkgmap.org.uk/"><em>mkgmap</em></a></li></ol><p>Of course, at the end you need to transfer the generated map to your device.</p><h4>Step 1 — Downloading the grid</h4><p>To get the coordinates of your unexplored tiles, you have to go to your <em>VeloViewer</em> activities tab.</p><p>Zoom the map to the specific area that you are interested in. <em>VeloViewer</em> will only export those unexplored tiles which are fully visible in the current view.</p><p>Click the gear icon on the right and click the unexplored tiles export button. There is a number of tiles in the current map view displayed next to it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i-7WWeC1UzAKsNRx4bE_BQ.png" /></figure><p>By default the file is saved as the <em>unexplored_tiles.kml </em>in a KML format.</p><p>It is best to create a new folder and to save the file in there to keep everything in one place (there are several more files to come).</p><p><strong>Removing the “tick” (optional)</strong></p><p>To differentiate between two types of tiles, <em>VeloViewer</em> adds a small “tick” in the upper left corner of an unvisited tile:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WKX8wNfadvu_rLPMVG3UBw.png" /><figcaption>Unexplored tiles with “ticks”</figcaption></figure><p>You can erase it by removing the coordinates of the first point in every tile, using <em>perl</em> (or your other favourite regexp tool):</p><pre>perl -pi -e &quot;s/(&lt;coordinates&gt;)[^ ]+ /\1/g&quot; unexplored_tiles.kml</pre><p>After that the <em>unexplored_tiles.kml </em>file should have 5 points for every tile, instead of 6 and the resulting grid will have no ticks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xScd75ZxnnxRqz8p_SK-Yw.png" /><figcaption>Unexplored tiles without “ticks”</figcaption></figure><p>But you can also leave it as is if you like.</p><h4>Step 2 — Converting to OSM format</h4><p>The conversion is necessary because the <em>mkgmap</em> program, which generates maps for Garmin GPS units, requires a file in the OSM format as an input.</p><p>To convert between different GPS formats it is best to use <a href="https://www.gpsbabel.org/index.html"><em>GPSBabel</em></a>. You can use the GUI wrapper if you want, but for me the standard command line version is much easier.</p><p>It is important to also tag all the lines with <em>tag=highway:primary. </em>It will be used later to set the style of the grid lines.</p><pre>gpsbabel -i kml -f unexplored_tiles.kml -o osm,tag=highway:primary  -F unexplored_tiles.osm</pre><p>The result of the above command will be written to the <em>unexplored_tiles.osm</em> file which is the input file for the <em>mkgmap.</em></p><h4>Step 3 — Generating the map</h4><p>If you don’t have the <em>mkgmap</em> tool, you have to get it first from <a href="http://www.mkgmap.org.uk/"><em>this site</em></a> and unzip it into your working folder (after unzipping there should be a subfolder named <em>mkgmap-rXXXX, </em>where <em>XXXX</em> is the current version).<br>At the time of writing the newest version was 4600. <br>If your version is different, or you have <em>mkgmap.jar</em> in another location, you will have to update the <em>java</em> command below to reflect it.</p><p><strong>Config files</strong></p><p>To generate a proper map layer with <em>mkgmap</em> you need to create three config files in your working folder, with the content given bellow (and name them accordingly).</p><p>You can also download them from my Dropbox share:</p><p><a href="https://www.dropbox.com/sh/83twx8s0uq6ohox/AADpvJqDOaznK0ORX8iRPUT7a?dl=0">https://www.dropbox.com/sh/78uzch2q82r07bq/AAAzaAxp2Dz-8TQE7R26Jwoya?dl=0</a></p><p><em>For those using Linux/Unix or MacOS, there are also shell scripts available for every command used in this article.</em></p><p><strong><em>typ.txt</em></strong></p><p>The first file is a TYP file which contains style definitions for Garmin maps (actually TYP file is a binary format but it will be automatically created based on the <em>typ.txt</em> file).<br>You can modify it if you want to set a different line width (default is 1 pixel) or a different colour (default is #AA0000 — dark red). <br>It is possible to tweak it a little more (e.g. making dashed lines instead of solid ones, etc.), but that is out of scope of this HOWTO. If you are interested take a look at the <em>typ2.txt</em> file on my Dropbox for some more details.</p><pre>[_line]<br>Type=0x01<br>UseOrientation=N<br>LineWidth=1<br>Xpm=&quot;0 0 1 0&quot;<br>&quot;1 c #AA0000&quot;<br>String=solid line<br>FontStyle=NoLabel<br>[end]</pre><p><strong><em>mkgmap.style</em></strong></p><p>This file applies the style defined in the TYP file to the grid lines, based on the tag set during the conversion, and also sets the visibility levels.</p><pre>&lt;&lt;&lt;version&gt;&gt;&gt;<br>0<br>&lt;&lt;&lt;options&gt;&gt;&gt;<br>levels: 0:24, 1:22, 2:20, 3:18, 4:16<br>&lt;&lt;&lt;lines&gt;&gt;&gt;<br>$highway=primary [0x1 level 3]</pre><p><strong><em>config.txt</em></strong></p><p>This file contains the list of options for the <em>mkgmap </em>program. They can also be declared as command line parameters, it is just easier this way. I won’t explain them here as they are well documented in the <em>mkgmap</em> docs.</p><pre>family-id: 66<br>product-id: 1<br>latin1<br>description: unexplored tiles<br>draw-priority: 100<br>style-file: mkgmap.style<br>transparent<br>gmapsupp<br>output-dir=output</pre><p><strong>Generating the map</strong></p><p>The <em>mkgmap</em> program is written in Java so you need the JRE to run it.</p><pre>java -jar mkgmap-r4600/mkgmap.jar -c config.txt typ.txt unexplored_tiles.osm</pre><p>And that’s about it. You should now have a new subfolder named <em>output</em>, with several files in it. One of them is <em>gmapsupp.img</em> which is the Garmin map with the grid layer. Upload it to your Garmin Edge, directly into the <em>Garmin</em> folder (you can change the name of the file to whatever you like, e.g. <em>unexplored.img</em>; just don’t overwrite existing files unless it is a previous version of your map).</p><p>Next time you run your Garmin Edge the map should already be present on the list of the installed maps<em>:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/282/1*XvMZvKi7-goVdX9Qn2Fg-g.png" /><figcaption>Unexplored tiles map on the list of maps</figcaption></figure><p>and the grid should be visible on the map as well:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*tL4T_WK1iGopFJbUselB1g.png" /><figcaption>Garmin map with a tile grid overlay</figcaption></figure><p>Happy exploring! 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b36e7c401bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>