When doing a trip seach in OTP we get back a token to navigate the the next/previous page. We sometimes get duplicate itineraries when going back or forward.
This is related to issue #3382
More information on the paging functionality is in the design doc.
Example
From: Rindal, (63.05502, 9.21167), NSR:StopPlace:41497
To: Studentersamfundet Trondheim, (63.42030, 10.38933), NSR:StopPlace:42660
Time: Working day 20:00
ArriveBy: true
Adjusting the searchWindow does not seem to have any effect. One(3600s) and two(7200s) hours give the same result.
Introduction
When doing a trip seach in OTP we get back a token to navigate the the next/previous page. We sometimes get duplicate itineraries when going back or forward.
This is related to issue #3382
More information on the paging functionality is in the design doc.
Example
From: Rindal, (63.05502, 9.21167), NSR:StopPlace:41497 To: Studentersamfundet Trondheim, (63.42030, 10.38933), NSR:StopPlace:42660 Time: Working day 20:00 ArriveBy: true Adjusting the
searchWindow
does not seem to have any effect. One(3600s) and two(7200s) hours give the same result.GraphQL Querry
In OTP Debug it looks like this:
Version of OTP used (exact commit hash or JAR name)
OTP2
Data sets in use (links to GTFS and OSM PBF files)
Norway
Steps to reproduce the problem
previousPageCursor
topageCursor