bicycling 940 meters takes 90 minutes?

[emiltin]

~$ curl "http://localhost:5000/route&55.69412&12.55245&55.68923&12.55311"

12.55246,55.69412 12.55267,55.69396 12.55267,55.69396 12.55301,55.69373 12.55311,55.69354 12.55280,55.69334 12.55247,55.69316 12.55349,55.69247 12.55400,55.69213 12.55303,55.69152 12.55397,55.69089 12.55450,55.69053 12.55501,55.69019 12.55579,55.68971 12.55504,55.68886 12.55487,55.68866 12.55450,55.68824 12.55285,55.68851 12.55297,55.68882 12.55307,55.68912 12.55311,55.68922 drive for 60m drive for 80m drive for 150m drive for 90m drive for 270m drive for 180m drive for 110m drive for 70m drive for 10m

[emiltin]

speedprofile is the default from the repo:

[car]
motorway = 110
motorway_link = 90
trunk = 90
trunk_link = 70
primary = 70
primary_link = 60
secondary = 60
secondary_link = 50
tertiary = 55
unclassified = 25
residential = 40
living_street = 10
service = 30
ferry = 5
pier = 5
obeyPollards = 1
useRestrictions = 1

[bike]
trunk = 16
trunk_link = 16
primary = 16
primary_link = 16
secondary = 16
secondary_link = 16
tertiary = 16
unclassified = 16
residential = 16
living_street = 16
service = 16
track = 16
cycleway = 16
path = 16
ferry = 5
pier = 5
obeyPollards = 0
useRestrictions = 0

[emiltin]

guess i don't specify bicycle anywhere in the request - what profile is used then?

[DennisOSRM]

The first profile in the ini file is used. KML is broken in so many ways and it's going to be removed soon. I am closing this issue therefore.

[emiltin]

can i choose the profile when i request a route?

[DennisOSRM]

No, you have to specify beforehand or hack the server to hold routing data for several profiles simultaneously.