My knowledge of route finding is pretty basic so correct me if I am wrong.
I would expect that the route finding routine runs on some sort of shortest path algorithm. Now weights can be added to different roads. Now in google maps and most other mapping software the parameter which we are trying to minimize is time so there is a waiting produced to favor trunk roads and motorways. Some mapping software also alowes you to also choose shortest route.
Every road is classified and this will already be held by google. There is a possibility to have a users control panel where the weighting for each road type can be defined by both numerical and sliding bar values. There can be a series of preset values such as normal (probably fastest), scenic, lorries (an infinite weight put on any v.narrow roads or low bridges, I think google has this info already), no motorways, minimize use of dual carriage ways / large A roads e.t.c. These can be a starting point for people to tweak for their own use. This would not be perfect I know and as a cyclist you may still get sent on the Hamersmith flyover but it is an easy to implement solution which could give large customization possibilities for many types of user.
EDIT: You could also have a community type feature where say someone like VB says like these parameters when cycling around London and surrounding area fast but then someone else in Newcastle cycling with their children would like a different set of parameters. Settings could be sheared and described.
How about this VB.
My knowledge of route finding is pretty basic so correct me if I am wrong.
I would expect that the route finding routine runs on some sort of shortest path algorithm. Now weights can be added to different roads. Now in google maps and most other mapping software the parameter which we are trying to minimize is time so there is a waiting produced to favor trunk roads and motorways. Some mapping software also alowes you to also choose shortest route.
Every road is classified and this will already be held by google. There is a possibility to have a users control panel where the weighting for each road type can be defined by both numerical and sliding bar values. There can be a series of preset values such as normal (probably fastest), scenic, lorries (an infinite weight put on any v.narrow roads or low bridges, I think google has this info already), no motorways, minimize use of dual carriage ways / large A roads e.t.c. These can be a starting point for people to tweak for their own use. This would not be perfect I know and as a cyclist you may still get sent on the Hamersmith flyover but it is an easy to implement solution which could give large customization possibilities for many types of user.
EDIT: You could also have a community type feature where say someone like VB says like these parameters when cycling around London and surrounding area fast but then someone else in Newcastle cycling with their children would like a different set of parameters. Settings could be sheared and described.