GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.0.0 at 2025-05-17T07:56:01Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Summary

Agencies included

BFC SUD
- website: https://www.transdev.com/fr/nos-activites-en-france/transdev-bourgogne-franche-comte/
- 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:
2024-09-01 to 2025-08-31 (?) 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
routes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 4
Shapes: 0
Stops: 42
Trips: 129

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

Route Colors Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed

Specification Compliance report

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

Notice Code

Severity

Total

missing_recommended_file

WARNING

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"

mixed_case_recommended_field

WARNING

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
`Field Text`	`Dataset`
"Schwerin, Hauptbahnhof"	Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin"	NYC Ferry
"Campo Grande Norte"	Carris

Bad examples:
`Field Text`
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"agency.txt"	"agency_name"	"BFC SUD"	2
"stops.txt"	"stop_name"	"AUTUN - POPA"	22

unexpected_enum_value

WARNING

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row number of the faulty record.	fieldName (?) The name of the field where the error occurred.	fieldValue (?) Faulty value.
"routes.txt"	3	"route_type"	715
"routes.txt"	4	"route_type"	715
"routes.txt"	5	"route_type"	715