> One thing that was a bit irritating was the directions at intersections, where you clearly had to go straight, but it told me to turn right and then immediately turn left. This happened when the bike path took a slight turn before the intersection, e.g. to guide you towards pedestrian traffic lights. Not sure which one of the two apps is to blame here.
It's your workflow that's to blame: using a GPX erases that information. If you'd planned the route in OSMAnd it would have been able to give you more road-layout-aware navigation.
I see, I'll play around with it a little more then. The thing is that the OSMAnd route looked way worse, and from using it on shorter routes occasionally I didn't really trust it.
Yeah, OSMAnd's built-in routing isn't great. But anything based around exporting a GPX from one app and using it in another is going to have the problem you describe; the only way to avoid it is to find an all-in-one app that's good enough on all fronts (or possibly use a fancier format like TCX).
TCX sounds cool, and apparently it's going to be supported in the next release of openrouteservice [1]. Looking forward to that, since the route itself was pretty solid.
It's your workflow that's to blame: using a GPX erases that information. If you'd planned the route in OSMAnd it would have been able to give you more road-layout-aware navigation.