GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-24T13:17:28Z,
for the dataset file:///shared/ccgq_f292d9bb.zip. No country code was provided.

Summary

Agencies included

CCGQ
- website: https://www.ccguillestroisqueyras.fr/vivre/deplacements/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
CC du Guillestrois et du Queyras: Publisher URL:
https://www.ccguillestroisqueyras.fr/vivre/deplacements/: Feed Email:
pablo.bedek@comcomgq.com: Feed Language:
French: Feed Start Date:
2025-12-01: Feed End Date:
2026-09-07: Service Window:
2025-12-20 to 2026-09-06 (?) 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
booking_rules.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
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 15
Shapes: 53
Stops: 134
Trips: 254

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

Shapes Frequencies Feed Information Fares V1 Booking Rules Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

15 notices reported (0 errors, 15 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	"20251221_20260322_lmmjvsd"
3	"20251221_20260104_lmmjvsd"
4	"20260207_20260308_lmmjvsd"
5	"20251220_20260104_lmmjvsd"
6	"20260105_20260206_lmmjvsd"
7	"20260309_20260322_lmmjvsd"
8	"20260323_20260327_lmmjv--"
9	"20260328_20260329_-----sd"
10	"20251223_20251231_-mm----"
11	"20260210_20260305_-mm----"
12	"20251225_20260319_---j---"

route_color_contrast

WARNING

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"CCGQLIGNE0023"	2	"#FBBA00"	"#FFFFFF"
"CCGQLIGNE0029"	8	"#FFCC00"	"#FFFFFF"
"CCGQLIGNE0016"	15	"#FBBA00"	"#FFFFFF"

route_long_name_contains_short_name

WARNING

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"CCGQLIGNE0011"	12	"Guillestre"	"Guillestre - Eygliers - Montdauphin"