All OpenMTBMaps and VeloMaps now with DEM – Digital Elevation Model plus countless improvements

Some of you may have noticed - that the European country maps since last week now include a DEM - digital elevation model in addition to the contourlines. Todays and Tomorrows map update will now bring DEM to all maps - this has quite a few advantages. E.g. altitude profiles for tracks, a more plastic and easier to understand topography overview in Basecamp on desktop - and the quite useful 3D view in Basecamp (make sure to set elevation exaggeration in Options --> Display --> scroll down to 3D to 0% - the default 100% is really too much inside the Alps. 

Lago die Garda 2D with DEM

above the Lago die Garda and some of it's nicest trails - notice the DEM shading....

 

On your Garmin GPS device I have so far not enabled DEM (if you set show DEM to auto it will not show) - I'm working on adding this a couple of weeks later - but as it is only useful when zoomed out very far (if you're zoomed in close it only makes the map darker - and the GPS device screen is too small to properly see the altitude profile properly if zoomed in close). I may add in future DEM shading for devices for zoom levels 5km or 10km to 30km - this helps understanding the topography a bit - however even though I looked at optimizing this as well as possible - it still slows down the map drawing when panning the map around quite substantially (it's not too bad as first the map is drawn - then in a second step it's shaded). I will need to do some further tests on this before it will be released however.

My favourite place in Europe for Mtbiking - the Val D'Anniviers

For maps where the contourlines are not integrated but as a separate download - this may cause some chaos tomorrow as the old contourlines are replaced on server as the openmtbmap is created on server - but it may take some time to be downloadable on the FTP server. Especially for the VeloMaps tomorrow there will be many countries where the new contourlines are already online, but the map is not yet. European maps are not affected here however - and the OSx OpenMTBMaps are also not affected. However make sure especially on OSx that you do not reuse your old contourlines if the map is compiled Yesterday or newer! On windows the new installer will throw an error if you provide the old contourlines however the old installer (if map is older than yesterday) will happily unpack the new contourlines and the map will be broken (no contourlines visible - and when you try to send it to device it will fail).

As for some countries the contourlines including DEM became too big (5 countries overall, in Europe only Norway) those countries now have contourlines as external download. I'm sorry that for Norway last week the contourlines v3 download was not online until 2 days ago (so 4 days after the map update). 

Note here I am using 100% 3D exaggeration - this looks impressive but is not good for planning routes

Above Picture shows the Nordkette in Innsbruck with 100% 3D exaggeration - notice that on the backside - you cannot see much anymore. Therefore I advise to stay away from the exaggeration for planning - it's nice for looking at it though.

 

The next update of the Europe map (mid next week) will then also see DEM - it will be the last map to be changed to include DEM though.

 

In some places when routing along over the last 1-3 years the openmtbmaps and velomaps did cause crashes (fine if not using autorouting) - this was due to OSM mapping errors - in combination of my maps being aggressively tuned for best routing for MTBs and bicycles - most of these are now solved in software - and not problematic anymore (especially roundabouts were problematic). There are still a very few places where this can happen (maybe 40 in Germany, 50 in Italy, 10 in Austria and so on) - and I hope that at least 90% of those remaining will also be solved soon. The problem is always related to people drawing roads on top of each other in OSM without noticing their mistake - if then at least one of the overlaying incorrect ways is part of a hiking, bicycle or MTB relation (route) this likely caused problems. Also some super detailed areas where people drew roads shorter than 5m into OSM were problematic (this is 99% solved now).

 

Also last week only, some software misconfiguration caused some maps not to be digitally signed - and virus scanners running havoc - this is fixed in todays map update too - Sorry for the glitch it happened as I cleaned up the OS to dig out HDD space.

 

blank

Raxseilbahn in Lower Austria - like this with 0% altitude exaggeration the 3D view is pretty nice for planning!

 

English vs Local Language Maps

Over the last 2 months I invested a load of time to optimize the language / codepage handling of the OpenMTBMaps and VeloMaps.

I had originally implemented a very complicated system trying to make any map also usable for non native speakers of the local language - or people not able to read e.g. arabic or kyrillic. In the end this was a rather big mess even though it kinda worked for many countries.

Now I've changed this - there are local language maps - which are in local language and local script - as well as maps in english for any country that does not primarily use latin script.

Also all continent maps (except Antarctica and North America which are anyhow english speaking) are now available in English or local Language. South-America/Central America english maps will be available for download starting tomorrow.

The theory of how it should work is laid out below - if you find things not working drop a comment. Especially if you find OSM keys which are not implemented yet and would help in improving the map translations.

 

Map Updates:

Maps that are not available in English - will be updated weekly as before. All maps which are also available in English language - will be updated biweekly alternating between update in English in week 1, and update in local language in week 2 and so forth.

 

Who needs Unicode maps - a reminder:

Garmin blocked reading in free unicode maps about 2 years ago in their newest devices. However you can look around in the grey areas of the internet and you will find firmwares for basically all those devices unblocking the devices not reading in free unicode maps. This is a small part of the firmware taken out. If you use those changed firmwares only to display free unicode maps - it should be legal at least in European Union. It would not be legal to use those firmwares in order to display "pirated" Garmin original maps. In general of course for countries where latin is not primarily used unicode maps will be superior!

Please note: I will not help you in finding such firmwared. You can use google to find out more about this.

 

Both Unicode and Non Unicode are available in local and English:

Unicode local language maps: These maps use local language and local script - additionally for POI search for cities usually it's possible to use English as well. So the city Moscow in Russia will display as Москва however you can find it in the POI search also by searching for Moscow (and actually also by German Moskau). The address search will only work in local language - so you need to type: Москва as city in address search. In POI search Москва, Moscow or Moskau is all possible.

Unicode english language maps: These maps use English as label whenever possible (meaning in OSM database). If no English translation is available the maps tries to use English transcription from OSM database. If also no transcription exists - the map will show local language names.

POI search is possible in English, local Language and German language. Adress search is possible in English whenever English exists in OSM - else in local language.

Moscow will be used as a city for address search. POI search Moscow, Moskau or Москва is findable.

 

Non Unicode local language maps: These maps use local codepage (excpet for Chinese and Japanese where Garmin does not offer a non unicode codepage that can display the characters) and local naming. POI search is possible in English, German and local language.

Moscow in address search will be found under Moscow only. In POI search it can be found under Moscow, Moskau or Москва (as kyrillic codepage supports enough character to spell moscow also in latin)

Non Unicode english maps: These maps are in latin only. Maps uses English wherever available in OSM, if not then Transcription from OSM, if also not available a machine transcription is used - which is a bit faulty however!

Address Search is only possible in latin script - and often not working as you cannot guess the automatic transcription used for a streetname. As city names in OSM tend to exist also in English or proper transcription address search for a city or POI search usually works still okay. POI search in local script is not possible.

Moscow can be found under Moscow or Moskau - but not Москва