GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T21:09:13Z,
for the dataset file:///shared/minokamo.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:
2024-04-01
Feed End Date:
2025-03-31

Files included


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

Counts


  • Agencies: 1
  • Blocks: 6
  • Routes: 9
  • Shapes: 0
  • Stops: 244
  • Trips: 127

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 7

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 "101471-まちぐる西回り(岐阜健康管理センターあり)"
3 "101471-まちぐる西回り(岐阜健康管理センターなし)"
4 "101471-休園日(健康の森)"
5 "101471-全日"
6 "101471-平日(福祉会館)"
7 "101471-日祝(福祉会館)"
8 "101471-開園日(健康の森)"
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 "20251205" "20250331" "20251212"
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 22

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_long_name" "あい愛バス まちなかぐるっと線" 2
"routes.txt" "route_short_name" "あい愛バス3公園連絡線" 3
"routes.txt" "route_long_name" "あい愛バスあまちの森・しょうよう線" 4
"routes.txt" "route_long_name" "あい愛バスむくの木・そうきち線" 5
"routes.txt" "route_long_name" "あい愛バス古井駅-可児川駅線" 10
"stops.txt" "stop_name" "かも~る(文化会館)" 13
"stops.txt" "stop_name" "島町2丁目" 14
"stops.txt" "stop_name" "島町2丁目" 15
"stops.txt" "stop_name" "本郷町6丁目" 23
"stops.txt" "stop_name" "本郷町6丁目" 24
"stops.txt" "stop_name" "食品スーパー アルビス" 34
"stops.txt" "stop_name" "太田本町4丁目" 38
"stops.txt" "stop_name" "前平町1丁目" 141
"stops.txt" "stop_name" "前平町1丁目" 142
"stops.txt" "stop_name" "前平町3丁目" 143
"stops.txt" "stop_name" "中部台5丁目" 197
"stops.txt" "stop_name" "中部台5丁目" 198
"stops.txt" "stop_name" "田島町1丁目" 216
"stops.txt" "stop_name" "田島町1丁目" 217
"stops.txt" "stop_name" "田島町3丁目" 218
"stops.txt" "stop_name" "田島町3丁目" 219
"stops.txt" "stop_name" "本郷町7丁目" 225
non_ascii_or_non_printable_char WARNING 3566

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.

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

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" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar.txt" 3 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar.txt" 4 "service_id" "101471-休園日(健康の森)"
"calendar.txt" 5 "service_id" "101471-全日"
"calendar.txt" 6 "service_id" "101471-平日(福祉会館)"
"calendar.txt" 7 "service_id" "101471-日祝(福祉会館)"
"calendar.txt" 8 "service_id" "101471-開園日(健康の森)"
"calendar_dates.txt" 2 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 3 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 4 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 5 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 6 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 7 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 8 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 9 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 10 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 11 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 12 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 13 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 14 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 15 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 16 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 17 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 18 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 19 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 20 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 21 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 22 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 23 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 24 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 25 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 26 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 27 "service_id" "101471-まちぐる西回り(岐阜健康管理センターあり)"
"calendar_dates.txt" 28 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 29 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 30 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 31 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 32 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 33 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 34 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 35 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 36 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 37 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 38 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 39 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 40 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 41 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 42 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 43 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
"calendar_dates.txt" 44 "service_id" "101471-まちぐる西回り(岐阜健康管理センターなし)"
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.
"20251205" "20240401" "20250331"