Expected behavior

When using the transit-group-priority feature we expect all optimal results to be listed - acknowlaging the cost slak function provided.

Observed behavior

Setting the Relax Transit Group Priority in the request have no effect. This can be demonstrated with a search from Trondheim to Steinkjær. If we turn off coach vi get this result:

If we turn it on, we get this:

What happens (after som debugging) is that the 15:13 departure is rejected when arriving Levanger station, because of the heuristic. The 15:26 coach has arrived and dominate the 15:13, since the c2 criteria is not checked.

Version of OTP used (exact commit hash or JAR name)

dev-2.x

Data sets in use (links to GTFS and OSM PBF files)

Arkiv.zip

(Stops are not included, stops for Trøndelag and RailWay stops for Norway is needed in addition).

Router config and graph build config JSON

Entur PROD (2025-12-03)