This datafield helps to improve the veloviewer explorer score, see</p><p></p><p>https://blog.veloviewer.com/veloviewer-explorer-score-and-max-square/</p><p></p><p>The header shows: number of tiles visited for the first time, number of unique tiles visited during current activity and the tile coordinates (relative to the home tile)</p><p></p><p>Below, tiles surrounding the current location are shown. Red=never visited, Dark-green: visited in the past, Light-green: visited during current activity. In addition the recent track and a heading-direction indicator are displayed.</p>
version 1.1.4: added support for Edge® 1000 and Edge® 1030</p><p>version 1.1.5: added support for landscape modes</p><p>version 1.1.6: fixed an issue that showed up with the newest firmwares</p><p>version 1.1.7: added support for Edge® 530 and Edge® 830</p><p></p><p>Warning: Garmin changed the maximal string length for the App settings to 256 Characters, which brakes the mechanism of importing your map to the app. Currently there is no workaround available.
This app requires access to:
Jim Karthauser
January 17, 2021
I understand that garmin has broken the app with the 256 character limit, but the app is now completely broken as I'm getting 'bad map string' error on setup, so it's storing no history at all now. :(
Hans Van Wijngaarden
December 2, 2020
I had the same problem as named in the other reviews: only red tiles. It seemed the kml file didn’t fit. I’ve tried several times on my Macbook with the same disappointing result. Today I tried again on a Windows computer and now I can say it works well. So in my opinion the app only works with a Windows computer.
Gregory D
August 12, 2020
Pretty useless : I followed the procedure (http://www.shmo.de/EveryTile/setup.html) to generate a string, but it is too long according to Garmin Express. Which means all my squares are red. Actually, they all become red whenever I switch my Edge 520 on to go for a ride... Which is of no help for veloviewer tiles, and not much help for tracking tiles as a rule anyway. Sad, because despite a spartan interface (very much to my liking), it seems it might have been great to use it as a on field complement to track tiles. Maybe the app could load the string from a file deposited on the edge instead of as a string from the IQ interface ? Or even, work out directly from a .kml file as downloaded on Veloviewer ?
Sorry, no statistics available yet.