prioritize cycleways in bike routing

[emmexx]

From what I understand looking at the code, osrm is not giving an advantage to cycleways (highway=cycleway or highway=* AND cycleway=*) when calculating edge weights.
As a consequence I noticed that almost always osrm chooses a "normal" street instead of the cycleway that runs parallel to it.

I don't know enough the algorythm used to choose a way or another but, from what I understand, in the current version of osrm only the speed is used as a weight edge.
Is there any plan to change this behaviour?

thank you
maxx

[DennisOSRM]

Yes, work for a scripting engine using LUA is underway. It will give much more flexibility and will let you specify any priorities.

[emmexx]

Il 06/28/2012 11:42 AM, Project OSRM scrisse:

Yes, work for a scripting engine using LUA is underway. It will give
much more flexibility and will let you specify any priorities.

Great!
Emil Tim wrote about this in another thread.
I'd like to contribute.
Is the following the correct starting point?
#240.

thank you
maxx

[emmexx]

Another important feature should be to give a "feedback" when a cyclist should use a cycleway. Roads and cycleway often run in parallel and in OSM many cycleways don't have a street name.
It would be helpful to add to the json answer a flag to indicate that the suggested way is a cycleway.

maxx

[emiltin]

the way name should be chosen/constructed by the lua parser too

[emiltin]

see #77 for discussion about weights in general

[emiltin]

a good solution to this requires separating speed and impendance, so leaving open for now.

[daniel-j-h]

Outdated; take a look at the bicycle.lua profile. There are already tickets re. speed vs. weight.