The trip identifiers in the Realtime Transit Feed (GTFS) are using the old identifier type, not the current one used in the static GTFS

The trip identifiers in the Realtime Transit Feed (GTFS) are using the old identifier type, not the current one used in the static GTFS (https://gtfs.at.govt.nz/gtfs.zip). Is there a service for converting the old identifiers into the new format? Are you planning to update your realtime API to support the new format? Cheers, Matt

Comments

  •  
    Hi, here is the reply from our developers. For now you can use the 'Realtime Compact' API as this uses the new ID as query parameter and in response. As a note, we are moving away from using the old ids, but for now this would be the way to go. There is no estimation of when this will be completed. The migration is still in progress and is done progressively. Thank you.
    Posted by Hidden Fri, 09 Dec 2022 01:52:39 GMT
  •  
    Just to confirm - the Realtime Compat legacy endpoint is using the new identifiers, and the current Realtime Transit Feed is using the old identifiers? Is the legacy endpoint likely to be decommissioned any time soon?
    Posted by Hidden Fri, 09 Dec 2022 02:24:07 GMT
  •  
    Hi, The Realtime Compact API uses new IDs. APIs using old IDs will be decommissioned once the migration is completely done. Thanks and hope that answers the question.
    Posted by Hidden Fri, 09 Dec 2022 03:43:32 GMT
  •  
    Thanks for the quick reply! I'll stop using the endpoints that provide the old identifiers and migrate to the new ones.
    Posted by Hidden Fri, 09 Dec 2022 04:41:03 GMT


You're not signed in. Please sign-in to report an issue or post a comment.