Data
Viewed: [[ro.stat.viewed]] Cited: [[ro.stat.cited]] Accessed: [[ro.stat.accessed]]
ctx_ver=Z39.88-2004&rft_val_fmt=info%3Aofi%2Ffmt%3Akev%3Amtx%3Adc&rfr_id=info%3Asid%2FANDS&rft_id=http://discover.data.vic.gov.au/dataset/gtfs-realtime&rft.title=GTFS Realtime&rft.identifier=http://discover.data.vic.gov.au/dataset/gtfs-realtime&rft.publisher=data.vic.gov.au&rft.description=GTFS Realtime feeds have been provided by the Victoria Department of Transport and Planningto provide realtime updates about Public Transport services. It contains feeds about:* **Trip Updates** \\- delays, cancellations, changed routes* **Service Alerts** \\- stop moved, unforeseen events affecting a station, route or the entire network* **Vehicle Positions** \\- information about the vehicles including location and congestion level Please note these feeds are provided in the Protocol Buffer format and are not human readable.For more information refer to this GTFS Realtime page () which is maintained by MobilityData () and facilitates the GTFS and GTFS\\-R specification. **Summary of Changes****GTFS\\-R \\- Trip Updates \\- Metro Train:** Schedule Relationships, Stop ID, and Route ID have been added as additional fields to enhance real\\-time trip accuracy. **GTFS\\-R \\- Vehicle Positions \\- Metro Train:** Route ID added as a Conditionally Required field to improve data details. **GTFS\\-R \\- Service Alerts \\- Metro Train:** Additional information about planned and unplanned disruptions have been added to include more details about delays and bus replacement services. Route ID and Direction ID are two new fields that have been added also.  **Why are these changes being made?**These changes are being made to:* Create consistent and accurate real\\-time transport information for open data users.* Improve trip planning and data usability by better aligning static and real\\-time datasets. **NOTE:** * The API Key is to be used in the request header. Header name is 'KeyID'.* API endpoint rate limit \\- Metro Train (24 calls per 60 seconds), Tram (24 calls per 60 seconds), Bus (24 calls per 60 seconds)* Data Refresh rate \\- (Metro Train \\- Near real\\-time), (Tram \\- Every 60 seconds), (Bus \\- Near real\\-time)&rft.creator=Anonymous&rft.date=2025&rft_rights=Creative Commons Attribution 4.0 International https://creativecommons.org/licenses/by/4.0/&rft_subject=gtfs realtime&rft_subject=gtfs-r&rft_subject=public transport&rft_subject=service alerts&rft_subject=trip update&rft_subject=vehicle position&rft.type=dataset&rft.language=English Access the data

Licence & Rights:

Open Licence view details
CC-BY

Creative Commons Attribution 4.0 International
https://creativecommons.org/licenses/by/4.0/

Access:

Open

Brief description

GTFS Realtime feeds have been provided by the Victoria Department of Transport and Planning

to provide realtime updates about Public Transport services. It contains feeds about:

* **Trip Updates** \\- delays, cancellations, changed routes
* **Service Alerts** \\- stop moved, unforeseen events affecting a station, route or the entire network
* **Vehicle Positions** \\- information about the vehicles including location and congestion level

 

Please note these feeds are provided in the Protocol Buffer format and are not human readable.

For more information refer to this GTFS Realtime page () which is maintained by MobilityData () and facilitates the GTFS and GTFS\\-R specification.




**Summary of Changes**

**GTFS\\-R \\- Trip Updates \\- Metro Train:** Schedule Relationships, Stop ID, and Route ID have been added as additional fields to enhance real\\-time trip accuracy. 

**GTFS\\-R \\- Vehicle Positions \\- Metro Train:** Route ID added as a Conditionally Required field to improve data details. 

**GTFS\\-R \\- Service Alerts \\- Metro Train:** Additional information about planned and unplanned disruptions have been added to include more details about delays and bus replacement services. Route ID and Direction ID are two new fields that have been added also. 

 

**Why are these changes being made?**

These changes are being made to:

* Create consistent and accurate real\\-time transport information for open data users.
* Improve trip planning and data usability by better aligning static and real\\-time datasets.




**NOTE:** 

* The API Key is to be used in the request header. Header name is 'KeyID'.
* API endpoint rate limit \\- Metro Train (24 calls per 60 seconds), Tram (24 calls per 60 seconds), Bus (24 calls per 60 seconds)
* Data Refresh rate \\- (Metro Train \\- Near real\\-time), (Tram \\- Every 60 seconds), (Bus \\- Near real\\-time)

Created: 2025-05-30

This dataset is part of a larger collection

Click to explore relationships graph
Subjects

User Contributed Tags    

Login to tag this record with meaningful keywords to make it easier to discover

Identifiers