search

buskerudbyen / cycling-norway

3 stars 2 forks source link

Travel time: Investigate the validity for the planned route #66

Closed tsobuskerudbyen closed 1 year ago

tsobuskerudbyen commented 1 year ago

Got some feedback that it seems that our solution overestimates the time used to cycle a route. Se example and comparison between Ås and Oslo under. What is the criteria and estimated time made of here? thumbnail_image006 thumbnail_image005 https://leonard.io/cycling-norway/?from=59.66340%2C10.79422&to=59.91107%2C10.74813#9.03/59.7876/10.7977

Beck-berry commented 1 year ago

We use the following settings as in this example query.

    modes: {directMode: bicycle, accessMode: bicycle, egressMode: bicycle}
    bicycleOptimisationMethod: safe
    triangleFactors: {safety: 0.6, slope: 0.2, time: 0.2}
    bikeSpeed: 5

We can change these parameters as you'd like.

tsobuskerudbyen commented 1 year ago

Sorry, probably not made myself clear here. It is the time estimated to cycle a route I am questioning. Why is the time from Google Maps faster than OTP/Entur? Just checked another service – Komoot – and this estimates travel times of 2 hours and 32 minutes with a e-bike and 2:06 with road cycling. Per now I feel that our solution is estimating using longer time on longer routes, and – hence – may discourage people from cycling.

leonardehrenfried commented 1 year ago

@Beck-berry Can you increase the bike speed a little?

Beck-berry commented 1 year ago

I modified the settings like so:

  bicycleOptimisationMethod: triangle,
  triangleFactors: {safety: 0.5, slope: 0.2, time: 0.3}
  bikeSpeed: 7

Image

@tsobuskerudbyen Is it more like what you wanted?

tsobuskerudbyen commented 1 year ago

For this ticket/issue there is just change in bikeSpeed: 7, right? I do not see any changes in the route. If that is the case, it looks good for now. Just leave it closed. Thanks!

leonardehrenfried commented 9 months ago

Yes, the speed should not change the route at all.