We have multiple routing requests within a single request to handle walking bikes: see bikeWalkingOptions in RoutingRequest. I believe this is a remnant of a past era when RoutingRequests only contained a few options for traversing streets.

Besides being a bit strange semantically, this creates concerns about recursively calling methods. Might it make more sense to have parameters for how much slower/harder walking a bike is and keep them in the main RoutingRequest?

Also: for some reason bicycle walking options are being created when getDriving() is true. Why is this?