[OSRM-talk] weight instead of speed

Emil Tin ZF0F at tmf.kk.dk
Fri Feb 15 14:55:11 GMT 2013

> can I use weights instead of speed for routing?

Not yet, but it's heavy requested, and as Dennis mentioned, on the OSRM to do list. Initial work has been done in the branch https://github.com/DennisOSRM/Project-OSRM/tree/feature/lua_impedance. Here you can set speed/impedance separately, however, there's a problem with the travel time not being correct.

Regarding relations, there's a working implementation in https://github.com/DennisOSRM/Project-OSRM/tree/experimental/route_relations. Check the bicycle profile.

Med venlig hilsen

Emil Tin
IT- og Processpecialist
Teknik- og Miljøforvaltningen
Center for Trafik

Islands Brygge 37 Vær. 169
Postboks 450
2300 København S

Mobil +45 2369 5986
Email ZF0F at tmf.kk.dk
EAN 5798009493149

-----Oprindelig meddelelse-----
Fra: Jens Thiele [mailto:karme at karme.de] 
Sendt: 15. februar 2013 15:47
Til: Michal Palenik
Cc: osrm-talk at openstreetmap.org
Emne: Re: [OSRM-talk] weight instead of speed

Michal Palenik <michal.palenik at freemap.sk> writes:

> hi
> I try to set up a bicycling routing. in bicycles, speed is not the only
> routing parameter, but some other abstract measure (which a function of
> speed, safety, surface, comfort and gerenal coolness of the way). after
> searching osrm github (which shows similar thoughts) I've got lost...
> so:
> can I use weights instead of speed for routing?
> can I put different forward/backward speed/weight on a way?
> can I use out of OSM information? (e.g. elevation)
> (or does any branch support this?)

maybe a good time to provide a quick status update from my side

i am working on a tool implementing an additional preprocessing step
which does the following (already took much more time than expected):

- split ways at intersections
- add elevation profile (and length) to ways
- denormalize relations onto ways
- fix way references in restriction relations

it works but is still quite slow (memory consumption is ok, though)
other todos:
- cleanup
- limit precision in output / fix output format
- handle duration when splitting way (can't think of a better solution
  than distributing according length)
(- handle tunnel/bridges?)
(- maybe handle areas at some point?)

example input (799K):
example output (540K):

after that the normal processing can go on and the lua way function has
all information required

there is a branch for different foward/backward weight and emil had a
branch for weight vs time - likely dennis/emil will comment on this


OSRM-talk mailing list
OSRM-talk at openstreetmap.org

More information about the OSRM-talk mailing list