Video Tutorial how to send the maps. For more Video Tutorials explaining all the basics go here: https://openmtbmap.org/tutorials/beginnners_windows/
Contents
About the Maps - Please Read
Maps are available Worldwide. They are usually updated every Friday.
- Map Data
All maptiles are compiled with mkgmap using map data from openstreetmap.org & Contributors. You can use and edit the map data by visiting openstreetmap.org.
Thanks to Geofabrik for providing the map data snapshots which I use to create the maps.
-- For Copyrights please see the Installer or if you unextract the installer see the file copyright.txt.
Contourlines/DEM data:
The altitude data for the contourlines is from varying sources in the following priority (if available):
- LIDAR data from open government data and other openly available sources - collected and converted to hgt format by - Sonny - https://data.opendataportal.at/dataset/dtm-austria This data is very very high quality and resolution - there is no better open data available according to my knowledge.
- ALOS World 3D30 - überall zwischen N60° und S60°
- SRTM 1" v3.0 - very rarely for some tiles missing in ALOS data - also only between N60° and S60°.
- Viewfinderpanormas 1" - then 3" - above N60° / below S60° as there is no SRTM data nor ALOS or LIDAR Data avialble.
- SRTM v3.0 by NASA 3" v3.0 (very very rarely, 8 tiles only)
more exact info which data is used where - inside the copyright.txt files.
The default equidistance is 20m - meaning every 20m altitude one contourline. For all countries with the highest point below 1000m - the default equidistance is 10m. However due to popular demand I also additionally offer optional 10m contourlines for all countries with altitude above 1000m. The installer cannot integrate the optional 10m contourlines into the maps however.
Programs to Display the Openmtbmap
Besides being shown on (nearly) all Garmin GPS devices - most People will use Garmin Basecamp (v4 or later) to show the maps on their Desktop and plan tours/trips.
For anyone on the good side of earth AKA Linux - Openmtbmap.org maps are also correctly shown in Qlandkarte_GT - QLandkarte_GT is compatible with all big OS (Linux, MacOSx and well Windows too). Linux users can alternatively install Mapsource 6.13.6 in WINE. The .exe files can be unpacked with 7zip. After unpacking you find instructions for Qlandkarte / Linux use in a .txt file (informations... .txt).
For Linux/Unix users there is also a script to unpack the maps, and automatically create a gmapsupp: https://github.com/btittelbach/openmtbmap_openvelomap_linux You can unpack the .exe with 7-zip , ( Linux users use p7zip-full --> see here for more details), MacOSx Users can use "Unarchiver" (requires v3.0 or newer) . After unpacking you find instructions for Qlandkarte / Linux use in a .txt file (informations... .txt).
For General Use - Basecamp is much better than Mapsource by now - The only thing were Mapsource is better is selecting parts of maps to send. The only usable Mapsource version is 6.16.3. Mapsource versions 6.14 to 6.15.6 are complete junk. Also note that Mapsource versions prior to 6.16.1 do not show all ways and pathes so they are not really usable.
Problems - Help - Tutorials
Beginners Guide can be found here: get started with openmtbmaps
Install Basecamp/Mapsource: tutorials/install-mapsource/
Install the Openmtbmap on your PC: tutorials/install/ explains the options of the installer.
Send Maps to GPS with Mapsource/Basecmap: tutorials/send-maps-to-your-gps/mapsource/ I recommend to allways send maps to an external data card and not internal memory. (this way if something goes wrong, or maps would be damaged you run less danger of wrecking your GPS).
Alternative: Use create_gmapsupp.img.bat and place the newly created gmapsupp.img into /garmin folder on your GPS. Address search cannot be included this way. If you use create_gmapsupp.img_with_mkgmap address search will be enabled, but you need depending on the size of the map quite a lot of free RAM.
Send maps to GPS with mkgmap (for Unix users): tutorials/send-maps-to-your-gps/mkgmap/
Basecamp Error / debug Mapsource: There is a problem with the MapSource / Basecamp registry. Please re-install Mapsource and start again Solve with Mapsource Fix Or with Mapset Toolkit
Please also read the FAQ
Change Layout and Contrast of the maps
On installation you can choose the layout of the maps. Traditional layout is for Qlandkarte GT, Mapsource and Basecamp and offers a good layout and design for big screens. On the GPS thin, classic and wide or easy or hiking offer high contrast for best orientation while riding your bike or hiking.
In order to change the layout - simply run openmtbmap_country_change_layout.exe (this is also linked in your Start --> Programs Folder for each map). This also enables you to quickly change the layout before sending maps to your GPS device, and then quickly change it back for better planning on your desktop.
You can adapt the .TYP-files, which are responsible for the layout - and therefore the map colours, to your liking by using http://maptk.de/. Do not use http://ati.land.cz/gps/typdecomp/editor.cgi because it is not fully compatible and may corrupt the .TYP-file.
Compatibility - Unicode vs Non Unicode (cannot authenticate maps)
Newer Garmin devices cannot use free unicode maps (except if you hack the firmware) - usually a "cannot authenticate maps" message which show on boot. The following Garmin outdoor devices are affected:
- All Garmin devices presented 2016 or newer
- Edge 1000
- Epix
- Etrex 20x / 30x (not "etrex 30")
- Etrex Touch 25/35
- GPS Maps 64 series
- Montana 610, 680
- Oregon 700,750
- Some recent Nuvi devices - as well as some super old devices that do not support Unicode. (E.g. Garmin Vista C, GPS Maps 60 C)
you will need to download the "Non Unicode" version of the map. Only maps of regions where several different scripts are used - are in unicode. I've listed the non unicode maps however also unter the unicode header for convenience (actually only maps with (unicode ) following their name are actually in unicode.
Also english version of maps is only available for countries/regions not using latin only.
Garmin Edge x30 or newer
Garmin introduced a completly broken high contrast mode - that washes out the colors of the maps. Either disable the high contrast mode on the map visibility section. Or delete the \Garmin\MapThemes\Mountain.kmtf (sometimes also called \Garmin\MapThemes\Mountains.kmtf ) file (back it up if you think you ever want to use that mode.
Language and Codepage
Default - Local Language Unicode. All labels / street names are exactly like in the name tag of OSM. Note for any country that uses latin - the default will be latin1 and the options below are not available. An exception is the South America continent map that is additionally available in English Non Unicode. For USA/Canada this is also the only option. For European countries using latin if you want the English version - you can use the European continent map that is available in English versions.
English Unicode: If available in OSM - English or other European language translation is used. If no translation is available in OSM, the local name tag is used.
Local Language Non Unicode: Same as default but instead of Unicode the local codepage is used. So some characters may need to be transcribed automatically in creation. Codepage is always the local default codepage.
English Language Non Unicode (always latin1): If available English or other European language translation from OSM is used. If not names are transcribed to Latin.
Current Issues
The address search is not working consistently. Most problems are due to inconsistent data structures in OSM address data.
- General: Autorouting over longer distances on GPS works only with Via Points. Solve with WinGDB: plan-routes-efficiently
- Autorouting needs attributes like tracktype, bicycle routes, mtb:scale, sac_scale, mtb routes and others to work well. So keep care to enter those details into OSM. (not all are needed, but enough for me to guesstimate wether a street is cyclefriendly/mtbriendly or not).
- Note sometimes sea/lakes are missing/emtpy. This is not an issue, but currently not differently possible. It is usually a problem in OSM data.
Notice on Updating Maps
If you want to be notified by email on map updates please go to the frontpage and enter your email address in the subscribe field of the left sidebar. You only get an e-mail when there are changes besides a simple map data update. Map updates are usually every Thursday night / Friday morning. You can look at the server to see the date of map upload. To update the maps, simply run a newer .exe Download.
Overlapping maps in border regions
While you can join maps of different countries, routing over the boundary is a bit shaky, and you will have one map overlaying the other with white background. As long as mkgmap cannot create randomly shaped overview maps (currently only rectangles), this problem is not solvable. There is however the possibility to download a Europe map, which will be updated every 4-6 weeks. Get Europe Map here (donation needed): https://openmtbmap.org/support/europe-map/
Velomap and Openmtbmap of the same Country -- Problems
If you install an Openmtbmap and a VeloMap of the same country with contourlines as separate download, you should only send the contourlines once (meaning with either Openmtmbap or Velomap of the country). Else you GPS might not show the maps, or worse not even start until maps are deleted. There are several possibilities.
a) Install both maps without contourlines and contourlines separately (install separate contourlines only map option in installer). You have not trouble.
b) be careful here: Select the map as usual in Basecamp/Mapinstall, then go to the list of the selected tiles ready to be sent to the GPS, scroll down to the bottom, and unselect the contourlines only tiles from the list.
-- This is not a problem with countries where contourlines are fully integrated like Germany, Alps, Austria,......
Feedback
Please comment if you like theese maps or even better tell other people about them (forums, blog about it, twitter, etc…) In case maps break Basecamp or don't work - please write exactly which downloads don't work and the time of download as well as your OS and Basecamp version.. Please also look here https://openmtbmap.org/download/#problems-help-tutorials or in the FAQ
Map Downloads by GWDG
Premium maps are only downloadable for people who have a openmtbmap membership. For last map update: please look at recent posts for changes - usually maps are updated at least every 7 days with updates on Thursday/Friday.
To check the last update time for a map - just click onto the MD5 link.
Contourlines Premium Downloads
Most countries, especially the popular ones, have the 20m contourlines already integrated. However for several countries the contourlines are rather large (rule of thumb if contourlines have more data than the maps) and I integrate them, but you need to download them separately (once). The installer will ask for the contourlines file as soon as you activate the checkbox to integrate the contourlines in the installer. You do not need to extract the contourlines - this will be done by the installer (and is only needed once. On updates you don't need to redo it).
In general it is fine to only update the map, as I try to change the contourlines as seldom as possible. The 10m contourlines always have to be downloaded once - the installer will ask for the 7z 10m download and unpack and install them for you if you activate the 10m contourlines checkbox.
If you get the message - "cannot authenticate maps" or you have you have one of the following devices:
- All Garmin devices presented 2016 or newer
- Edge 1000
- Epix
- Etrex 20x / 30x (not "etrex 30")
- Etrex Touch 25/35
- GPS Maps 64 series
- Montana 610, 680
- Oregon 700,750
- Some recent Nuvi devices - as well as some super old devices that do not support Unicode. (E.g. Garmin Vista C, GPS Maps 60 C)
you will need to download the "non unicode" version of the map instead of the unicode version. So get the map from the "non unicode openmtbmap" tab instead. Only maps of regions where several different scripts are used - are in unicode. If Latin is the predominant script - then of course no unicode map is offered. If your device can display Unicode maps - then of course get the standard version - meaning Unicode if needed for the country.
Note1: if you install the non Unicode version of a map - you will overwrite the Unicode map. You can only have either or installed.
Note2: The contourlines are identical for openmtbmap/velomap and unicode or non unicode. You only need to download them once. On updates it's enough to re-download and reinstall the map installer.
Note3:Here only those countries are listed - where the standard download is Unicode. If you don't find a country here - look at the standard downloads.
Note4 - local language maps of: Sri-Lanka, Nepal and Cambodia are in latin1 - so the local language maps are not very useful. There is no ANSI Codepage available (besides Unicode) that would support the script/garmin units. Israel-Palestine map is in hebrew (so the Palestine area is not useful). Afghanistan codepage is for Dari - Pashto is not supported outside of Unicode.
Language and Codepage
Default - Local Language Unicode. All labels / street names are exactly like in the name tag of OSM. Note for any country that uses latin - the default will be latin1 and the options below are not available. An exception is the South America continent map that is additionally available in English Non Unicode. For USA/Canada this is also the only option. For European countries using latin if you want the English version - you can use the European continent map that is available in English versions.
English Unicode: If available in OSM - English or other European language translation is used. If no translation is available in OSM, the local name tag is used.
Local Language Non Unicode: Same as default but instead of Unicode the local codepage is used. So some characters may need to be transcribed automatically in creation. Codepage is always the local default codepage.
English Language Non Unicode (always latin1): If available English or other European language translation from OSM is used. If not names are transcribed to Latin.
Openmtbmap (and VeloMap) maps Premium Download in Mac OSx format (gmap)
I have decided to make available all openmtbmaps and velomaps also in gmap format for Mac OSX. Please get them from here: https://openmtbmap.org/download/macosx/
For VeloMap downloads please go here: https://openmtbmap.org/download/velomap/
(note if you are not a OpenMTBMap member - please directly go to www.velomap.org/
Hi Felix
Can you look at the contour lines for Lord Howe Island. Mount Gower (S31.58820 E159.07371) is officially 875 m but the openmtbmap Australia-Oceania contour lines show it about 360 m. Attached is a scan of part of an Australian government topo map to compare to.
I looked at some other Australia government mainland topo maps and New Zealand government maps (https://www.linz.govt.nz/land/maps/topographic-maps) and they seem generally to match openmtb maps so maybe it’s an issue specific to Lord Howe Island.
well that looks like there was a data hole in the DEM data – Nothing I can fix. There are a few places like this worldwide – there is only SRTM data available. Look here it is the same rubbish: https://opentopomap.org/#map=17/-31.58817/159.07387
Just the data to fill the hole seems to be a different source. This place is missing in ALOS World 3D – as it is too small island. Then if SRTM data there is broken – results will be very problematic. As ALOS World 3D used SRTM to fill small outlying islands. Opentopomap uses viewfinderpanoramas here – which is also voidfilled with some rubbish. Both are way way too far of so I guess there is no free source of decent quality data.
Hallo, leider kann ich die Datei Europe Contours nicht runterladen. Die beiden anderen Dateien haben den Zeitstempel 06.06.2021, Europe Contours von 10.05.2021. Hat das mit dem “Traffic” zu tun?
Kann man POI’s in die Karten Dateien einfügen, z.B. die POI’s vom E1?
Mit freundlichen Grüßen
Klaus Berning
In die Karten nicht – aber du kannst POI oder Tracks in Basecamp sowie am GPS Gerät anzeigen lassen.
Hallo Felix,
liegt es an mir, Basecamp oder ist das Autorouting kaputt? Alle Routen die ich im Basecamp (4.6.2 und 4.7.4) erstelle, meiden Autobahnen wie die Pest. Älteste Karte die ich noch installiert hatte war vom 13.05.21, probiert habe ich Berlin, Brandenburg, Sachsen und China. Hier mal ein Screenshot von einer extrem kurzen Route am Berliner Ring.
Funktioniert genau so wie es soll. Die Karten sind nicht für PKW oder Motorrad gedacht! Lies dir das Autorouting Tutorial durch.
Danke. Sorry für die unnötige Frage, bin neu, hab mir versucht alles durchzulesen, bin aber wohl irgendwo in den Links verloren gegangen.
PS ist es gewollt dass man pro Jahr weniger bezahlt wenn man sein Abo jetzt kündigt und dann neu verlängert? Wenn man ne Karte runtergeladen hat und installiert hat werden einem noch 15€+13€ jedes weitere Jahr angeboten
Ui nein, ich konnte nur die neuen Preise nicht direkt komplett ersetzen, da ich per email noch für Verlängerung die alten Preise angeboten hatte – und dass dann nicht direkt ändern konnte. Ich habe vergessen im Installer den Link auf den neuen Link zu setzen (in 4 Tagen sind dann nur noch die neuen Preise möglich).
Dentro del listado de mapas, hay alguno de Isla Reunión. Gracias
Yes – look down for the French DOM TOM – there is Reunion
Hi. I’m a new subscriber here, and I have troubles with the contour lines.
One thing is that the dotted lines for the contours are very thin and nearly impossible to see on my GPSmap 66i. I’m a hiker not an MTB-er, and in areas with lots of terrain (such as here in Norway) it’s rather important to know where you want to go. And even on the desktop profile, those thin dotted lines seem to be the norm.
Could you perhaps modify (or make a new profile) for the more high-resolution GPS-es
And while you’re at it, could you make such a profile more like a normal map where the terrain and its features are more visible, and it’s not just the paths taht come to the front? We hikers are not all running blindly after the trail, the reason I started to use the OSM maps at all is it has better coverage of local, small paths than even Garmin’s most detailed maps, and for Norway they are detailed indeed, and I often go to explore the terrain just for the experience.
Another thing is the contour lines seem to be simplified, at least for Norway’s case. Looking at Openstreetmap, they have 10 meter contour lines. While your maps offer just 20 meters. They seem rougher, too. Looking at Osmand, the compressed contour lines package for Norway is at 976 Mb while yours is at 229. And while I understand that a gigabyte (or more, really) of contour lines is overload for many, I want the full package! If I could get hold of and use the 5 meter contours (and perhaps even the markings) they use for orienteering maps, I’d be happy.
I’m fine if it is for subscribers only. As this is the kind of things you can charge for.
And oh, a related question:
Could it be possible to install your maps on the SD card of these newer GPS-es? Put in a 16 GB card, and there’s much better space.
of course – I always recommend to install to SD card and not to internal memory – because if you f*ck up something – just take the sd out and boot instead of needing to resort to more difficult solutions.
Hi – if you use the gmapsupp.img downloads (and not on newest osx without 32bit support) you can find a script in the contourlines gmapsupp.img download with which you can change the appearance from thin to thick or default. I cannot offer this for the installable maps.
2. Which layout are you using. And what do you mean with terrain. Areas or topographic features displayed as lines?
3. I’m right now preparing also 10m lines – but actually in mountains I feel 20m are far superior to 10m lines. And 5m contourlines is just pure rubbish so to say – even more if the underlying data is not good. For Norway I think there exist full LIDAR coverage – so yes 5m lines would be possible but absolute useless in terms of use. You can see the actual altitude in the popup/display anyhow – and in flat areas that will be much more exact than 5m lines.
And yes I do likely simplify the lines a bit more – that is because Garmin GPS don’t have the biggest processor power – so I have to smoothen them a tiny bit more. On the other hand Mapsforge format is way worse on compression vs garmin map format (on the other hand garmin map format is not useful if you zoom in closer than 30-40m – as it has inbuilt accuracy of about 7-8m per dot in Norway (depends a bit how far away from equator). So everything needs to be moved to that 6-7m raster. That’s good enough for most usecases – mainly makes buildings zoomed in close a bit ugly however.
I guess it depends on where you are. Not all of Norway is steep mountains. Here in the southeast, for example, we have lots of small hills and hillocks. So keeping them apart and knowing the terrain isn’t always easy.
I’m not asking you to make 5 meter contours, I’m just saying that on my 1:10000 orienteering maps it makes a lot of sense. (See attached image.) But I guess there’s a limitation on the GPS software that says “either we show contour lines or we don’t” instead of progressively going into further detail as you zoom in. I doubt you can do much with that, so yes you’ll have to set the limit somewhere.
And yes, I agree the GPS unit can be hard to draw sometimes. But I have the Garmin Topo Norway Premium map (version 3 for region 2 -Southeasst), and they manage it fine there. I just don’t want to switch maps back and forth all the time, just because I have the pathways on one map and the terrain on another.
Well I’m very sceptical about the use of 5m equidistance – I don’t see why it would matter (at least as long as you stay on trails – if you go off trails then yes) – because things like a big rock would not be affected anyhow and invisible on the contourlines. 10m will come but only as add on – not integrated.
Again, I’m not asking for 5 meter contours. I’m just using it as an argument for 10 meter contours. Saying “all things considered, 10 meters isn’t all that extreme”. While I agree 5 meters is a more rarely needed use case.
But again, orienteering isn’t all that rare as a sport. And I’m sure there’s more like me, who find all those roads and paths somewhat boring. They’re okay if you want to get somewhere, but not as a place to explore and experience nature it’s fullest. And that’s what I’m there for, not to stress about with some “task”. (There’s more than enough of that elsewhere.)
So again, I’m just advocating a slightly different view at maps: Where the terrain is at least as important as those paths.
I tried using your “hiking map” layout but I find it of little use as it is so focused on the paths and little else. So I don’t know what to choose. Do you have a suggestion?
Well the terrain is much more than the altitude lines. The problem is there is not that much terrain information in openstreetmap. Much less than 25m maps of alpine clubs or military/orienteering maps. So right now in most areas OSM data will not be that sufficient. But as I said – in a couple of weeks I will offer 10m lines additionally as download worldwide (though it will only make sense where there is LIDAR data or very mellow / rather flat terrain).
Okay, that’s good then. Thank you for that. Now I just need to find out how to change the profile for these maps…
I’ll guess I’ll ask for documentation if I get stuck.
The 10m contourlines are online for gmapsupp.img format. The osx and windows maps (you cannot integrate them into the normal maps without losing address search) are uploaded but I need 2 more days to link all of them.
For norway change the gmapsupp.img link to: 10m/windows/windows_contours_norway10m.7z repectively 10m/osx/gmapi_contours_norway10m.7z
Thank you so much! I have now working, good contour lines.
And for your enjoyment, I think I’d share with you an orienteering map I got hold of yesterday. With 2 meters contour lines! 🙂
At 1:3000 scale it’s quite detailed, sure enough. But at any rate.
Hi Harald, I updated the 10m contourlines another time – because in some very steep regions they did not look nice.
You could give me your opinion on:
a) https://openmtbmap.org/?s2member_file_download=10m/windows/windows_contours_norway10m.7z
b) https://openmtbmap.org/?s2member_file_download=10ml/windows/windows_contours_norway10ml.7z
Do you think the quite big increase in size for the 10m vs 10ml is worth it for you? Also the 20m contourlines are better now and will be used from the next update or second next onwards. My server needs about 10 days to compile all those contourlines newly.
Ich habe es nun nochmal erneut probiert. Kleinere Bereiche gehen meistens. In jedem Fall erfolgt ein Abbruch, wenn die Karte größer als 4 GB wird – meist kurz nach dem Start der Indexberechnung für das zweite File.
Wenn man unter 4 GB bleibt ist es mir nicht gelungen einen Bereich der Karte zu identifizieren, der sicher zum Abbruch führt. Die Auswahl mit der Maus ist ja sehr grob, und man kann nur schwer abschätzen welchen Bereich man erwischt. Oder gibt es bei Mapinstall einen versteckten Trick, um dort die Auswahl aus einem File einzulesen?
Ups, das sollte eigentlich eine Antwort auf https://openmtbmap.org/download/odbl/comment-page-9/#comment-25374
sein:
extremecarver
Montag, der 15. März 2021 at 03:38
Wenn du per MapInstall nur einen kleinen Bereich sendest, geht es dann? Oder bricht MapInstall generell ab?
Aber es gab auch Abbrüche bei unter 4GB? Dann könnte eine Kachel defekt sein – ich render Europa gerade neu – wird in 2 Tagen online sein (inklusive neuer Höhenlinien). Du kannst es dann mit der neuen Europakarte nochmal probieren. Dass eine Kachel kaputt ist – ist sehr selten – bei ganz Europa halt wahrscheinlicher wie bei einer Länderkarte – sollte aber trotzdem so selten sein – dass es nur 1-2mal pro Jahr bei der Europakarte auftritt.
Gibt es denn eine Möglichkeit bei MapInstall ein Logging einzuschalten, damit man erfährt bei welcher Kachel Probleme bestehen?
Kann ich eigentlich eine erzeugte Karte (gmapsupp.img) in Basecamp einzubinden, um bequem zu sehen wo die Ränder der Karte liegen?
Nein – es ist auch äußerst selten. Vor allem fast auzuschließen dass zwei Kacheln in der Europakarte kaputt sind. Wenn es also etwa einmal ganz im Norden, einmal von Süden aus jeweils nicht über 4GB geht – liegt das Problem eher woanders (versuch mal eine andere Karte wie Asien oder Afrika mit Höhenlinien ob es über 4GB geht).
Zweitens – dafür müsstest du mit gmaptool die das Sichtbarkeit Bit ändern – Standardmäßig werden nur die gmapsupp.img Karten in Basecamp angezeigt, aber nicht jene die man mit Mapsource oder MapInstall sendet.
Mit Mapsource lässt sich gut sehen was man genau sendet (aber halt 4GB Limit).
Die neue Europakarte braucht noch gut 30 Stunden – da für Slowakei und Sachsen-Anhalt neue Höhendaten verfügbar sind – und ich die Höhenlinien nur selten updaten möchte – konnte ich das letzte Update nicht veröffentlichen.
Vor dem Download sollte immer die bevorzugte Variante (Thin…) zu wählen sein. Das wird aber nicht immer angeboten. Wenn die Karte ausgesucht worden ist, geht der Download schon mal sofort los. Wie komme ich in diesem Fall an meine gewünschte Auswahl?
Das ist absolut unmöglich – dann müsste ich ja alle Versionen extra zum download anbieten. Wenn du die Windows Installer Karten meinst – da kannst du ja beim installieren die Version auswählen. Du kannst auch nachher ohne neuinstallieren die change_layout…. .exe ausführen um schnell das Layout zu ändern.
Bei den gmapsupp.img Karten kannst du unter Windows und Linux einfach das batch/bash file aufrufen um das Layout zu ändern – nur am Mac geht das nicht mehr – da gmaptool keine 64 bit Version hat.
I have the 7.12.2020 version of the italy map that havn’t any problem.
about this last version (11.02.2021) i am not able to install it, neither directly to etrex touch 35 (gmapsupp version) nor omtb version from basecamp.
Please help me to solve the problem
many thanks
Hi gianfranco, what is your problem exactly? How do you try to send the map – and what error message do you get?
hier das Bild vom Edge 1030+ mit den breiten weißen Wanderwegen :d
Dürfte sicherlich der Hochkontrastmodus sein. Nimm ein Profil ohne mountain, oder mtb oder bike im Namen Hoher Kontrast muss ausgeschaltet werden: https://www8.garmin.com/manuals/webhelp/edge1000/DE-DE/GUID-76111736-B1C8-4EA0-91E1-72B53C52F71A.html
Auch mit “Kartensichtbarkeit: Automatisch” auf dem Edge verschwinden die breiten weißen Streifen nicht. Muss ich das Aktivitätsprofil im Basecamp ändern (aktuell und die Karten neu auf den Edge befördern, meinst du das?
Nur Aktivitätsprofil umbenennen sollte reichen. Es darf nicht mountain mtb, bike usw im Namen vorkommmen. Bzw wähle auch mal anderen Autorutingmodus nur zum testen. Karten brauchst du nicht neu senden. Es sollte aber aus sein, und nicht hoher Kontrast oder automatisch!
Eine Veränderung des “Standarttyp der Tour” hat die Lösung gebracht. Benutze nun Kartensichtbarkeit: Benutzerdefiniert. Meine Fahrprofile heißen (dirt) und (gravel) – daran sollte es vorher auch nicht nicht gelegen haben. Nun alles bestens, vielen Dank!