The same applies in non rectangle shapes:Īt this scale it should only show the roads, the Fenix is also configured to show minimal details, no boundaries.įor the north of Munich only the highways are shown, as it should be, but for the south this mess happens.img file - what is also proven to be true when scrolling leftwards (everything is visible), and rightwards too (again, everything visible) only in the overlapping case it is screwed. If sliding back, it get's corrupted again.įrom MapInstall I saw, that there a region boundary was lying but as all of this is covered in the. So you can get from a corrupted map to a good map. Shown in the picture is the exact same location, the only thing that makes a difference, is moving the map a bit to the side. Whenever I move the map, parts of it are shown properly, other useless. I copied them via MTP to the Fenix into the GARMIN folder. As alternative I downloaded the maps as.Of course these data cannot be transferred, when MapInstall assumes that already 6KB are too much.īut why this problem at all? There is plenty of space there is no other OSM map on the Fenix and it also does not - as the user manual says - suggest to delete anything for it.
When selecting all regions of Germany, it comes up with this (" 2.79 GB too much"):.(and before anyone is guessing the PC also has more than enough space: C: has 230 GB left, D: 1,22 TB).The map for Germany is 2.9 GB - so should fit perfectly well into the internal storage.This while on the Fenix 14 GB space are free no music, no other audio recordings, only plain training data stored on it.
#Garmin basecamp download install
OSM maps transfered via MTP are not shown properly.(BaseCamp +) MapInstall make problems, when I try to install OSM maps to my Fenix.
0 kommentar(er)
