Is the data for EFA Id to TSN Id mapping up to date?

App development
1

I have curated a list of stop id’s from the gtfs data and using that in the trip planner api (https://api.transport.nsw.gov.au/v1/tp/trip), however I noticed that using those id’s does not provide accurate trip information.

E.g. Seven Hills (StopId - 214732) to Town Hall (StopId - 200070)
The api will stop sending the data for train which coming within 3 mins. However If I use id like 10101234 for Seven hills, I always get accurate data.

  1. Is it advisable to use the stop Ids from gtfs-static data for trip planning apis ?
  2. How can I effectively map between gtfs stop id and the other id ? there are some challenges I am facing while mapping the stop Id data.
    I am looking for Stop EFA ID to TSN Mapping Table data and found this resource:

a.). Was the resource was last updated on August 21, 2023 ?
b.) Can I accurately rely on this data and create mapping from GTFS Stop id data and the Stop Id’s mentioned here?

.
Appreciate any help.

2

Hi,

I want to clarify that you should be using the parent ID from the GTFS data.

The stop ID you mentioned for Seven Hills (214732) corresponds to Platform 3, so results will only be returned from that specific platform. If you use the Seven Hills parent ID – 214710, you’ll receive the same results as when using 10101234.

Please avoid using EFA IDs (e.g., 10101234) going forward. These are internal system IDs that can change without notice and shouldn’t be relied upon.

Let me know if you have any questions.
Regards,
Suraj

2 Likes
3

Thanks for chasing @Suraj!

For everyone’s benefit - we’ve removed the Stop EFA to TSN Mapping Table excel file from this dataset at the request of the Data Owners.

Thanks!

1 Like