[:en]All OpenMTBMaps and VeloMaps now with DEM – Digital Elevation Model plus countless improvements [:de]Alle OpenMTBMaps und VeloMaps ab nun mit DEM – digitalem Höhenmodell, sowie viele weitere Verbesserungen [:it]All OpenMTBMaps and VeloMaps now with DEM – Digital Elevation Model plus countless improvements [:es]All OpenMTBMaps and VeloMaps now with DEM – Digital Elevation Model plus countless improvements

[:en]

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!

 

[:de]

Einigen ist es vielleicht schon aufgefallen - seit letzter Woche haben fast alle europäischen Karten nicht nur Höhenlinien - sondern auch ein DEM - also ein Digitales Höhenmodell wenn die Höhenlinien in die Karte integriert werden. 

Mit dem heutigen/morgigem Kartenupdate wird dies auf alle Karten weltweit ausgeweitet. Dies hat einige Vorteile - so sieht man in Basecamp nun auch eine Höhenschattierung - welche bei der Orientierung beim planen visuell hilft. Auch kann man nun mit 3D Karten planen (was allerdings IMHO nur Sinn macht - wenn man vorher in Optionen --> Ansicht --> ganz runterscrollen zu 3D Überhöhung - 0% einstellt - bzw endlich gibt es auch bei Tracks ein Höhenprofil.

Das Höhenprofil bei Routen ist auch detaillierter - ABER hat jetzt meist genauso wie etwa bei Garmins eigenen Karten auch das Problem dass der Höhenunterschied eher überbewertet wird - 10-20% sollte man da in etwa abziehen dann passt es ganz gut.

Auch auf Garmin GPS Geräten ist das Höhenprofil nun deutlich nutzbarer.

Lago die Garda 2D with DEM

Hier etwa mein Lieblingstrail vorne runter zum Gardasee - man erkennt gut die Schattierung und Steilheit.

 

 

Auf Garmin GPS Geräten wird derzeit die Karte (noch) nicht plastisch angezeigt. Ich bin hier noch etwas am experimentieren ob man dies sinnvoll hinbekommt. Denn Sinn macht es nur wenn man recht weit rauszoomt - sonst verdunkelt es nur die Karte ohne dass man Zusatzinfos bekommt - und es bremst die meisten Geräte doch recht ordentlich aus. 

Wahrscheinlich kommen hier dann noch separate Karten für jene die auch am GPS Gerät eine Schattierung haben möchten - aber NUR im Bereich 5 oder 10 bis 30km Zoommaaßstab. Dass Problem dabei ist noch halbwegs Details zu sehen ohne das Gerät komplett auszubremsen beim Karte verschieben. Da probiere ich derzeit noch einiges durch und werde nächste oder übernächste Woche entscheiden ob es sich lohnt oder nicht.

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

Der Server lädt die neuen v3 Höhenlinien nach erstellen der Karte automatisch hoch - da die Karten aber teils auf dem FTP Server liegen der nur einmal pro Tag gespiegelt wird, kann es Morgen - gerade bei der VeloMap zur Situation kommen dass schon die neuen Höhenlinien online sind, aber noch die alten Karten. Morgen wird es also etwas chaotisch diesbezüglich. Dieses Problem betrifft aber NUR Karten wo die Höhenlinien separat sind, und betrifft vor allem Windows User. Für OSx wird es primär bei der VeloMap die zu neuen Höhenlinien geben.

In Europa hat nur Norwegen externe Höhenlinien (gut dazu noch Türkei/Ukraine/Russland) - sonst sind die Höhenlinien eh in den Karten integriert und damit immer passend.

Der Installer unter Windows überprüft automatisch ob die Höhenlinien neu sind, und gibt wenn nicht eine Fehlermeldung. Aber Achtung - die alten Installer installieren die neuen Höhenlinien ohne nachfragen/Problemmeldung nur funktionieren diese dann nicht bzw wird sich die Karte nicht senden lassen. 

Sorry auch nochmal dass für Norwegen 4 Tage lang gar keine Höhenlinien downloadbar waren (Sontag bis Mittwoch).

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

Hier ein Beispielscreenshot vom 3D Modus in Innsbruck mit 100% Überhöhung - man sieht gut dass am Nordhang der Nordkette die Karte deutlich zu gestaucht erscheint - sprich man erkennt nicht mehr viel. Daher 0% außer für Screenshots wo es um die Bervorderseite geht...

 

Die Europakarte werde ich Mitte nächster Woche updaten, und dann also auch mit neuen Höhenlinien mit DEM - wenn alles gut klappt.

 

In den letzten 1-3 Jahren gab es ein paar Kartenstellen wo die OpenMTBMaps oder VeloMaps beim autorouting abgestürzt sind - der Fehler liegt an einer Kombination aus dem aggressiven versuchen Fahrrad/MTB freundliche Wege zu wählen und Datenfehlern in OSM (zund zwar genauer - dort wo fehlerweise mehrmals derselbe Weg übereinander eingetragen ist - am übelsten wenn auch noch beide Wege Teil einer MTB/FAhrad/Wanderroute sind. 

Das Problem ist nun zu 95% gelöst - es verbleiben in DE etwa noch 20-30 Einzelne Stellen wo es noch zu abstürzen kommen kann - ich hoffe dass ich das in den nächsten Wochen auf 3-4 reduzieren kann. In Italien gibt es so Fehler etwas öfter. Dazu tritt es teils dort auf - wo extrem detailliert gemapped wurde - und Straßenstücke unter 5.4m Länge in OSM eingetragen sind - dies wird wohl leider weiter problematisch sein - ist aber auch sehr sehr selten.

Letzlich - letzte Woche beim Kartenupdate lief etwas bei den digitalen Signaturen schief - und viele Karten wurden nicht signiert - dass ist diese Woche wieder gelöst (verursacht durch aufräumen des OS wobei eine Library die wichtig ist wegfiel.)

 

blank

Raxseilbahn in Niederösterreich - 3D Ansicht mit 0% Überhöhung - wie man sieht macht so die 3D Ansicht zum planen schon Sinn, es ist noch alles gut erkennbar (solange <50-60° steil) - und man erkennt recht gut die Steilheit.

[:it]

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!

[:es]

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!

 

[:en]English vs Local Language Maps [:de]English vs Local Language Maps [:it]Mappe localizzate vs inglese

[:en]

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 Москва

 

[:de]

Bisher waren die Openmtbmaps und Velomaps je nach Land in lokaler Sprache, bzw in Ländern die keine lateinische Schrift benutzen - meist in Englisch (aber nur wenn zu dem Land im Openstreetmap Wiki eine Codepage Definition vorlag - also etwa nicht in Israel).

In den letzten Wochen habe ich nun sehr sehr viel Zeit investiert dieses Wirrwarr aufzulösen. Nun gibt es in allen Ländern wo dies nötig ist - die Karten in lokaler Sprache - oder als separater Download in englischer Sprache. Wo halte ich dies für nötig? Nun zuallererst einmal bei allen Karten in denen Länder vorkommen wo die Normalschrift nicht Latein ist.

Kann man etwa kein kyrillisch lesen - so macht es ja am meisten Sinn direkt eine englischsprachige Karte zu nutzen - im Falle das kein Englisches Label in OSM existiert - wird ein transkribiertes Label genommen - nur im Falle dass es auch dieses nicht in OSM gibt - wird eine automatische Transkription nach Latein vorgenommen - dies aber nur bei den Non Unicode Karten - meist sind die automatischen Transkriptionen einfach nicht sinnvoll/vernünftig - daher sind die (Standard) Unicode Karten ohne maschinelle Transkription.

Zusätzlich sind auch alle Kontinentkarten (außer Nordamerika/Antarktika wo eh englisch Standard ist) auch in Englisch verfügbar. Dies betrifft also Zentral und Südamerika. Ich glaub zwar die meisten werden hier eine lokale Karte bevorzugen - schließlich sind spanische Namen für uns Europäer leicht zu verstehen - aber downloadbar ist es trotzdem. Hier betrifft es eh fast nur Stadtnamen (Süd/Zentralamerika sind ab Morgen downloadbar - alle anderen Karten sind schon online).

Europa, Asien und Afrika Kontinentkarten sind wegen Ländern die nicht Latein benutzen eh in Unicode lokal Sprache, Unicode englisch, Non Unicode lokale Sprache, Non Unicode Englisch downloadbar.

 

Allerdings - habe ich soweit möglich in den Suchfunktionen in den Ländern mit lokaler Sprache - zusätzlich auch die Englischen Namen suchbar gemacht. Dies betrifft aber leider nur die POI Suche - die Adresssuche geht auf den meisten Geräten leider nur in lokaler Sprache oder Englischer Sprache. Wenn man aber etwa nach einer Stadt per POI sucht - kann man sowohl nach München oder nach Munich suchen - man wird beides finden.

In den Non Unicode Karten ist die lokale Karte in komplett lokaler Sprache und Schrift - also etwa kyrillisch - die POI Suche ermöglicht aber auch Suche nach englischem Stadtnamen.  Die englische Karte allerdings ermöglicht im Normalfall keine Suche in lokaler Schrift/Sprache

 

Updates: In allen Ländern wo es englischsprachige und lokalsprachige Versionen gibt - werden die Karten nun alternierend geupdated. Länder wo es keine englischsprachige Version gibt bleibem beim wöchentlichen Update.

 

Nochmal zur Erinnerung - die Non Unicode Karten braucht man nur wenn das GPS Gerät die Unicode Karten sperrt (in den meisten Garmin GPS die seit 2016 neu vorgestellt wurden) bzw in ganz ganz alten Geräte (so vor 2005 vorgestellt). Es gibt allerdings in den weiten des Internets gehackte Firmwares für quasi alle neuen GPS Geräte von Garmin damit diese auch Unicode Karten einlesen ohne diese zu blockieren. Jeder muss hier selber wissen ob er dass will oder nicht. Solange diese Firmware nicht dazu benutzt wird kopiergeschützte Garmin Originalkarten als nicht lizensierte Kopie zu verwenden sollte der Gebrauch solcher Firmwares innerhalb der EU zumindest legal sein.

Ich werde diesbezgüglich alle Kommentare löschen bzw keine Hilfe bieten wo diese Firmwares zu beziehen sind - wer hier seine Fimware umflashen möchte - via google findet man da recht schnell Quellen.

 

Wenn ihr irgendwo in den Karten noch Verbesserungsmöglichkeiten seht was die Sprachen angeht - und in OSM dafür Keys existieren - werde ich versuchen die noch umzustezen. Ich denke es ist erst so 95% perfekt.

[:it]

Negli ultimi 2 mesi ho investito diverso tempo per ottimizzare la gestione delle lingue/codifiche delle OpenMTBMaps e VeloMaps.

Originariamente avevo implementato un sistema molto complesso per rendere utilizzabili le mappe anche per chi non parlava il linguaggio locali, o le persone non in grado di leggere ad esempio l'arabo o il cirillico. Alla fine è diventato tutto confusionario anche se funzionava per molti paesi.

Adesso ho cambiato questo sistema, ci sono mappe localizzate, tradotti in lingua con i caratteri locali, e mappe in inglese per tutti i paesi che non utilizzano principalmente caratteri latini.

Anche le mappe dei continenti (ad eccezione dell'Antartide e il Nord America che parlano comunque inglese) sono ora tradotte in Inglese o tradotte. le mappe relative al Sud America/Centro America saranno disponibili per il download da domani.

Se trovassi qualcosa che non funziona lascia un commento. Specialmente se dovessi trovare chiavi OSM che non sono ancora implementate e volessi aiutare nella traduzione delle mappe.

Aggiornamento delle mappe:

Le mappe che non sono disponibili in Inglese saranno aggiornate settimanalmente come prima. Tutte le mappe che sono disponibili anche in inglese saranno aggiornate ogni 2 settimane, alternando l'aggiornamento in inglese nella prima settimana e l'aggiornamento in lingua locale nella seconda settimana e così via.

Chi ha bisogno delle mappe Unicode - reminder:

Garmin ha bloccato la lettura delle mappe libere Unicode circa 2 anni fa nei suoi nuovi dispositivi.
Ad ogni modo cercando nei meandri di internet si trovano firware per questi dispositivi che non leggono le mappe in Unicode, in cui una piccola parte del firmware è stata rimossa. Se utilizzate questi firmware modificati per visualizzare solo le mappe libere in Unicode dovrebbe essere legale, per lo meno nell'Unione Europea.
Non è legale invece utilizzare questi firmware per visualizzare mappe "pirata" originali Garmin.
In generale nei paesi non latini le mappe Unicode saranno superiori!

Notate bene: non vi aiuterò a trovare questi tipi di firmware, potete utilizzare Google per sapere di più a riguardo.

Sia le mappe Unicode che non Unicode sono disponibili in lingua e in inglese:

Mappe Unicode localizzate: Queste mappe utilizzano lingua e caratteri localizzati, inoltre per la ricerca dei POI delle città solitamente è possibile utilizzre l'inglese.
Quindi la citta Mosca in Russia sarà visualizzata come Москва ma si potrà trovare nella ricerca dei POI anche con la dicitura Moscow (e anche in italiano come Mosca).
La ricerca degli indirizzi invece funzionerà solamente nella lingua locale, quindi sarà necessario digitare: Москва come città nella ricerca indirizzi.
Nella ricerca POI saranno consentiti Москва, Moscow o Mosca.

 

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 Москва