Contents
- 1 About the Autorouting
- 2 Usage Instructions - For All Programs / GPS.
- 3 New Generation - Firmwares from 2016 onwards - Basecamp 4.6 or newer:
- 4 Mid Generation (Basecamp 3.3 - 4.5 or older Garmin GPS with first version of Activity Routing Support)
- 5 Old Generation (Mapsource, Garmin GPS without Activity Routing Support)
- 6 Faster Time vs Shorter Distance
- 7 Road Type Avoidances
- 8 Feature Type Avoidances:
- 9 General Tips and Advices - e.g. Route Calculation Fails
About the Autorouting
The maps offered here are to be used for cycling, mtbiking and hiking. There is a general preference to route you over trails and cycleways. Streets have lower priority. However note that the GPS will not take huge detours on trails to avoid a primary or secondary highway - even though they have the lowest priority. Autorouting with my maps is unusable with a motorcar. Use another Openstreetmap implementation instead if you intend to use you car. The maps can be used for autorouting on a racing bicycle - however the Velomaps are better for racing bicycles..
Downhill preference on difficult trails
All trails from which I can assume that they are usable downhill only will have much higher priority in the downhill direction, uphill they will only be chosen if long detours are unavoidable otherwise. This means uphill on relatively easy trail, downhill much more technical. In order for this to work you need to use the incline tag correctly. I have rules setup to catch more or less any value, be it incline=up or incline=down, incline=(-)??% or also wrong tags like incline=positive or incline=-. Any way with mtb:scale:uphill=4 or mtb:scale:uphill=5 (see mtb:scale for explication of mtb:scale:uphill) will be avoided on uphill. Therefore please add mtb:scale:uphill and incline tags to all your favourite trails that are too difficult for uphill. mtb:scale:uphill=3 will be considered oneway if incline>15% or incline<-15%.
It does not matter whether the way itself in the OSM database points uphill or downhill. I reverse ways pointing uphill when rendering the maps. This is of course only possible if the incline tag exists on the way.
Usage Instructions - For All Programs / GPS.
Note that all may behave different. In principle we have the following classes:
New Generation - Basecamp v4.6 - 4.8, Oregon 700/750, GPSMaps 64 current firmware/66 series, Edge 830/1030, Edge 820 with current firmware
New Generation - Firmwares from 2016 onwards - Basecamp 4.6 or newer:
Note that long distance routing does not work reliably with car based vehicles anymore - except if you block residential roads.
Usually the best setting is now to use bicycle, Tour cycling or mountainbike or, shorter distance, and as avoidances only toll road and or unpaved roads based on preference for difficult or less difficult trails.
Then there are several Bicycling, Mountainbiking, Tour Cycling options. With the OpenMTBMap - if you configure the avoidances the same, they all route alike. They are now the best option for longer distance routing.
ATV and Dirt Biking Route pretty similar - Dirt Biking gives the best routes and can route over shorter distances (<=10km by air without any intermediary routing points). IUt usually fails on longer distances. Also Dirt Biking is not available on most GPS devices - while ATV is.
Hiking, Walking, Mountaineering also all behave alike --> The results are okay for short distances with the OpenMTBMap - over long distances however it seems to use the worst streets/ways for cycling (mainly primary and secondary roads).
Motocar/Motorcycle
not suitable for longer distances. Very short distances route pretty well. In general ATV or dirt biking are better however.
Mid Generation - Basecamp v3.3 to v4.5. Dakota, Oregon 600/650, Montana, GPSMaps 62 series with newest Firmware, 64 with older firmwares, edge 520/820 with older firmwares
Mid Generation (Basecamp 3.3 - 4.5 or older Garmin GPS with first version of Activity Routing Support)
Basecamp v3.3 to 4.5 behave quite differently to previous versions, or Mapsource, and also on the internal side of how it checks the maps, and what it does is very different. So Let's have a look on what you can set. In Principle (except for etrex 10/20/30) the GPS devices behave very similar to Basecamp v4.
In the top left, you can set the Profile. Currently Automotive is activated.
Automotive and Motorcycling have been the method of choice for Basecamp v3 and Mapsource - but are not really usable except for short distances with OpenMTBMaps in Basecamp v4 and newer anymore! On etrex and 62s series - where you cannot choose ATV as routing mode - use car or bicycle.
Then there are several Bicycling, Mountainbiking, Group Cycling (and maybe more in future) options. With the Openmtbmap - if you configure the avoidances the same, they all route alike. These modes are okay, if you don't mind to find yourself quite often on asphalt and streets. They do tend to often use bigger streets with newer firmwares though.
ATV and Dirt Biking Route pretty similar - Dirt Biking gives the best routes and can route over very long distances (>100km by air without any intermediary routing points). However Dirt Biking is not available on most GPS devices - while ATV is (e.g. on most Oregon/Montana and maybe Dakota/64s?).
Therefore you can chose between ATV - which is the best choice if you want to transfer the route itself to your new generation device - and Dirt Biking, which you can use for best routes that you copy via right-click advanced to a track - and send the track to your device (except of course if your device supports Dirt Biking profile - then go for it in any case).
Hiking, Walking, Mountaineering also all behave alike --> The results are okay for short distances with the Openmtbmaps - over long distances however it seems to use the worst streets/ways for cycling (mainly primary and secondary roads). Difficult Via Ferratas are only available in this mode!
So what of the above makes sense?
For CrossCountry: Use profile ATV/Dirt Biking, avoid toll roads, and avoid unpaved roads. Use shorter time.
For AllMountain/Enduro: Use profile ATV/Dirt Biking, avoid toll roads. Use shorter time.
For Vertriding / Technical Enduro or whatever you call it and Hiking: Use profile ATV/Dirt Biking, don't avoid any roads/features. Maybe avoid residential roads. Use shorter distance.
Hiking/Mountaineering with Via Ferrata included: Use Mountaineering mode - without any avoidance.
-- As the map data in Openstreetmap is everywhere different, and also the offer of good ways/routes for mtbiking differs a lot, just try around a bit in Basecamp, to find out what happens. In General Basecamp and your GPS will route similar over short distances.
Old Generation - Mapsource, Basecamp v1 & v2 & v3.1, v3.2, All Garmin GPS WITHOUT Activity Routing (etrex vista/legend hcx or older, edge 705, GPS Maps 60 series; AND Dakota, first generation Oregon, Montana,GPSMaps 62 series with older Firmwares )
Old Generation (Mapsource, Garmin GPS without Activity Routing Support)
Transport Modes
Car/Motorcycle = Works well on shorter distances - might produce long detours.
Taxi = behaves like Car/Motorcycle.
Bus / Truck = Avoids turning. Hence don't use it.
Pedestrian No good autorouting over longer distances, will usually give quite direct vias - does not respect oneways.
Bicycle = Works well in combination with "shorter distance". Is good for calculating longer distances on you GPS if you get "out of memory" errors.
Only For Mapsource - Note the slider called "Road Selection". The more towards the right (prefer highways) you push it, the more you will be routed over great trails, hiking routes, mtb routes or cyclroutes. Never move it to the left. If you feel that cycleroutes, hiking routes, and mtb routes are favored too much, better use transport mode: bicycle, or use "shorter distance".
Only Available on (some) old Generation Garmin GPS Devices - Route Calculation Method: Per default I would advise to use "quick". However if you get "out of memory" errors, go for "better route". On best route calculation is able to get you to pretty remote places, however you might need to wait up to 10 minutes or longer until the calculation is actually finished.
Route Calculation Percentage value - The indicator has a bug on all units. It is only correct if jumping by several percent. However if it only increases by one percent per second, then it will reach 100% long before it has calculated the route. Hence when it gets stuck at 100%, there is still a good chance that the route can actually be calculated correctly. Using "better route" or "best route" for route calculation method, this often means waiting 3-5minutes until the route is actually calculated.
So what of the above makes sense?
For CrossCountry: Use profile motorcar, avoid toll roads, and avoid unpaved roads. Use shorter time.
For AllMountain/Enduro: Use profile motorcar, avoid toll roads. Use shorter time.
For Vertriding / Technical Enduro / Hiking or whatever you call it: Use profile motorcar or bicycle, don't avoid any roads/features. Use shorter distance.
Hiking/Mountaineering with Via Ferrata included: Use Pedestrian mode - without any avoidance.
For the Old Generation, there is still one Distinction. In Mapsource under options/autorouting you have a slider to prefer small roads (left side) to highways (right side). If you move this slider to the right hand side, better suited ways/streets will be preferred. On the GPS such a setting does not exist, but the GPS is anyhow more strict on choosing well suited roads. On the other hand the "route calculation method" is only available on the GPS.
Faster Time vs Shorter Distance
With my maps shorter distance already tries to route over nice ways. If you use "faster time" - especially in combination with car/motorcycle or Automotive mode, then an even higher preference for "nice" ways will be used and routes tend to be longer (more detours) overall. With my maps there is no such routing as really shortest distance (it is actually impossible to do really have autorouting on Garmin GPS find the shortest route over long distances). If you use shorter distance the route will be in general straighter and with less detours - also longer overall distances will be calculated without crashing (error notice, no actual crash).
Estimated Arrival time
Garmin is not supporting proper Arrival times for Cycling. Using bicycle the estimated arrival times using "faster time" are simply calculated by averaging 18km/h - hence not very useful. Using "shorter distance" the arrival time often becomes really bogus. Using Automotive, Car/Motorcycle or other modes, the times will be far too short. Also elevation (so climbs or downhills) are not taken into the calculation. This is the same for Garmins own maps.
Road Type Avoidances
NEVER Tick "Avoid Highways" - It will block the best ways. On my maps, shared use pathes and cycleways are encoded for the GPS as highways. Real highways or big streets where cycling is not allowed are not routable anyhow with the Openmtbmaps (so no need to avoid them).
Interstates: don't avoid them, you'll miss the nicest trails.
Major Highways: If you tick it you will avoid streets that are nice for cycling, cycleways, cyclepaths, and so on. Well as you want to cycle with this map, I don't think you ever want to tick that box.
State Highways: Don't tick it. Most ways in the Openmtbmap would be blocked.
Residential Roads: If you tick it, then residential streets, primaries and secondaries are blocked as well as trails that are no fun to bike. May work, but don't bet on it (too often some very short residential street or bad quality trail is necessary to get from A to B without crazy alternations.
Unpaved roads: If you are a XC biker, then yes, try activating it. All ways with mtb:scale=1 or higher are blocked, as well as sac_scale = T2 or higher.
Feature Type Avoidances:
Toll roads Avoid ways, that are only for vertriders. Also avoids biking against the allowed traffic direction, blocks uphills you have to carry your bike (if mtb:scale:uphilll and incline are set properly), or ways were you are not allowed to bike.
Avoid Ferries - Avoids ferries, cablecars, gondolas and mixed lifts.
U-Turns avoids any turn over 120° - best not use, because it will destroy sensible autorouting.
Cable Cars: Does not matter with Openmtbmaps (or more correctly, does not work, best don't tick anyhow).
Narrow Trails: Does not matter with Openmtbmaps
Carpool lanes: Avoids all ways where cycling is forbidden (and no more). (is activated by default in all profiles but car/motorcycle).
Date and Time Closures - it is currently not possible with mkgmap to produce maps that react to this setting.
Climbing Paths: Does not matter with Openmtbmaps.
Roundabouts: Well does exactly what it says. I advice you to never tick this box, else roundabouts are avoided, and then routing likely won't work well.
General Tips and Advices - e.g. Route Calculation Fails
If Routing fails and you need to get somewhere without being able to set via points, you can try with “shorter distance” caculation which should autoroute even through heavily mapped cities (actually the better a region is mapped, without sufficient bicycle/mtb routes the more difficult it is for the routing engine to get over longer distances, Enabling “shorter distance” instead of “Faster Time” gets you to your destination quite well (though then also big streets are chosen quite often). Due to the way the maps are setup, setting your GPS to “shorter distance” should generate routes that are much quicker. “Faster Time” calculates nicer routes, but will take much more time. It it fails with "out of memory" error, you can also change the route calculation method. Another possibility to to deactivate "avoid unpaved roads". Often some very small patches of unpaved roads will hinder the routing to work well. Then just try to cycle a bit nearer using the route, and after a few kilometers (or better say 20 turns) click on recalculate after reactivating avoid unpaved roads.
Attention - Same Map.
You need to plan the routes with the identical map in Basecamp (same country, same date (that is paramount) that you use on your GPS device. Unicode/Non Unicode does not matter however. If you created the route with an older map - recalculate it in Basecamp first - then send it again to your GPS device. Also if you update maps on your device - it will often lead to errors if you try to use an older route (does not have to - but the more months between the map used for planning, and the map used with the route on your device - the more likely you get route calculation errors). To correct this - recalculate the routes in Basecamp with the new map - and send them again to your device. If the route now does not work in Basecamp anymore - its quick to notice. Maybe you will need to move some via points.
Routing does not work over long distances:
There are two main causes for bad routing: 1. non connected streets in OSM. 2. Not enough streets suitable for cycling - or tracks and pathes that are not tagged with tracktype/smoothness so that they are blocked when using "avoid unpaved roads". You should be able to route for 15km minimum to about 70-80km maximum without needing to route over via points on old GPS. Using Mapsource or newer GPS like Oregon or Dakota you can route over much longer distances. Very very long routes will never work because the routing engine of Garmin is not strong enough (and maybe there are still some improvements to be made in mkgmap). This is because Garmin algorithm likes to go straight for long time (like on a motorway) - routes suitable for cycling or mountainbiking make turns, have many intersections and are not so easy to be routed on. Because I don't want the maps to send you onto big roads, routing will not work over very long distances. For autorouting inside your car there are better maps available. Maps offered here are supposed to give you the best routing possible on Garmin GPS for mountainbiking / hiking or cycling. Solution: Insert additional via-points.
How to overcome problems when routing over long distances:
Routing without via points over large distances (i.e. 50-100km) will often not work, even though by setting via points you will find a way. The better the OSM Coverage the greater the distance you can cover with the autoroute function. For in car use I recommend either Garmin City Navigator maps if you have the doll to shell out, or the excellent Autoroutable maps by Lambertus: http://garmin.openstreetmap.nl/ The maps offered here are to be used for cycling, commuting via bicycle and roadbiking. I have structured the Routing Preferences so that small streets are preferred over larger streets. If you want to plan you're routes in Mapsource and be sure that recalculation works on GPS I recommend you to read through here: plan-routes-efficiently following this tutorial and using wingdb you can easily create routes via pc that go over 200-300km. I advise however to make a new route for each day.
Vielleicht hilft das ja jemandem: Ich habe gerade stundenlang versucht auf einem Edge 830 (v 9.30, 9.40) eine 6km lange Strecke mit der omtb Alps routen zu lassen. (Fast – s.u.) egal mit welchen Routingeinstellungen (Fahrzeugtyp, Vermeidungen etc.) wurde ich IMMER auf Hauptstraßen geroutet, obwohl direkt daneben ein Radweg verläuft. Unterwegs wurde ich auch immer aufgefordert, auf die Hauptstraße zu wechseln.
Ich habe dann später in Basecamp (Mac) versucht, das ganze nachzuvollziehen, und aufgrund der schnelleren Testmöglichkeiten hab ich’s dann gefunden:
– Bei Routing “Distanz minimieren” werde ich sowohl in Basecamp, als auch auf dem Edge 830 auf die Autostraßen geroutet.
– Bei Routing “Zeit minimieren” werde ich dagegen sowohl in Basecamp, als auch auf dem Edge 830 wie erwartet (und erhofft) auf Radwege und vernünftige Strecke abseits der Hauptstraße geroutet.
Zusammenfassung: Wenn ihr Probleme mit dem in-device, ad-hoc-Routing in eurem Garmin Edge 830 habt, es auf jeden Fall noch mit der Option “Zeit minimieren” probieren, welche man hier findet:
[Edge 830] = > Aktivitätsprofile > [gewünschtes Profil] > Navigation > Routing > Rechenmethode > Zeit minimieren
Vielleicht hilft das ja jemandem.
Grüße, Christian
Ja das kann passieren wenn die Hauptstraße sehr geradeausgeht – wenig Kreuzungen hat – und der Weg daneben halt deutlich komplizierter. Zeit Minimieren hat das Problem dass es meist über längere Distanzen nicht klappt.
Hi, this weekend I was about to go crazy with my Garmin while mountain biking.
I set up my Edge 830 as you say in this guide but it kept pointing me to follow the paved road instead of the mountain bike trails.
The settings were:
– vehicle type: mountain bike
– route preference: minimize ascent
– items to avoid: toll roads.
So, when I got home, I tried to plot the route with BaseCamp and in fact it gave me the same indications, which I post in the image below.
Next, I tried playing with the autorouting settings, and if I turn off state highways, it gives me the route I eventually followed (it was a route designed for a local event).
The result remains the same if I choose the car as the autorouting profile. What do you recommend me to do? Keep car as my profile while mountain biking?
Many thanks and keep up with the great work!
Emanuele
Wrong path:
Right path (both with ‘mountain bike’ + ‘avoid state highways’ and ‘car’:
avoid toll roads only if you want to avoid very difficult ways. However usually nowadays shorter distance gives better results than faster time (which you were using). Sometimes it is not possible to understand why a certain road is chosen, but mountainbike, no avoidances (toll roads does what it does usually – meaning nothing mtb:scale=3 or more difficult) and shorter distance works best. Sometimes you still have to force the route via via points.
using shorter distance or faster time didn’t make any difference, the annoying part of this is that the device was pointing me to the paved road including a 200m climb instead of a downhill single trail. Also, on garmin edge 830 you have to choose between faster time, shortest distance or minimum ascent, so it’s a bit different than the basecamp profile. I think I’ll try car profile next time
usually shorter distance or faster time makes a huge difference in the routes chosen. But yeah in some places no clue why routes do not chose a specific way.
Actually, before the big update in late May, the maps worked great and the device was directing me to nice trails.
I don’t know if this is a coincidence or if it is related to the update, or the fact that I was near a map boundary, or due to some map issue in that area.
Next time I’ll test out 🙂
Hi Felix
I found another “crash point” with the 02/07 maps, which did not happen before but now, ridden twice crashed twice. Edge 830 is being a painnful thing
It is at the point highlighted in the attached screenshot.
Closest OSM node: https://www.openstreetmap.org/node/415767820
At OSM way: https://www.openstreetmap.org/way/35444777 towards the North
I was following a route, imported into the Garmin from Komooth
Same crash at the same point yesterday with the 09/07 map.
New crash this morning at another point. Let’s see tomorrow there
Just reviewed a few past activities in Strava and the new crash is not actually new, it’s recurrent.
Closest node: https://www.openstreetmap.org/node/1847483899
Riding https://www.openstreetmap.org/way/174005252 towards the South
In both cases, the device crashes only when following a route.
I just tried it out on my Oregon 600 – however with the map from the 9. July – and it is not crashing. Can you try the 09.07 spain map please?
Yes, I did…
https://openmtbmap.org/about-2/autorouting/comment-page-1/#comment-24671
However I made a third pass over that point and did not crash. The only difference was that Climb Pro was off on that time
Crash today at the same point. Climbpro activated. Turn by turn guide on. Device on data screen
Made a second pass and crashed again.
Third pass with Climb pro off (but device on the map screen) and did not crash
Okay – I don’t have a device with climbpro to test. I didn’t think so far elevation profile has something to do with routing (garmins own maps work a bit differently there) – but so with climbpro it seems they do. I cannot debut this. I think it is rather due to the altitude profile than to the map itself.
Glück Auf, Felix!
Mir war aufgefallen, das beim Routing mit der openmtbmap am PC mit Basecamp 4.6.2 schon bei einer relativ geringen Strecke die Luftlinie angezeigt wird. Dabei hatte ich als Profil “Fahren” eingestellt, mit dem PKW-Symbol, und alle Vermeidungen deaktiviert. Diese Einstellungen hatte ich mir mal vor ein paar Jahren gemerkt als sinnvoll.
Ich hatte schon angefangen, eine entsprechende Support-Anfrage zu schreiben.
Inzwischen habe ich dann aber in der Anleitung zum Autorouting gelesen, dass “Auto/Motorrad nicht für längere Strecken geeignet” ist, weil Garmin das Autorouting 2016 stark verändert hat.
Mit dem Profil “Fahrrad” klappt es jetzt aber! Auch mit der Einstellung “kürzere Zeit” komme ich ziemlich weit.
(Wäre eine typische “RTFM”-Anfrage geworden…)
Vielen Dank nochmal für die Erstellung / Bearbeitung und Bereitstellung der Karten!!! (Auch wenn ich jetzt der 1000ste bin.) Ich unterstütze dich gerne weiterhin mit einem Abo!
Viele Grüsse aus dem Harz,
Henning
Ja – Garmin hat da leider einiges in negativer Richtung verändert.
Hi
I’am having an issue with my new Garmin Edge 830. When I ask the device to autoroute to a certain area, the routing is done, then a few seconds later the device restarts.
It is a short one. 10Km. It always happens with that area, but not with others. Spain/Madrid zone.
I have now 30.01 map, gmapsup.img direct download. It also happened with the previous version and the version before last. The device is new so I cannot tell you if also happened with 2019 versions.
Is there any way you can dig into it? I can send any info or files in the Garmin you may need.
Thanks
cv
I don’t think I can find out what happens there. It’s very strange. I guess it will go away in a couple of weeks/months. You could try to send the map as an extract from the Europe continent map – instead of the spain map instead. Such problems are super rare – but I have no idea how to find out where the problem is.
Same thing with partial extrract from Europe 🙂 Weird…
Thats very strange – are you always routing to the same place or starting from the same place?
Yes, it’s always from
N40° 31.290′ W3° 55.812′
to
N40° 26.523′ W3° 57.266′
Basecamp calculates a route, not the best one though
okay – I will check 4 weeks (I’m just leaving for Nepal – and the internet speeds are not good enough for me to analyze it from there…)
Thanks
Just to mention, the issue is still there with latest, February, maps. There must be something rare in OSM Data in the area. A couple of days ago I was riding around that route, I went off course, the Garmin recalculated and crashed.
Yep, I suspect super micro mapping but have to check. Or duplicate roads on top of each other (my maps don’t handle that well)
Hi, a bit more info:
I found that the route that makes the Garmin crash has a gap. The device calculates the route and I can see the route map (with the gap). The device does now crash until I start the navigation.
The OSM points at the edges of the gap are:
https://www.openstreetmap.org/node/3007268429
https://www.openstreetmap.org/node/309663416
Some bitmaps and Garmin crash reports here:
https://drive.google.com/drive/folders/1jLtUjs_v8ysci_8oSvyzaMUm7Oi9dghB?usp=sharing
Next week I will have a look at it. Right now in Nepal internet is too slow to analyze it.
If I invert the route, the result has the same gap, but the device does not crash, at least when I press “ride” (I have not ridden it actually)
Hi Felix
Hope you are not trapped in Nepal by coronavirus!!!
No, i’m trapped in Vienna at my parents place right now. My flight back to Italy got cancelled but I could reroute to Vienna (that was on 05 March). So no worries – I’m in the same boat as everyone else here in Europe. I had already been afraid when booking in January but speculated Nepal cannot test for it and 10.02 to 05.03 is still fine. I did not expect that Italy breaks down so quickly – I had rather expected it for Nepal first.
Hi Felix. The issue is gone with the latest map. The gap is closed and the device does not crash.
Thanks
cv
Hi Felix
The issue is back, now in a different area. This time is different as the route that makes the device crash is calculated by the device from one point to another. There are no gaps like in the previous case…
Is there anything you can look at? I like the maps but they are hard to use if I get random restarts.
Garmin will not provide any help, as third party maps are not supported
can you tell me the coordinates / location (easiest would be an OSM permalink for the location of the crash).
Hi Felix, is not related to a particular point, I guess
I can reproduce the issue with the same route as back in Feb
https://openmtbmap.org/about-2/autorouting/comment-page-1/#comment-24029
Same gap in the route but different behaviors depending on how is calculated. I made a short video that is easier that is easier than writing:
https://youtu.be/43jLB7mHJT4
This is very strange – I am trying to find out why this happens there – but not sure I can find the bug.
Answering here – because lower down is not possible anymore. Can you just try to route in that short section – with the two oneway lanes – from the one to the next waypoint as seen in my screenshot.
I assumed the starting point should be the flag at the top-right and the destination the flag at the bottom-left.
I tested a few cases:
1. Navigation => Courses => Course Creator => Add your two points => View Map => Ride
The Garmin calculates a route with a gap. The device does not crash when I press Ride which is consistent with the behavior in the video.
Screenshot 1
2. Navigation => Browse map => Select your destination point => Ride
The Garmin crashes shortlyafter calculating the route from my current location (at home) This is also consistent with the video.
3. Same as case 1 but swapping the points
Similar gap in the reversed route but no crash in any case
Screenshot 2
4. Same as case 2 but using your top-right point as destination
The Garmin calculates the route from my current location, there is still a gap, very similar to the one in the video, but no crashes.
okay – thanks for confirming. It’s a bit strange why it’s crashing – but I know the reason. So it’s the following. In order to make residential streets (and some more) also routable against an indicated oneway direction – I add the same road twice. Once normally in proper direction and oneway – once usable in both directions but at very low speed/priority.
On most devices this does not seem to cause problems. I will try out some things and drop another message in 1-2 days using another solution, maybe that will then evade crashes – thanks a lot for your screenshots.
Could you please try out this version from today – between the same two points: https://openmtbmap.org/mtbspain.exe
MacOs… 🙂
oh just get the newest mac osx – The windows version is on a different server – so only updates twice per day. The mac osx version is instantly up to date after I update it. Also the gmapsupp.img version is up to date.
Nothing has changed I am afraid
okay – that’s pretty bad. I hoped todays map – 27.05 fixes the routing problem. I will try some other solutions – but I think I will have to cut down on the oneway opposite routing then. But I don’t really want to do this everywhere – it is very useful on devices where it’s not broken (I will cut down on the oneway routing in city cases however).
Hi Felix, any news on this?
I’ve got some more crashes in different areas, perhaps due to the same isuee
Thanks
cv
I still couldn’t solve it. On todays maps it should be less common – but not fully solved.
The settings
did you activate any avoidances?
Toll roads only. But it crashes also with all deactivated
Toll roads I meant
yes – that’s fine. What about the newest map. Is it still crashing?
oh yeah – and what are your autorouting setting on the device?
I think it is finally fixed – download the maps as of yesterday/today and I hope those errors are gone.
Hi Felix
The gap in the route is gone with the latest version.
Unfortunately I am away from home for a few weeks si I won’t be able to test if the crash is gone as well.
I’ll let you know as soon as I can.
Thanks
cv
It should be gone – as well as routing problems in other areas. There was a problem with the map compiler.
Hallo Felix,
vielen Dank für alles, einfach sensationell.
Ich habe ein Edge Explore und spiele mit dem Routing und der OSM sehr viel auf meiner Hausrunde, um die Algorithmen zu verstehen.
Ich stolper jedoch immer wieder über die Routing Unterschiede zwischen Basecamp und dem Garmin. Das Garmin führt mich sehr häufig über Wege hoch, die mit mtb:scale:uphil:5 markiert ist.
Lässt sich das irgendwie vermieden?
Im Basecamp wird dieser Weg uphill vermieden.
Linie: 115591401 im osm, falls dir das etwas bringt (Schweiz)
Viele Grüsse
Julian
Das ist leider irgendwie immer ein bisserl blöd. Du kannst wenn du Strecken vorplanst – genug Zwischenpunkte setzen – damit das nicht passiert. Am Gerät mal andere Einstellungen versuchen – aber Patentrezept gibts leider keins mehr.
Hi.
Garmin Basecamp Version 4.8.4 on MacOS. Map: omtb_spain_20.08.2019
My issue: Dirty Biking is the recommended choice by it produces weird results. In the example attached, default Dirt Profile produces a huge detour. If I unlock Interstates, which should be less restrictive (and is the recommended option), it draws a straight line!!!
I’m not sure – maybe in that area there are a few problematic roads/pathes that are not correctly connected in OSM?
Second – Remove the feature type avoidances – especially carpool lanes can cause huge havoc. Same for U-turns!
You could try avoiding residential roads – lately this often produces better results. Avoiding interstates is not good.
I cannot see the map scale – try setting a via point in between longer distances.
Hi.
I assume that points are connected as “Mountain Biking”, “Walking”, “Hiking” and some other profiles are able to make a route.
I have made some combinations and put the results here
https://docs.google.com/presentation/d/1-tGtku8U3nMtdD9ryRB1Se-bQbQb43SL803DtcMmIHE/edit?usp=sharing
In summary, ATV and Dirt make straight lines most of the times. Mountain Biking without avoidances makes it pretty well
I guess the distance is too large and that causes dirtbike and ATV to fail calculating a route. You still have the carpool lanes ticked in the mountainbike profile shot.
Unticking Carpool lanes in MTB profile did not make any difference.
I put a via point right in the middle… no changes (now I get two straight lines!!). I had to use 3 via points, evenly distributed between Start and End points to get results with AVT and Dirt profiles…
I tried with different Start and End points separated by 18 Km and:
– Dirt without any avoidance make a straight line
– Dirt with only Interstates ticked makes a crazy detour for about 75Km !! see screenshot.
Probably the best way either use Mountain Bike without avoidances or setup a via point each 4-5 Km if you want to use Dirt without avoidances.
Forgot to say.. the doc says “Dirt Biking gives the best routes and can route over very long distances (>100km by air without any intermediary routing points)”.
Perhaps that shoud be reworded 🙂
yep I guess I have to adapt it – it’s often become problematic with Basecamp 4.6 or higher on Dirt Biking (was fine at least up to 4.5.x)
Sure, yesterday I used Google Transalator to read the german comments in this thread and found that there are many users having this issue 🙂
I’ve rewritten most of the page now (easier to read, and updated).
Hi Felix, ich hab mit gerade nen Edge 830 geholt. Dabei sind mir 2 Sachen aufgefallen:
1. Es gibt beim Routing ne neue Option “Routing nach Beliebtheit”, diese Option ist standardmässig eingeschaltet. Ne Idee, wie diese das Routing beeinflusst? Besser abschalten?
2. Nen genereller Hinweis. Die Kartenliste scheint von der Anzahl der Listeneinträge begrenzt zu sein. Ich hatte für 7 Länder schon Höhenlinien drauf geladen. Da wurde nur noch eine von mir draufgeladene Karte angezeigt, obwohl es 4 waren. Habe dann die nicht direkt benötigten Höhenlinien gelöscht und dann wurden die weiteren Karten angezeigt.
Gruß
1. Nein keine Ahnung. Das gibts wohl nur auf neuen edge.
2. Ui da war früher auch mehr Platz – sprich locker 20 Einträge.
1. Ok – dann mal beobachten
2. Yep – ziemlich doof, da man ja mit aktell mit Basecamp nicht mehr “kacheln” kann. Ich wohn im Grenzgebiet und brauche dann schon 3 Karten plus Höhenlinien. Dann jetzt noch Italien für den nächsten Urlaub. Dann ist ja auch noch Trailforks mit drauf. Man könnte natürlich alles Originale runterschmeissen. Lasse ich aber gerne als Notanker. Aber haushalten muss man eh, da Garmin wieder extrem geizig mit Speicher war und keine SD Karte.
2. doch geht noch immer mit MapInstall. Du musst die autorun.inf auf die Speicherkarte packen willst du über 4GB senden – etwa aus Europakarte. Ansonsten Mapsource läuft auch noch wie eh und je.
Hallo,
ich habe auch das Problem mit dem Autorouting.
Wenn ich Autobahnen vermeide dann gibt es nur eine Luftlinienverbindung.
Ich verwende die Version 4.7.0, aber unter der Vorgängerversion war es schon genauso.
Autobahnen vermeiden – weswegen tust du das? Lies dir auch einmal die Kommentare etwas unter deinem durch. Wenn schon dann residential roads vermeiden (mit Dirtbike/ATV). Kürzere Distanz ist fast immer besser als kürzere Zeit.
Hallo, danke für die Antwort.
Wenn ich Autobahnen vermeiden nicht auswähle, bekomme ich nur eine Luftlinienverbindung.
Entschuldige, war ein Wort weg gelassen.
Ich kriege einfach kein vernünftiges Routing hin.
Viel Straßen obwohl es auf der Karte Feldwege und Pfade gibt.
Die laufen zum Teil parallel zur Straße.
Mit der Garmin Cycling Map klappt es besser, aber auch nicht optimal.
Ich bin etwas ratlos.
Viele Grüße Bertram
Wie weit sind denn die Viapunkte voneinander entfernt?
Versuche mal Modus Fahrrad, keine Vermeidungen (außer evtl unpaved roads je nach Bedarf) – kürzere Distanz.
Alternativ – Residential Roads / Ortsstraßen vermeiden aktiveren – kürzere Distanz – sonst keine Vermeidungen!
Im Minimalfall 1 km Luftlinie, ich habe es variiert.
Das darf überhaupt nicht sein – evtl ist da irgendwas falsch in der Gegend bzw ab dem Punkt. Wie setzt du Start und Zielpunkt? Bzw welche Einstellungen hast du jetzt beim Autorouting Setup?
Evtl ist da grundlegend was schiefgelaufen beim installieren der Karte – welches Land, welches Datum? Was ist beim routing einfach nur um eine Straßenecke?
Hallo, ich habe nun die Karte nochmal installiert.
Es tritt jetzt folgendes auf, wenn ich Routing wähle und als Fahrzeug Mountainbike oder auch Geländefahrzeug wird geroutet, zwar ziemlich straßenlastig aber es funkioniert, auch über einige km Strecke.
Sobald ich aber meinen Garin mit der installierten Garmin Cycle anstecke, die ausgewählte Karte bleibt die Open MTB Map, geht plötzlich das Routing nur noch wenn ich die Autobahnen auf vermeiden stelle.
Garmin wieder abziehen und das Routing klappt wieder.
Ich versuche in den nächsten Tagen noch Bildschirmfotos zu machen.
Viele Grüße Bertram
Du meinst am PC wenn du das Garmin Gerät mit der Cycle Map anhängst – geht das Routing nicht mehr? Könnte sein – es darf immer nur eine einzige routingfähige Karte aktiv sein – evtl wird die Karte quasi dazugeladen. Probier mal andere Einstellungen auch aus – und halt bis auf evtl residential roads oder unpaved/toll roads keine weiteren Vermeidungen!
Hallo Felix
Danke für die Antwort. Erste Tests waren positiv
Grüsse von Ernst
Hallo Felix
Hast du meine Anfrage vom 30. April übersehen?
Grüsse Ernst
Nein habe ich nicht. Es stimmt mit Basecamp 4.6 hat Garmin Das Routing mit Dirtbike ziemlich zerstört. Alternativ kann man “Residential Roads” / “Straßen in Wohngebieten” noch verbieten – dann klappt das Routing mit Dirtbike oder Motorcycle oder Car/PKW recht gut. Bis Basecamp 4.5.x hat Dirtbike/ATV sehr gut funktioniert. Jetzt leider nicht mehr.
Hallo Felix
Benötige auch mal wieder deinen Rat.
Aus Beilage ist ersichtlich dass Basecamp in Münster nicht mal einen Kilometer routen kann mit Dirt-Biken und den von dir angegebenen Vermeidungen. So viele Strassen sind ja dort nicht.
Habe dasselbe Problem schon des öftern festgestellt.
Verwende Basecamp 4.6.2. und neuste Velomap_Germany
Danke für deine Hilfe. Als Veloreiseleiter wäre ich echt froh wenn das Routing besser funktionieren würde.
Grüsse aus CH von Ernst
Habe bis jetzt das Autorouting in Basecamp (4.6.2)im Autoprofil mit allen Vermeidungen deaktiviert (Straßentypen + Merkmale) durchgeführt (kürzere Zeit). Entsprechend dieser überarbeiteten Anleitung habe ich nun mal das Profil Dirt-Biken versucht entsprechend der Anleitung unter ‘Für Vertriden…..’, also kürzere Strecke und keine Vermeidungen ausgewählt. Da erhalte ich aber lediglich eine Direktverbindung von A nach B (etwa 30km), eine vernünftige Route ergibt sich nur, wenn mindestens ‘Autobahn vermeiden’ aktiviert ist (neueste Europakarte 08.03.2019). Entsprechend Anleitung soll aber genau das doch nicht aktiviert werden. Was läuft da (bei mir) eventuell falsch?
Gruß Manfred
Ist mit kürzere Zeit wahrscheinlich zu weit – sprich du musst kürzere Distanz nehmen – oder mehr Viapunkte setzen. Und ja – Autobahn vermeiden definitiv nicht aktivieren.
Das funktioniert (bei mir) auch nicht mit wesentlich kürzerer Entfernung (z.B. 7,5km). Ich bekomme mit Dirt-Biken (kürzere Zeit, alle Vermeidungen ohne Häkchen) immer nur eine Direktverbindung. Erst wenn ich zumindest ‘Autobahnen’ aktiviere, bekomme ich eine Route. Mit der bisherigen Vorgehensweise (Modus ‘Auto’, kürzere Zeit und alle Vermeidungen ohne Häkchen) funktioniert das auch über größere Entfernungen (ohne Viapunkte) völlig problemlos. Kann das an der Karte liegen (Europa 08.03.2019)? Habe leider kein älteres Kartenmaterial zum Ausprobieren. Gruß Manfred
Funktioniert es auf 500m? Ab und zu gibt es Punkte die in Basecamp nicht routen wollen – helfen tut dann neben die Straße den Punkt zu setzen. Welche Basecamp Version – von 4.8.x auf OSx hab ich schon komische Sachen gehört.
Basecamp 4.6.2 unter Win8.1. Mit den identischen Start- und Endpunkten funktioniert es mit Kartenmaterial ‘Bayern 07.05.2015’ problemlos, sowohl im ‘Auto’ als auch im ‘Dirt-Biken’ Modus (kürzere Zeit, kein Häkchen gesetzt) kommt identische Route raus. Da fahre ich wohl doch besser wie bisher im ‘Auto’-Modus :-). Gruß Manfred