Home
France Feeds
donnessta-3
Source Data Validation Report

donnessta-3 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T22:26:36Z,
for the dataset file:///shared/donnessta-3_db391e03.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

SNT SUMA
- website: https://www.suma.fr/
- 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:
2025-06-21 to 2025-09-15 (?) 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
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 2
Shapes: 7
Stops: 27
Trips: 19

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

ShapesRoute ColorsHeadsigns

Specification Compliance report

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

Notice Code Severity Total

expired_calendar WARNING 2

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	"LIGNE 1"
3	"LIGNE 2"

missing_recommended_file WARNING 1

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"

missing_timepoint_value WARNING 253

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

Only the first 50 of 253 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's `stop_times.trip_id`.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2	"1"	0
3	"1"	1
4	"1"	2
5	"1"	3
6	"1"	4
7	"1"	5
8	"1"	6
9	"1"	7
10	"1"	8
11	"1"	9
12	"1"	10
13	"1"	11
14	"1"	12
15	"1"	13
16	"1"	14
17	"1"	15
18	"1"	16
19	"1"	17
20	"1"	18
21	"1"	19
22	"10"	0
23	"10"	1
24	"10"	2
25	"10"	3
26	"10"	4
27	"10"	5
28	"10"	6
29	"10"	7
30	"10"	8
31	"10"	9
32	"10"	10
33	"10"	11
34	"10_0"	0
35	"10_0"	1
36	"10_0"	2
37	"10_0"	3
38	"10_0"	4
39	"10_0"	5
40	"10_0"	6
41	"10_0"	7
42	"10_0"	8
43	"10_0"	9
44	"10_0"	10
45	"10_0"	11
46	"10_0_0"	0
47	"10_0_0"	1
48	"10_0_0"	2
49	"10_0_0"	3
50	"10_0_0"	4
51	"10_0_0"	5

mixed_case_recommended_field WARNING 21

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"	"SNT SUMA"	2
"stops.txt"	"stop_name"	"PORT GRIMAUD 1 PLAGE"	2
"stops.txt"	"stop_name"	"CAMPING CHARLEMAGNE"	3
"stops.txt"	"stop_name"	"HAMEAU DE LA TOURRE"	4
"stops.txt"	"stop_name"	"HAMEAU VAL DE GILLY"	5
"stops.txt"	"stop_name"	"PORT GRIMAUD POTERNE"	6
"stops.txt"	"stop_name"	"PORT GRIMAUD ECHANGEUR"	7
"stops.txt"	"stop_name"	"LES BLAQUIERES"	8
"stops.txt"	"stop_name"	"LA RINE"	10
"stops.txt"	"stop_name"	"COOPERATIVE/GENDARMERIE"	11
"stops.txt"	"stop_name"	"VILLAGE MAIRIE CABRE D’OR"	12
"stops.txt"	"stop_name"	"OFFICE DE TOURISME"	13
"stops.txt"	"stop_name"	"CAMP MARIN"	15
"stops.txt"	"stop_name"	"ROND POINT COOPERATIVE"	16
"stops.txt"	"stop_name"	"LA PINEDE"	18
"stops.txt"	"stop_name"	"LA QUESTE"	19
"stops.txt"	"stop_name"	"LES BASTIDES"	20
"stops.txt"	"stop_name"	"LES CAGNIGNONS"	21
"stops.txt"	"stop_name"	"LES COUZES"	22
"stops.txt"	"stop_name"	"LES MÛRIERS"	23
"stops.txt"	"stop_name"	"MAISON COMMUNE"	25

non_ascii_or_non_printable_char WARNING 9

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

filename (?) Name of the faulty file.	csvRowNumber (?) Row number of the faulty record.	columnName (?) Name of the column where the error occurred.	fieldValue (?) Faulty value.
"stops.txt"	23	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	25	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	37	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	49	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	61	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	78	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	90	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	102	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	114	"stop_id"	"LES MÛRIERS"

route_long_name_contains_short_name WARNING 1

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`.
"1"	2	"1"	"1 Navette GRIMAUD"

trip_coverage_not_active_for_next7_days WARNING 1

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.
"20260323"	"20250701"	"20250831"