[dockd]

There's also a huge variation in what roads cyclists consider acceptable.

For example, one of our local highways has a speed limit of 55mph and a shoulder that is maybe 10 feet wide with a rumble strip near the cars. Is that a good road for bicycles or not? I'm OK with it but some of my riding friends are not. A bike path can be perfect for a family yet dangerous for practicing time trials.

I've also been surprised at how narrow some of my favorite roads are for driving. Just about any road is great if it doesn't have traffic. So a good road at lunch time is no good during rush hour.

So maybe the ultimate bicycle router would a) Offer a bunch of preferences just like you see for cars, e.g. "avoid freeways", "avoid tolls". b) Flag roads as "avoid", e.g. that four lane road with no shoulder next to the sidewalk. c) Specify roads with gravel. (OSM data can have this; not sure about Google.)

[gonehome]

Most cyclists I know use Garmin bike computers and (when their servers are not down from ransomware hacks) I think they work pretty well.

I know they do a lot with determining routing based on what other cyclists prefer, but I'm not sure how granular it is.