Hi,
this morning, trying to use my map (https://parcours.scasb.org ) wich use ORS.
And got the error 2009 when sending more two waypoints.
Something have changed?
The body of the post request to https://api.openrouteservice.org/v2/directions/cycling-road/json:
{
"attributes":["avgspeed","percentage"],
"elevation":"true",
"extra_info":["waytype","surface","waycategory","suitability","steepness","tollways","traildifficulty","osmid","roadaccessrestrictions","countryinfo"],
"id":"rounting_request",
"instructions":"true",
"instructions_format":"text",
"language":"fr",
"maneuvers":"true",
"continue_straight":"true",
"geometry":"true",
"coordinates":[[2.2913789749145512,48.6539204007717],[2.286314964294434,48.65825778238394],[2.2797918319702153,48.659816880668174]]
}
And got an http error 500 with the json response:
{
"error":{
"code":2099,
"message":"Heading is not (fully) supported for CHGraph. See issue #483"
},
"info":{
"engine":{
"version":"6.1.1",
"build_date":"2020-06-22T04:58:15Z"
},"timestamp":1593156975489
}
}
adam
June 26, 2020, 7:48am
2
Hi @gegeweb
there was a problem introduced in the last update relating to bearings with the bike profiles (using “continue_straight” automatically enables these). We already have a fix in place and it will be fixed with the next update which is scheduled for next week
opened 06:10AM - 30 Apr 20 UTC
closed 10:56AM - 24 Mar 21 UTC
bug
#### Here's what I did
Requested a route that made use of the bearings API … parameter, i.e.
```
https://api.openrouteservice.org/v2/directions/cycling-mountain
{
"coordinates": [[8.681495,49.41461],[8.687872,49.420318]],
"bearings": [[25,30],[90,20]]
}
```
---
#### Here's what I got
An error message saying that headings is not supported
```
{
"error": {
"code": 2099,
"message": "Heading is not (fully) supported for CHGraph. See issue #483"
},
"info": {
"engine": {
"version": "6.1.0",
"build_date": "2020-04-27T04:45:15Z"
},
"timestamp": 1588226836862
}
}
```
---
#### Here's what I was expecting
That the routing process takes the preferred bearings into account as has previously been the case
---
#### Here's what I think could be improved
It seems there has been some change in the logic as previously when bearings was passed the system dropped out of using CH as bearings were not possible with that. Now this is not the case and when bearings are provided it does not fall back. This can be seen by adding the `"preference": "shortest"` parameter which then falls out of CH as shortest does not have the CH graph built
Thanks for the reply.
I’ve removed this option, works fine now.