Expected behavior

The estimated times given in GTFS-RT feeds are used and exposed in the API.

Observed behavior

The estimated time returned in the API is not equal to the time given in GTFS-RT feed if the stop is skipped.

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

2.9.0-SNAPSHOT

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

A feed which contains estimated times for skipped stops in GTFS-RT.

Command line used to start OTP

Router config and graph build config JSON

Steps to reproduce the problem

Run the following GraphQL query at a stop which is skipped by some services

query GtfsExampleQuery {
  stop(id:"GB:9100STPXBOXA") {
    stoptimesWithoutPatterns(omitCanceled: false) {
      trip {
        gtfsId
        tripShortName
        routeShortName
      }
      headsign
      scheduledArrival
      scheduledDeparture
      realtimeArrival
      realtimeDeparture
      realtimeState
    }
  }
}