In hafas-client, the HAFAS client underlying v6.db.transport.rest & v5.db.transport.rest, I have changed the default rtMode (routing mode of the HAFAS engine) from "hybrid" routing to "realtime" routing: public-transport/hafas-client@3c17678d. This change has been done in hafas-client@6 only, so that explains why the pagination is only broken in v6.db.transport.rest.

The ticket in the hafas-client repo proposes adding an option to hafas-clients's journey() method, which could then be exposed here in db-rest. Then, we should also clearly document the effects of the realtimeRouting option.

TLDR: blocked by public-transport/hafas-client#287

I have published the fix (#295) as [email protected]. 🎉

public-transport/hafas-client#287 (comment)

This is unblocked now. What needs to be done here:

• expose the opt.routingMode option as a query parameter, in mapRouteParsers()
• document that the query parameter exists, and link to the hafas-client docs
• document that the trade-off: realtime routing per default and with routingMode= REALTIME; working pagination with e.g. routingMode= HYBRID

Is there work in progress for this? If not, I might try looking into it, since it's affecting my usecase.

Is there work in progress for this?

None that I know of.