Odd routing / 500s from Mission to Wildcat Canyon

[graue]

I'm getting a bunch of 500 errors, depending on time of arrival, and weird routes when I route from the Mission to Wildcat Canyon.

Weird route example, go all the way to Orinda and bike over enormous hills:

I think the weird routes are partly OSM's fault -- looking up "Wildcat Canyon" gets the centroid(?) of the park, way up in the hills, not the park entrance. But the 500s are strange.

I also just got another 500 after dragging the destination point to the actual park entrance. This: https://api.bikehopper.org/v1/graphhopper/route-pt?locale=en-US&elevation=true&useMiles=false&layer=OpenStreetMap&profile=pt&optimize=true&pointsEncoded=false&pt.earliest_departure_time=2022-05-29T16:42:00.000Z&pt.connecting_profile=bike2&pt.arrive_by=true&details=cycleway&details=road_class&point=37.75993,-122.41914&point=37.95253,-122.32181

If you just do "Mission District" to "Wildcat Canyon", arrive by 9:42am Friday, it also 500s

Good route after dragging point and setting arrival time to 9:32am Sun but if I set the arrival time to between 9:33am and 9:39am inclusive then it 500s:

[graue]

Update: here is the stack trace for one of the errors.

https://gist.github.com/graue/2e3dadb9002e0610922aef7fae872651

How I found this: there's a "message" in the error response that tells you the error was logged and includes an ID

$ kubectl get pods -n production|grep graphhopper

(two instances will be listed; guess which one and you'll be right half the time)

$ kubectl logs graphhopper-deployment-xxxxxxxxx-yyyyy -n production | grep ID-from-JSON-response

[graue]

Closing as a duplicate in favor of

• For the router bug: #68
• For the geolocation issue with Wildcat Canyon Regional Park: https://github.com/bikehopper/bikehopper-ui/issues/156