hexhome wrote:andymiller wrote:Another option rather than abandoning the map would be to switch off the 'avoid highways' setting.
Again there's another option: change your settings: when you want a fast route switch to 'route for cars/motorbikes' and if you want a more scenic option switch to 'route for bikes'.
I'm confused by the reference to algorithms - I thought the algorithms were in the software - either on the PC or the GPS or on the unit itself - although I can see how the map can influence the routing outcome (eg classifying certain roads as highways).
Is there anyone who can give a quick explanation of how the Garmin gps and the map interact - eg does the Garmin cycling option mean that it prefers roads marked as cycle-friendly in the mapping database - or simply avoids roads where bikes are prohibited?
This isn't as clear as it at first appears. Each mapset seems to have it's own way of interpreting GPS or Basecamp settings. For example
http://www.openfietsmap.nl/tips-tricks/ ... amp-3-3-en and
http://www.velomap.org/velomaporg/autorouting/In neither of these examples do the obvious settings produce the desired results. As an example, I have been struggling to get OFM to give me a route other than on fast trunk roads, after reading the instructions carefully, I found that on the GPS, selecting 'faster time' produced the desired result. I have not been able to achieve this with Basecamp yet. So to take your suggestion to switch off 'avoid highways' would actually have the opposite effect!
For cycle specific routing which avoids fast trunk roads with OFM, my Etrex 20 has to be set to route for 'Car and Motorcycle', no avoidances and route for time. If I change profile to bicycle, it will route me along a fast trunk road. I would advise anyone who uses any of these solutions for autorouting to read the providers instructions regarding settings very carefully.
Incidentally, you have assigned quotes to the wrong sources.
Just to clarify, there are some aspects of routing that are built into the mapping and cannot be altered by settings. The trunk road setting of VeloMap is built into the mapping as permanently missed off routing information, so there is simply no data.
As a quick guide to what is going on, OSM has all the roads with tags on them to describe the types of roads they are. These are arbitrary and every system that renders the map data into a working map for Garmin has to use a tool to translate the data from OSM into Garmin's definitions via a variety of tools. TalkyToaster uses one system, based on his knowledge of the UK road system, Mr Velomap has based his work on the German system. The tag used for trunk roads is the same in the UK and Germany, but in Germany it means "No bikes", in the UK it means "Bikes allowed" As the OSM system has no way of understanding national boundaries, it is not possible to generate a Europe-wide system based on the current tags. It's basically an error in the underlying data of OSM, using the same tags for different road types. Velomap takes it a bit further, and as it is targeted at cyclists, he makes use of the car option as another alternative for cycle routing and has, fro example, made cycle paths appear to the routing software as if they are roads so that option will work.
Using the TalkyToaster OSM maps, I got a 12 mile auto-route home from New Street Station (the joys of arriving back on the train from C2C at 10:30pm on a rainy Sunday) to my home near Solihull and it took me a perfect cycle route on my 800, avoiding main roads - going parallel to them even though this was slightly longer - taking a direct route that took advantage of cycle routes in one or two places. It clearly was correctly weighted to avoid main roads without refusing to use them when there was no alternative.
So, I guess to summarise the issues:
1. There are many different variations of OSM available.
2. Different variations will route differently and interact differently with routing options on the Garmin.
3. The routing may work differently on different Garmins, so there is no guarantee that one person's experience will mirror another's.
4. Routing does work well on OSM. However, there are variations, and also BaseCamp may route differently to the Garmin device.
5. More modern Garmin devices can provide guidance from tracks. Older eTrex devices expect to have a route and do not generally provide routing on tracks.
6. OSM is more likely to have areas where there are mistakes on mapping than the OS derived professional mapping; however, aside from that there is no guarantee that the Garmin OS routing is better than OSM derived maps.
7. If an actual route is required to be followed, on older eTrex devices, you need to build one or more routes of 50 or less points, and check the route on the device to convince yourself that it will work.
8. Appearances are dependent on device, and there are no best versions, just personal taste.
9. Garmins can get a bit upset if they are not convinced you have started a route and will merrily try and guide you to the start until such time that they are convinced you have passed though a via point, or some other clue that you are on the way. Newer Garmins are better at this than the old eTrex.
A reasonable routing test is to find a route where to get from A to B you have a choice of 100 metres on a trunk A road (e.g. working across the A46 north of Stratford-upon-Avon or across the A50 near Burton-upon-Trent) where the alternative is a 2 mile diversion. (This is also a test for you - would you want to cycle 2 miles to avoid a potentially dangerous trunk road?)