GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T19:52:26Z,
for the dataset file:///shared/byroneasybus.zip. No country code was provided.

Summary

Agencies included

Byron Easybus
- website: https://www.byronbayshuttle.com.au/?utm_source=AddTransit&utm_medium=GTFS
- phone number: 61 (0)2 6685 7447
- email: info@byronbus.com

Feed Info

Publisher Name:
AddTransit: Publisher URL:
https://addtransit.com: Feed Email:
N/A: Feed Language:
English: Feed Start Date:
N/A: Feed End Date:
N/A: Service Window:
2016-04-03 to 2020-04-04 (?) 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
fare_attributes.txt
fare_rules.txt
feed_info.txt
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
transfers.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 9
Shapes: 0
Stops: 27
Trips: 142

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Feed Information Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

33 notices reported (0 errors, 33 warnings, 0 infos)

Notice Code

Severity

Total

expired_calendar

WARNING

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"1"
3	"2"
4	"4"
5	"3"
6	"5"
7	"6"
8	"7"
9	"8"
10	"9"
11	"10"
12	"11"
13	"12"
14	"13"
15	"14"
16	"15"
17	"16"
18	"17"
19	"18"
20	"19"
21	"20"
22	"21"
23	"22"
24	"23"
25	"24"

missing_feed_contact_email_and_url

WARNING

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2

missing_recommended_field

WARNING

missing_recommended_field

A 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.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"feed_info.txt"	2	"feed_start_date"
"feed_info.txt"	2	"feed_end_date"

stop_without_stop_time

WARNING

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
7	"14"	"Casuarina (Southbound)"
18	"24"	"Kingscliff (Southbound)"
20	"26"	"Chinderah (Southbound)"
22	"28"	"Pottsville (Southbound)"
25	"5"	"Hastings Point (Southbound)"

trip_coverage_not_active_for_next7_days

WARNING

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20251212"	"20160403"	"20191005"