GTFS-RT - Far West incorrect TripID

1

Hi,

Just want to report that the Far West FW GTFS-RT bus feeds for CDC Broken Hill are reporting incorrect TripID’s to the real-time feed. Those vehicles/services are reporting TripId’s to the feed for example as Trip ID: 165335190001:33416881 where as the Trip ID for the equivalent trip is stored in the static FW GTFS trips.txt as for example 2463631 - this results in a mismatch and for some third-party apps results in these services not showing real-time information.

This is also not a one off - all services for CDC Broken Hill are consistently reporting these malformed tripids for all routes and all days.

Also, a less critical issue more of an observation, TrainLink services operated by RoadCoach are reporting malformed vehicle identifiers in that real-time feed, for example, usual vehicles in the feed will have a licence_plate like 1234MO for example, these vehicles have an id for example 355353351471374. This is only an observation, it doesn’t appear to affect the tracking of these vehicles that i am aware of.

Thank you

1 Like
2

Hi @james00 ,

thank you for reporting this. We do occasionally see those incorrect TripID’s for our TCB feeds. I will let the team know about the Broken Hill TripIDs.

Will have a look into the Coach IDs of NSW Trains.

3

Hi Marcie,

Thanks for the reply. Could you also please note that Albury services (Dysons Buslines) – specifically routes 901, 902, and 903 – do not appear in the real-time GTFS feed on most days. The last time I saw these in the feed was 8th June, and even before then, their presence was sporadic.

Let me know if you need further details.

Thanks,
James

1 Like
4

Hi,

Just confirming the TripIDs now appear correctly in the feed for CDC Broken Hill—thanks for sorting that out.

However, I’ve noticed that for routes 590, 591, 592, and 593:

  • The TripIDs in the real-time feed look normal,
  • But those TripIDs (and the routes themselves) aren’t present in the static GTFS files—neither in trips.txt nor routes.txt.

Could you please look into this also?

Thanks,
James

5

Thanks, James, for your feedback. We are investigating the issue. We will update you once it has been fixed.