ptv-regional-train — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T16:36:54Z,
for the dataset file:///shared/ptv-regional-train_ee6b12db.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Agencies included
- Transport Victoria
- website: https://transport.vic.gov.au/?utm_source=open_data_click_agency&utm_medium=open_data_agency_click&utm_campaign=open_data_click
- phone number:
- email: Not provided
Feed Info
- Publisher Name:
- N/A
- Publisher URL:
- N/A
- Feed Email:
- N/A
- Feed Language:
- N/A
- Service Window:
- 2026-06-18 to 2026-09-20 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt
Files included
- agency.txt
- calendar.txt
- calendar_dates.txt
- levels.txt
- pathways.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- transfers.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 0
- Routes: 13
- Shapes: 1177
- Stops: 641
- Trips: 4709
Specification Compliance report
142 notices reported (1 errors, 141 warnings, 0 infos)
| Notice Code | Severity | Total | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| number_out_of_range | ERROR | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
number_out_of_rangeOut of range value. The values in the given column of the input rows are out of range. You can see more about this notice here.
expired_calendar | WARNING | 1 | expired_calendarDataset should not contain date ranges for services that have already expired. This warning takes into account the You can see more about this notice here.
leading_or_trailing_whitespaces | WARNING | 4 | leading_or_trailing_whitespacesThe value in CSV file has leading or trailing whitespaces. This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser. The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces. You can see more about this notice here.
missing_recommended_field | WARNING | 13 | missing_recommended_fieldA recommended field is missing. The given field has no value in some input row, even though values are recommended. You can see more about this notice here.
missing_recommended_file | WARNING | 1 | missing_recommended_fileA recommended file is missing. You can see more about this notice here.
route_long_name_contains_short_name | WARNING | 5 | route_long_name_contains_short_nameLong name should not contain short name for a single route. In routes.txt, Good examples:
Bad examples:
You can see more about this notice here.
stop_without_stop_time | WARNING | 117 | stop_without_stop_timeA stop in Such stops are not used by any trip and normally do not provide user value. This notice may
indicate a typo in You can see more about this notice here. Only the first 50 of 117 affected records are displayed below.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||