GTFS Realtime - Service Alerts - Metro Train
GTFS Realtime Metro Train Service Alerts data feed provides real time information about disruptions affecting metropolitan train services including cancellations or unforeseen events affecting a station, route or the entire network in Melbourne, Victoria. The feed doesn’t cover train replacement buses, service deviations and platform information. Note: This API endpoint has a rate limit of 20-27 calls per minute (depending on the data size) and caching time of 30 seconds. To obtain an 'API Key' please continue to sign up using our Data Exchange Platform (https://data-exchange.vicroads.vic.gov.au/).
Source
This data file or API can be downloaded from:
https://opendata.transport.vic.gov.au/dataset/2d9a7228-5b81-40d3-8075-ae7a3da42198/resource/6e0a0416-d5a9-4f94-b906-fb757e7478ce/download/gtfsr_metro_train_service_alerts.openapi.jsonResources
There are no views created for this resource yet.
Additional Information
| Field | Value |
|---|---|
| Data last updated | May 30, 2025 |
| Metadata last updated | June 5, 2025 |
| Format | JSON |
| License | Creative Commons Attribution 3.0 Australia |
| Api url | https://data-exchange-api.vicroads.vic.gov.au/opendata/v1/gtfsr/metrotrain-servicealerts |
| Attributes | [{"attribute_display_order_id": 1, "db_format": "FeedHeader()", "db_name": "header", "definition": "Metadata about a feed, included in feed messages.", "fixed_values": "", "id": "7975", "name": "Feed Header", "ref_number": "AT-7975"}, {"attribute_display_order_id": 2, "db_format": "", "db_name": "Feed Message", "definition": "The contents of a feed message. Each message in the stream is obtained as a response to an appropriate HTTP GET request. A realtime feed is always defined with relation to an existing GTFS feed. All the entity ids are resolved with respect to the GTFS feed.", "fixed_values": "", "id": "7976", "name": "Feed Message", "ref_number": "AT-7976"}, {"attribute_display_order_id": 3, "db_format": "STRING()", "db_name": "header.gtfs_realtime_version", "definition": "Version of the feed specification. The current version is 2.0.", "fixed_values": "", "id": "7987", "name": "GTFS Realtime Version", "ref_number": "AT-7987"}, {"attribute_display_order_id": 4, "db_format": "ENUM()", "db_name": "header.incrementality", "definition": "<p>Determines whether the current fetch is incremental. Options include:</p>\n<p>-FULL_DATASET: this feed update will overwrite all preceding realtime information for the feed. Thus this update is expected to provide a full snapshot of all known realtime information.</p>\n<p>-DIFFERENTIAL: currently, this mode is unsupported and behavior is unspecified for feeds that use this mode. There are discussions on the GTFS Realtime mailing list around fully specifying the behavior of DIFFERENTIAL mode and the documentation will be updated when those discussions are finalized.</p>", "fixed_values": "FULL_DATASET, DIFFERENTIAL", "id": "7988", "name": "Incrementality", "ref_number": "AT-7988"}, {"attribute_display_order_id": 5, "db_format": "int64()", "db_name": "header.timestamp", "definition": "This timestamp identifies the moment when the content of this feed has been created (in server time). In POSIX time (i.e., number of seconds since January 1st 1970 00:00:00 UTC). To avoid time skew between systems producing and consuming realtime information it is strongly advised to derive timestamp from a time server. It is completely acceptable to use Stratum 3 or even lower strata servers since time differences up to a couple of seconds are tolerable.", "fixed_values": "", "id": "7989", "name": "Feed Header Timestamp", "ref_number": "AT-7989"}, {"attribute_display_order_id": 6, "db_format": "STRING()", "db_name": "entity.id", "definition": "Feed-unique identifier for this entity. The ids are used only to provide incrementality support. The actual entities referenced by the feed must be specified by explicit selectors (see EntitySelector below for more info).", "fixed_values": "", "id": "7990", "name": "Feed Entity ID", "ref_number": "AT-7990"}, {"attribute_display_order_id": 7, "db_format": "BOOLEAN()", "db_name": "entity.is_deleted", "definition": "Whether this entity is to be deleted. Should be provided only for feeds with Incrementality of DIFFERENTIAL - this field should NOT be provided for feeds with Incrementality of FULL_DATASET.", "fixed_values": "", "id": "7991", "name": "Feed Entity Is Deleted", "ref_number": "AT-7991"}, {"attribute_display_order_id": 8, "db_format": "STRING()", "db_name": "FeedEntity.trip_update", "definition": "Data about the realtime departure delays of a trip. At least one of the fields trip_update, vehicle, alert, or shape must be provided - all these fields cannot be empty.", "fixed_values": "", "id": "8139", "name": "Trip Update", "ref_number": "AT-8139"}, {"attribute_display_order_id": 9, "db_format": "STRING()", "db_name": "FeedEntity.vehicle", "definition": "Data about the realtime position of a vehicle. At least one of the fields trip_update, vehicle, alert, or shape must be provided - all these fields cannot be empty.", "fixed_values": "", "id": "8140", "name": "Vehicle", "ref_number": "AT-8140"}, {"attribute_display_order_id": 10, "db_format": "Alert()", "db_name": "entity.alert", "definition": "An alert, indicating some sort of incident in the public transit network.", "fixed_values": "", "id": "7992", "name": "Feed Entity Alert", "ref_number": "AT-7992"}, {"attribute_display_order_id": 11, "db_format": "TIMERANGE()", "db_name": "alert.active_period", "definition": "Time when the alert should be shown to the user. If missing, the alert will be shown as long as it appears in the feed. If multiple ranges are given, the alert will be shown during all of them. This field can be repeated as many times as needed.", "fixed_values": "", "id": "7993", "name": "Alert Active Period", "ref_number": "AT-7993"}, {"attribute_display_order_id": 12, "db_format": "EntitySelector()", "db_name": "alert.informed_entity", "definition": "Entities whose users we should notify of this alert. At least one informed_entity must be provided. This field can be repeated as many times as needed.", "fixed_values": "", "id": "7996", "name": "Alert Informed Entity", "ref_number": "AT-7996"}, {"attribute_display_order_id": 13, "db_format": "ENUM()", "db_name": "alert.cause", "definition": "<p>Cause of this alert. Options include:</p>\n<p>-UNKNOWN_CAUSE</p>\n<p>-OTHER_CAUSE</p>\n<p>-TECHNICAL_PROBLEM</p>\n<p>-STRIKE</p>\n<p>-DEMONSTRATION</p>\n<p>-ACCIDENT</p>\n<p>-HOLIDAY</p>\n<p>-WEATHER</p>\n<p>-MAINTENANCE</p>\n<p>-CONSTRUCTION</p>\n<p>-POLICE_ACTIVITY</p>\n<p>-MEDICAL_EMERGENCY</p>", "fixed_values": "UNKNOWN_CAUSE, OTHER_CAUSE, TECHNICAL_PROBLEM, STRIKE, DEMONSTRATION, ACCIDENT, HOLIDAY, WEATHER, MAINTENANCE, CONSTRUCTION, POLICE_ACTIVITY, MEDICAL_EMERGENCY", "id": "8008", "name": "Alert Cause", "ref_number": "AT-8008"}, {"attribute_display_order_id": 14, "db_format": "ENUM()", "db_name": "alert.effect", "definition": "<p>The effect of this problem on the affected entity. Options include:</p>\n<p>-NO_SERVICE</p>\n<p>-REDUCED_SERVICE</p>\n<p>-SIGNIFICANT_DELAYS</p>\n<p>-DETOUR</p>\n<p>-ADDITIONAL_SERVICE</p>\n<p>-MODIFIED_SERVICE</p>\n<p>-OTHER_EFFECT</p>\n<p>-UNKNOWN_EFFECT</p>\n<p>-STOP_MOVED</p>", "fixed_values": "NO_SERVICE, REDUCED_SERVICE, SIGNIFICANT_DELAYS, DETOUR, ADDITIONAL_SERVICE, MODIFIED_SERVICE, OTHER_EFFECT, UNKNOWN_EFFECT, STOP_MOVED, NO_EFFECT, ACCESSIBILITY_ISSUE", "id": "7978", "name": "Alert Effect", "ref_number": "AT-7978"}, {"attribute_display_order_id": 15, "db_format": "TranslatedString()", "db_name": "alert.url", "definition": "The URL which provides additional information about the alert.", "fixed_values": "", "id": "7979", "name": "Alert URL", "ref_number": "AT-7979"}, {"attribute_display_order_id": 16, "db_format": "TranslatedString()", "db_name": "alert.header_text", "definition": "Header for the alert. This plain-text string will be highlighted, for example in boldface.", "fixed_values": "", "id": "8011", "name": "Alert Header Text", "ref_number": "AT-8011"}, {"attribute_display_order_id": 17, "db_format": "TranslatedString()", "db_name": "alert.description_text", "definition": "Description for the alert. This plain-text string will be formatted as the body of the alert (or shown on an explicit \"expand\" request by the user). The information in the description should add to the information of the header.", "fixed_values": "", "id": "7982", "name": "Alert Description Text", "ref_number": "AT-7982"}, {"attribute_display_order_id": 18, "db_format": "STRING()", "db_name": "alert.informed_entity.agency_id", "definition": "The agency_id from the GTFS feed that this selector refers to.", "fixed_values": "", "id": "7997", "name": "Alert Informed Entity Agency ID", "ref_number": "AT-7997"}, {"attribute_display_order_id": 19, "db_format": "STRING()", "db_name": "alert.informed_entity.route_id", "definition": "The route_id from the GTFS that this selector refers to. If direction_id is provided, route_id must also be provided.", "fixed_values": "", "id": "7998", "name": "Alert Informed Entity Route ID", "ref_number": "AT-7998"}, {"attribute_display_order_id": 20, "db_format": "int32()", "db_name": "alert.informed_entity.route_type", "definition": "The route_type from the GTFS that this selector refers to.", "fixed_values": "", "id": "7999", "name": "Alert Informed Entity Route Type", "ref_number": "AT-7999"}, {"attribute_display_order_id": 21, "db_format": "TripDescriptor()", "db_name": "alert.informed_entity.trip", "definition": "The trip instance from the GTFS that this selector refers to. This TripDescriptor must resolve to a single trip instance in the GTFS data (e.g., a producer cannot provide only a trip_id for exact_times=0 trips). If the ScheduleRelationship field is populated within this TripDescriptor it will be ignored by consumers when attempting to identify the GTFS trip.", "fixed_values": "", "id": "8001", "name": "Alert Informed Entity Trip", "ref_number": "AT-8001"}, {"attribute_display_order_id": 22, "db_format": "STRING()", "db_name": "alert.informed_entity.stop_id", "definition": "The stop_id from the GTFS feed that this selector refers to.", "fixed_values": "", "id": "7977", "name": "Alert Informed Entity Stop ID", "ref_number": "AT-7977"}, {"attribute_display_order_id": 23, "db_format": "STRING()", "db_name": "alert.informed_entity.trip.trip_id", "definition": "<p>The trip_id from the GTFS feed that this selector refers to. Whether trip_id is required depends on the type of trip:</p>\n<p>- Non-frequency-based trips: The trip_id field alone is enough to uniquely identify these trips. Note that non-frequency-based trips aren't defined in GTFS frequencies.txt.</p>\n<p>- Frequency-based trips: The trip_id, start_time, and start_date fields are all required. Frequency-based trips are defined in GTFS frequencies.txt.</p>\n<p>- Schedule-based trips: The trip_id field can be omitted only if the trip can be uniquely identified by a combination of the provided route_id, direction_id, start_time, and start_date fields. Note that scheduled-based trips aren't defined in GTFS frequencies.txt.</p>", "fixed_values": "", "id": "8002", "name": "Alert Informed Entity Trip ID", "ref_number": "AT-8002"}, {"attribute_display_order_id": 24, "db_format": "STRING()", "db_name": "alert.informed_entity.trip.route_id", "definition": "The route_id from the GTFS feed that this selector refers to. If trip_id is omitted, then route_id, direction_id, start_time, and schedule_relationship=SCHEDULED must all be set to identify a trip instance.", "fixed_values": "", "id": "8003", "name": "Alert Informed Entity Trip Route ID", "ref_number": "AT-8003"}, {"attribute_display_order_id": 25, "db_format": "UINT32()", "db_name": "alert.informed_entity.trip.direction_id", "definition": "<p> The direction_id from the GTFS feed trips.txt file, which indicates the direction of travel. If trip_id is omitted, direction_id must be provided.</p>\n<p>Caution: This field is still experimental and subject to change. It might be formally adopted in the future.</p>", "fixed_values": "", "id": "8004", "name": "Alert Informed Entity Trip Direction ID", "ref_number": "AT-8004"}, {"attribute_display_order_id": 26, "db_format": "STRING()", "db_name": "alert.informed_entity.trip.start_time", "definition": "<p>The initially scheduled start time of this trip instance. The field type Time defines the format of this field, for example 11:15:35 or 25:15:35. Whether the start_time field is required depends on the type of trip:</p>\n<p>\u2022 The trip_id corresponds to a non-frequency-based trip: The start_time field needs to either be omitted or be equal to the value of departure_time in the GTFS feed's stop_times.txt file.</p>\n<p>\u2022 The trip_id corresponds to a frequency-based trip: start_time is always required and must be specified for trip updates and vehicle positions. Frequency-based trips are defined in GTFS frequencies.txt.</p>\n<p>\u25e6 If the frequency-based trip corresponds to an exact_times=1 GTFS record: The start_time field must be some multiple, including zero, of headway_secs later than the frequencies.txt start_time for the corresponding time period.</p>\n<p>\u25e6 If the frequency-based trip corresponds to an exact_times=0 GTFS record: The start_time can be arbitrary, and it's initially expected to be the first departure of the trip. After it's established, the start_time of this frequency-based exact_times=0 trip is considered immutable, even if the first departure time changes. Any subsequent time changes can instead be reflected in a StopTimeUpdate message.</p>\n<p>\u2022 The trip_id is omitted: start_time must be provided.</p>", "fixed_values": "", "id": "8005", "name": "Alert Informed Entity Trip Start Time", "ref_number": "AT-8005"}, {"attribute_display_order_id": 27, "db_format": "STRING()", "db_name": "alert.informed_entity.trip.start_date", "definition": "<p>The start date of this trip instance in YYYYMMDD format. Whether start_date is required depends on the type of trip:</p>\n<p>- Scheduled trips: start_date must be provided. This is to disambiguate trips that are so late that they collide with a scheduled trip on the next day. For example, suppose a train departs at 8:00 and 20:00 every day. If the train is 12 hours late, then there would be two distinct trips scheduled for the same time.</p>\n<p>Note: This field is optional for scheduled trips in which such collisions are impossible. For example, this could happen if a service runs on an hourly schedule, and a vehicle that's one hour late isn't considered related to the schedule anymore.</p>\n<p>- Frequency-based trips: start_date must be provided. Note that frequency-based trips are defined in the GTFS frequencies.txt file, while scheduled trips aren't.</p>\n<p>- trip_id is omitted: start_date must be provided.</p>", "fixed_values": "", "id": "8006", "name": "Alert Informed Entity Trip Start Date", "ref_number": "AT-8006"}, {"attribute_display_order_id": 28, "db_format": "ENUM()", "db_name": "alert.informed_entity.trip.schedule_relationship", "definition": "<p>The relation between this trip and the static schedule. If TripDescriptor is provided in an Alert EntitySelector, the schedule_relationship field is ignored by consumers when they identify the matching trip instance. Options include:</p>\n<p>-SCHEDULED: Trip that is running in accordance with its GTFS schedule, or is close enough to the scheduled trip to be associated with it.</p>\n<p>-ADDED: An extra trip that was added in addition to a running schedule, for example, to replace a broken vehicle or to respond to sudden passenger load.</p>\n<p>-UNSCHEDULED: A trip that is running with no schedule associated to it - this value is used to identify trips defined in GTFS frequencies.txt with exact_times = 0. It should not be used to describe trips not defined in GTFS frequencies.txt, or trips in GTFS frequencies.txt with exact_times = 1.</p>\n<p>-CANCELED: A trip that existed in the schedule but was removed.</p>", "fixed_values": "SCHEDULED, ADDED, UNSCHEDULED, CANCELED, DUPLICATED, DELETED", "id": "8007", "name": "Alert Informed Entity Trip Schedule Relationship", "ref_number": "AT-8007"}, {"attribute_display_order_id": 29, "db_format": "Translation()", "db_name": "alert.header_text.translation", "definition": "A localized string mapped to a language. This field can be repeated as many times as needed.", "fixed_values": "", "id": "8012", "name": "Alert Header Text Translation", "ref_number": "AT-8012"}, {"attribute_display_order_id": 30, "db_format": "STRING()", "db_name": "alert.header_text.translation.text", "definition": "A UTF-8 string containing the message.", "fixed_values": "", "id": "7981", "name": "Alert Header Text Translation Text", "ref_number": "AT-7981"}, {"attribute_display_order_id": 31, "db_format": "STRING()", "db_name": "alert.header_text.translation.language", "definition": "BCP-47 language code. Can be omitted if the language is unknown or if no internationalization is done at all for the feed. At most one translation is allowed to have an unspecified language tag - if there is more than one translation, the language must be provided.", "fixed_values": "", "id": "8013", "name": "Alert Header Text Translation Language", "ref_number": "AT-8013"}] |
| Datastore active | False |
| Datastore contains all records of source file | False |
| Edc sync | True |
| Filesize | 2,498 |
| Has views | False |
| Historical | False |
| Id | 6e0a0416-d5a9-4f94-b906-fb757e7478ce |
| Last updated date | 2 weeks ago |
| Mimetype | application/json |
| Open dataset title | GTFS Realtime - Service Alerts - Metro Train |
| Package id | 53d596e8-7d96-4ef9-85ec-870ace4442fe |
| Position | 4 |
| Publication date | 3 years ago |
| State | active |
| Zip extract | False |
| Size | Unknown |
| ID | 6e0a0416-d5a9-4f94-b906-fb757e7478ce |
| Harvested | True |
| Package ID | 53d596e8-7d96-4ef9-85ec-870ace4442fe |
| State | active |