Mystery stop id in realtime bus feed

Real-time Public Transport
1

Hi all,

Just found a bug where the realtime data feed returns a stop ID that’s not listed in the GTFS static (nor the new Trip Planner API).

For trip 387374, stop 202198 has been added to the stopping pattern, listed as stop_sequence 3.

The GTFS-static data shows 3 stops, instead of the 4 reported by realtime:

| SEQ | GTFS-static stops | GTFS-realtime stops |
|  1  | 2031163           | 2031163             |
|  2  | 2031164           | 2031164             |
|  3  | 200039            | 202198              |
|  4  |                   | 200039              |

This is not exclusive to the 895 route. Just a few examples:

  • Trip 145462, bus route L94, reports an additional stop (202199)
  • Trip 285603, bus route 377, reports an additional stop (2031190)

The GTFS-realtime decoded entity for the first example is below:

entity {
  id: "11954_142497141_2441_895_1"
  trip_update {
    trip {
      trip_id: "387375"
      start_time: "17:46:00"
      start_date: "20170120"
      schedule_relationship: SCHEDULED
      route_id: "2441_895"
    }
    stop_time_update {
      stop_sequence: 3
      arrival {
        delay: 37
        time: 1484895277
      }
      departure {
        delay: 45
        time: 1484895285
      }
      stop_id: "202198"
      schedule_relationship: SCHEDULED
    }
    stop_time_update {
      stop_sequence: 4
      arrival {
        delay: 186
        time: 1484895726
      }
      departure {
        delay: 223
        time: 1484895763
      }
      stop_id: "200039"
      schedule_relationship: SCHEDULED
    }
    vehicle {
      id: "11954_142497141_2441_895_1"
      tfnsw_vehicle_descriptor {
        air_conditioned: true
        wheelchair_accessible: 1
        special_vehicle_attributes: 0
      }
    }
    timestamp: 1484895215
  }
}
1 Like
2

Hi @jxeeno, we found that this is a problem with the feed. The buses feed team is investigating and aiming to resolve as soon as possible. I’ll keep you up to date.

Thanks,
Alex

1 Like
3

Thanks for responses alex!

4

Interesting. After two years later, I found this is still happening! Is it only me? How to deal with stop_id from realtime data, which is not in stops.txt?

5

Yeah, it still happens (but to a lesser extent). We just skip any stops we don’t know about.

1 Like
6

Thanks, @jxeeno!