Improving Tram Destination Information
New information included in the ‘GTFS Schedule’ dataset
Tram destination text has been improved for open data so third-party journey planning apps can show more accurate end of trip information. This will now match displays and screens on trams.
The following GTFS Schedule dataset changes have been made:
- Improved tram destination text in the trips.txt->’trip_headsign' field
- Adjusted ‘trip_id’ as part of our back-end system improvements to improve the stability of our timetable and real-time data feeds
- Updated ‘route_id’ with a new pattern and removing duplications in the routes.txt file
These changes have been made because it is common for tram trips on Melbourne’s extensive tram network to terminate early to make the best use of the system. Currently, open data for third-party journey planning apps have only provided end-of-route information, so it can be unclear if trips are ending earlier.
For example, on the number 70 tram route, some trips finish at Camberwell Tram Depot even though the end of the route is at Docklands. Similarly, on the number 16 tram route, some trips finish at Malvern Tram Depot even though the end of the route is at Kew.
We want to provide more accurate and consistent information to ensure passengers get to their final destination with confidence.
What are the benefits?
ü Third-party journey planning apps and tools will have more accurate end of tram trip information that matches displays and screens on trams. This will help passengers to more accurately plan their journey no matter which app or tool they prefer to use.
ü Passengers will be well informed about finding out when tram trips end short, promoting a reliable and seamless journey experience.
When will these changes take effect?
This update was released on 7 March 2025