Is the time estimation using the fitness function broken for bike routing?

[anna.b...@gmail.com]

see unset  (0:17)

https://maps.openrouteservice.org/directions?n1=49.011753&n2=8.418617&n3=14&a=49.01468,8.358107,49.013273,8.422544&b=1b&c=0&g1=-1&g2=0&h2=3&k1=en-US&k2=km

vs novice (0:34)

https://maps.openrouteservice.org/directions?n1=49.011753&n2=8.418617&n3=14&a=49.01468,8.358107,49.013273,8.422544&b=1b&c=0&g1=0&g2=0&h2=3&k1=en-US&k2=km

vs pro (0:36)

https://maps.openrouteservice.org/directions?n1=49.011753&n2=8.418617&n3=14&a=49.01468,8.358107,49.013273,8.422544&b=1b&c=0&g1=3&g2=0&h2=3&k1=en-US&k2=km

or did I get sth. wrong?

Thanks,

Anna

[Timothy]

Hi Anna,

the fitness settings are still very early stage. Please use with care. 

Could you please open an issue on https://github.com/GIScience/openrouteservice and explain the expected behaviour?

Thank you

Tim