GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T22:19:19Z,
for the dataset file:///shared/takashimacity-takasimasicommunitybus.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:
2025-04-01
Feed End Date:
2026-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. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 18
  • Shapes: 63
  • Stops: 306
  • Trips: 189

Specification Compliance report

4258 notices reported (0 errors, 4258 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.
7 "105265-夏季平日(畑線)"
missing_recommended_field WARNING 2

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"
"fare_attributes.txt" 3 "agency_id"
mixed_case_recommended_field WARNING 5

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" "武曽・横山線" 16
"stops.txt" "stop_name" "今市・辻沢" 162
"stops.txt" "stop_name" "今市・辻沢" 163
"stops.txt" "stop_name" "北浜（平和堂前）" 289
"stops.txt" "stop_name" "北浜（平和堂前）" 290
non_ascii_or_non_printable_char WARNING 4243

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 4243 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" "105265-冬季(マキノ北西部線)"
"calendar.txt" 3 "service_id" "105265-冬季(畑線)"
"calendar.txt" 4 "service_id" "105265-土休日(マキノ・今津)"
"calendar.txt" 5 "service_id" "105265-夏季(マキノ北西部線)"
"calendar.txt" 6 "service_id" "105265-夏季土休日(畑線)"
"calendar.txt" 7 "service_id" "105265-夏季平日(畑線)"
"calendar.txt" 8 "service_id" "105265-平日(マキノ・今津)"
"calendar.txt" 9 "service_id" "105265-平日(新旭・安曇川・高島)"
"calendar.txt" 10 "service_id" "105265-毎日(マキノ・今津)"
"calendar.txt" 11 "service_id" "105265-毎日(朽木)"
"calendar_dates.txt" 2 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 3 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 4 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 5 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 6 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 7 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 8 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 9 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 10 "service_id" "105265-冬季(畑線)"
"calendar_dates.txt" 11 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 12 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 13 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 14 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 15 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 16 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 17 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 18 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 19 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 20 "service_id" "105265-土休日(マキノ・今津)"
"calendar_dates.txt" 21 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 22 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 23 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 24 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 25 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 26 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 27 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 28 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 29 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 30 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 31 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 32 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 33 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 34 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 35 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 36 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 37 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 38 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 39 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 40 "service_id" "105265-夏季(マキノ北西部線)"
"calendar_dates.txt" 41 "service_id" "105265-夏季(マキノ北西部線)"
stop_too_far_from_shape WARNING 6

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
109 "105265-32041" "105265-6毎日(朽木)_10時15分_系統32041" 2370 "105265-191_01" "能家口" [35.336119000000004,135.868056] 2746.105591761305
109 "105265-32041" "105265-6毎日(朽木)_10時15分_系統32041" 2371 "105265-192_01" "能家分校前" [35.336119000000004,135.868056] 2973.2016852473203
109 "105265-32041" "105265-6毎日(朽木)_10時15分_系統32041" 2372 "105265-190_01" "能家" [35.351039,135.87014] 3835.1233495213028
112 "105265-32042" "105265-6毎日(朽木)_10時59分_系統32042" 2404 "105265-190_01" "能家" [35.351039,135.87014] 3835.1233495213028
112 "105265-32042" "105265-6毎日(朽木)_10時59分_系統32042" 2405 "105265-192_01" "能家分校前" [35.335997,135.868008] 2974.3700837660667
112 "105265-32042" "105265-6毎日(朽木)_10時59分_系統32042" 2406 "105265-191_01" "能家口" [35.335997,135.868008] 2746.3971776831836
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.
116 "105265-33021" "105265-6毎日(朽木)_08時38分_系統33021" 2472 "105265-265_01" "横谷口" [35.379842819291966,135.88033338021717] 2471 "105265-264_01" "横谷" [35.381716000000004,135.880381]