Skip to content

NEGATIVE_HOP_TIME on a real-time feed containing only arrival times but not departure times on stops after extended dwell #6391

Open
@miklcct

Description

@miklcct

Expected behavior

The update can be parsed with only arrival times given. The spec does not require both arrival and departure to be given, only either of them.

Observed behavior

A lot of trip updates fail with NEGATIVE_HOP_TIME if the bus is running late across an extended dwell.

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

2.7.0-SNAPSHOT

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

GTFS data for Uno buses and predictions generated by TheTransitClock.

Command line used to start OTP

Router config and graph build config JSON

Steps to reproduce the problem

  1. Run Transitime using a GTFS file of an agency and a GTFS-RT containing the bus positions for that agency, matched to the trips correctly.
  2. Run OpenTripPlanner with the same GTFS file, and a trip updater connected to the API output for the GTFS-RT predictions from Transitime.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions