GTFS Schedule Validation Report

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

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
French
Feed Start Date:
2024-06-15
Feed End Date:
2024-09-15

Files included

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

Counts

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

Specification Compliance report

14 notices reported (0 errors, 14 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 "102874-ETE-2024"
3 "102874-ETE-2024-L2"
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 "20250516" "20240915" "20250523"
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" "102874-LES-MÛRIERS"
"stop_times.txt" 25 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 37 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 49 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 61 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 78 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 90 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 102 "stop_id" "102874-LES-MÛRIERS"
"stop_times.txt" 114 "stop_id" "102874-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`.
"102874-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.
"20250516" "20240701" "20240831"