SydneyBuses GTFS RT broken for 3 days now?

Real-time Public Transport
1

It seems that the SydneyBuses GTFS realtime feed is no longer working properly.

For 3 days, we have not seen any live bus times in the Google Maps, TripChecker or CityMapper apps.

Is the issue related to this forum post about trip_ids ?

This appears to be an extremely critical issue, so we’re confused why there has been no forum replies, no announcements and no fix. Please respond!

1 Like
2

Hi @urbanthings, the feed seems to be up and working correctly. Can you please provide more details on how it’s not working properly so we can look into it further?

3

Thanks for the reply Alejandro. As per this other forum post we believe that the issue is all the trip_ids are either missing or no longer correlate with scheduled trips.

It can’t be a coincidence that none of the major apps, ours included, are displaying live bus times for the last couple of days!

4

Hi @alejandro.felman. We are seeing trip updates come through, but mostly with missing trip ids, which means that we are unable to link them to the schedule data, and thus we cannot display real time information to our users.

We are currently seeing around 3930 trip updates, of which 3094 are missing trip_ids, yet with a schedule relationship of ‘SCHEDULED’. An example of the feed content, showing missing trip_ids, is below:

 header {
  gtfs_realtime_version: "1.0"
  incrementality: FULL_DATASET
  timestamp: 1473841575
}
entity {
  id: "33553_11256226_2436_T66_1"
  trip_update {
    trip {
      start_time: "18:10:00"
      start_date: "20160914"
      schedule_relationship: SCHEDULED
      route_id: "2436_T66"
    }
    stop_time_update {
      stop_sequence: 2
      arrival {
        delay: 843
        time: 1473841623
      }
      departure {
        delay: 865
        time: 1473841645
      }
      stop_id: "2150300"
      schedule_relationship: SCHEDULED
    }
    stop_time_update {
      stop_sequence: 3
      arrival {
        delay: 703
        time: 1473841723
      }
      departure {
        delay: 742
        time: 1473841762
      }
      stop_id: "214511"
      schedule_relationship: SCHEDULED
    }

... snip ...

    vehicle {
      id: "33553_11256226_2436_T66_1"
      1999: "\b\000\020\000"
    }
    4: 1473841572
  }
}
entity {
  id: "33553_11258243_2436_T66_1"
  trip_update {
    trip {
      start_time: "17:50:00"
      start_date: "20160914"
      schedule_relationship: SCHEDULED
      route_id: "2436_T66"
    }
    stop_time_update {
      stop_sequence: 19
      arrival {
        delay: 154
        time: 1473841714
      }
      departure {
        delay: 179
        time: 1473841739
      }
      stop_id: "2155224"
      schedule_relationship: SCHEDULED
    }
    stop_time_update {
      stop_sequence: 20
      arrival {
        delay: 156
        time: 1473841776
      }
      departure {
        delay: 182
        time: 1473841802
      }
      stop_id: "2155195"
      schedule_relationship: SCHEDULED
    }
    stop_time_update {
      stop_sequence: 21
      arrival {
        delay: 182
        time: 1473841862
      }
      departure {
        delay: 204
        time: 1473841884
      }
      stop_id: "2155379"
      schedule_relationship: SCHEDULED
    }
    stop_time_update {
      stop_sequence: 22
      arrival {
        delay: 161
        time: 1473841901
      }
      departure {
        delay: 202
        time: 1473841942
      }
      stop_id: "2155380"
      schedule_relationship: SCHEDULED
    }

... snip ...

    vehicle {
      id: "33553_11258243_2436_T66_1"
      1999: "\b\000\020\000"
    }
    4: 1473841560
  }
}

... snip ...
5

thanks guys, we’re looking into it and will get back to you.

6

Hi @urbanthings, @david.else, this has been resolved so you should see trip ids in the buses feed again. Please let us know if it’s still not correct.

Thanks

1 Like
7

Hi @alejandro.felman. That looks much happier now, thanks very much for looking into it!