GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.0.0 at 2025-05-16T13:54:55Z,
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:
Japanese
Feed Start Date:
2021-12-17
Feed End Date:
2022-12-16

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 1
  • Shapes: 1
  • Stops: 2
  • Trips: 6

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 1

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 "100081-全日"
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" "20221216" "20250523"
missing_bike_allowance WARNING 6

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
2 "100081-10" "100081-1全日_07時40分_系統101001"
3 "100081-10" "100081-1全日_13時10分_系統101001"
4 "100081-10" "100081-1全日_16時00分_系統101001"
5 "100081-10" "100081-1全日_09時50分_系統102001"
6 "100081-10" "100081-1全日_14時30分_系統102001"
7 "100081-10" "100081-1全日_17時00分_系統102001"
missing_recommended_field WARNING 1

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"fare_attributes.txt" 2 "agency_id"
mixed_case_recommended_field WARNING 1

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.
"routes.txt" "route_short_name" "松島～呼子航路" 2
non_ascii_or_non_printable_char WARNING 25

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.
"calendar.txt" 2 "service_id" "100081-全日"
"stop_times.txt" 2 "trip_id" "100081-1全日_07時40分_系統101001"
"stop_times.txt" 3 "trip_id" "100081-1全日_07時40分_系統101001"
"stop_times.txt" 4 "trip_id" "100081-1全日_13時10分_系統101001"
"stop_times.txt" 5 "trip_id" "100081-1全日_13時10分_系統101001"
"stop_times.txt" 6 "trip_id" "100081-1全日_16時00分_系統101001"
"stop_times.txt" 7 "trip_id" "100081-1全日_16時00分_系統101001"
"stop_times.txt" 8 "trip_id" "100081-1全日_09時50分_系統102001"
"stop_times.txt" 9 "trip_id" "100081-1全日_09時50分_系統102001"
"stop_times.txt" 10 "trip_id" "100081-1全日_14時30分_系統102001"
"stop_times.txt" 11 "trip_id" "100081-1全日_14時30分_系統102001"
"stop_times.txt" 12 "trip_id" "100081-1全日_17時00分_系統102001"
"stop_times.txt" 13 "trip_id" "100081-1全日_17時00分_系統102001"
"trips.txt" 2 "trip_id" "100081-1全日_07時40分_系統101001"
"trips.txt" 2 "service_id" "100081-全日"
"trips.txt" 3 "trip_id" "100081-1全日_13時10分_系統101001"
"trips.txt" 3 "service_id" "100081-全日"
"trips.txt" 4 "trip_id" "100081-1全日_16時00分_系統101001"
"trips.txt" 4 "service_id" "100081-全日"
"trips.txt" 5 "trip_id" "100081-1全日_09時50分_系統102001"
"trips.txt" 5 "service_id" "100081-全日"
"trips.txt" 6 "trip_id" "100081-1全日_14時30分_系統102001"
"trips.txt" 6 "service_id" "100081-全日"
"trips.txt" 7 "trip_id" "100081-1全日_17時00分_系統102001"
"trips.txt" 7 "service_id" "100081-全日"
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
5 "100081-1" "100081-1全日_09時50分_系統102001" 9 "100081-1_01" "松島定期船乗り場" [33.58521,129.84022] 8 "100081-2_01" "松島行定期船乗り場" [33.53975,129.89472]
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" "20211217" "20221216"