Example in Vienna
O.k. I noticed that many of you simply think that the newer Garmin Mapsource versions do work and display the maps correctly. I wan't to help you to correct that wrong assumption
1. Actually Garmin Mapsource >6.14.1 currently does not display any map correctly, as they are squashed together. The further away you move from the equator, the worse. If you can live with it, fine, I would never accept it. (it means that 10cm horizontal on your screen, do not represent the same length as 10cm vertical). A square becomes a simple rectangle.
On top 6.13.6 – below 6.15.6 (though that should not be hard to guess)
Example showing the maplegend
Mapsource 6.15.7 and higher now shows the map legend correctly (apart from the broken projection fixed to Garmins Headquarters, the higher up north you live the worse).
Again 6.13.6 on top of the lower Image is still from Mapsource 6.15.6 which is why mtb attributes were not shown correctly. However Garmin Basecamp still displays maps incorrect as below.
Downgrade Garmin Mapsource if you are using a newer version
3. There are several other problems with newer Mapsource version, do yourself a favour, and downgrade. Writing and complaint e-mail to Garmin about broken Mapsource is never wrong either. How to downgrade is written here http://openmtbmap.org/tutorials/install-mapsource/ :
Spend a token to make the maps even better
Hi,
Maybe I’m missing something (as I don’t have the software in question), but this just looks like it’s in the wrong projection – a more noticeable problem down here in NZ.
Do you need to change it to WGS84 or something? JOSM has a similar setting, that when set incorrectly, gives you exactly what you’re seeing there.
My apologies if I’m suggesting anything really obvious/silly!
No, no wrong projection, only Garmin ***** engineers fixing longitude/lattitude stretch in one position for the whole world. I don’t know how stupid one can be to output such a crap but Garmin is unreactive about this since over a year.