GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T18:39:12Z,
for the dataset file:///shared/tam2.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
STGA
Publisher URL:
http://www.stga.fr/
Feed Email:
N/A
Feed Language:
French
Feed Start Date:
2021-07-07
Feed End Date:
2022-07-02

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 58
  • Shapes: 217
  • Stops: 1940
  • Trips: 10145

Specification Compliance report

51 notices reported (0 errors, 48 warnings, 3 infos)

Notice Code Severity Total
expired_calendar WARNING 15

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 "10"
4 "1000"
5 "1001"
6 "11"
7 "12"
8 "13"
9 "2"
10 "3"
11 "4"
12 "5"
13 "6"
14 "7"
15 "8"
16 "9"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260123" "20220702" "20260130"
leading_or_trailing_whitespaces WARNING 2

leading_or_trailing_whitespaces

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

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 743 "stop_desc" "Poteau,Banc "
"stops.txt" 889 "stop_desc" "Abri G.A,Poteau,Banc,Borne "
missing_feed_contact_email_and_url WARNING 1

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
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.
"20260123" "20210901" "20220706"
unexpected_enum_value WARNING 28

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" 19 "route_type" 700
"routes.txt" 20 "route_type" 700
"routes.txt" 21 "route_type" 700
"routes.txt" 22 "route_type" 700
"routes.txt" 23 "route_type" 700
"routes.txt" 24 "route_type" 700
"routes.txt" 25 "route_type" 700
"routes.txt" 26 "route_type" 700
"routes.txt" 27 "route_type" 700
"routes.txt" 28 "route_type" 700
"routes.txt" 29 "route_type" 700
"routes.txt" 30 "route_type" 700
"routes.txt" 31 "route_type" 700
"routes.txt" 32 "route_type" 700
"routes.txt" 33 "route_type" 700
"routes.txt" 34 "route_type" 700
"routes.txt" 35 "route_type" 700
"routes.txt" 36 "route_type" 700
"routes.txt" 37 "route_type" 700
"routes.txt" 38 "route_type" 700
"routes.txt" 39 "route_type" 700
"routes.txt" 40 "route_type" 700
"routes.txt" 41 "route_type" 700
"routes.txt" 42 "route_type" 700
"routes.txt" 43 "route_type" 700
"routes.txt" 44 "route_type" 700
"routes.txt" 47 "route_type" 700
"routes.txt" 48 "route_type" 700
unknown_column INFO 3

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"routes.txt" "direction0_name" 10
"routes.txt" "direction1_name" 11
"calendar.txt" "service_name" 11