GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T02:58:51Z,
for the dataset file:///shared/tosadentraffic-streetcar.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-08-18
Feed End Date:
2026-12-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. transfers.txt
  12. translations.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 2
  • Shapes: 48
  • Stops: 152
  • Trips: 1056

Specification Compliance report

32402 notices reported (0 errors, 32396 warnings, 6 infos)

Notice Code Severity Total
duplicate_route_name WARNING 1

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
2 "105729-東西線上り_A" 3 "105729-南北線下り_A" "とさでん路面電車" "" 0 "105729-9490001007796_1"
mixed_case_recommended_field WARNING 1053

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.

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

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "デンテツ・ターミナルビル前" 70
"stops.txt" "stop_name" "デンテツ・ターミナルビル前" 71
"trips.txt" "trip_headsign" "いの（朝倉 経由）" 2
"trips.txt" "trip_headsign" "知寄町（はりまや橋 経由）" 3
"trips.txt" "trip_headsign" "いの（はりまや橋・鏡川橋・朝倉 経由）" 4
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 5
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 6
"trips.txt" "trip_headsign" "ごめん（はりまや橋・文珠通・領石通 経由）" 7
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 8
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 9
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 10
"trips.txt" "trip_headsign" "領石通（はりまや橋・文珠通 経由）" 11
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 12
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 13
"trips.txt" "trip_headsign" "桟橋通五丁目（はりまや橋 経由）" 14
"trips.txt" "trip_headsign" "朝倉（はりまや橋・鏡川橋 経由）" 15
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 16
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 17
"trips.txt" "trip_headsign" "ごめん（はりまや橋・文珠通・領石通 経由）" 18
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 19
"trips.txt" "trip_headsign" "桟橋通五丁目（はりまや橋 経由）" 20
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 21
"trips.txt" "trip_headsign" "いの（はりまや橋・鏡川橋・朝倉 経由）" 22
"trips.txt" "trip_headsign" "領石通（はりまや橋・文珠通 経由）" 23
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 24
"trips.txt" "trip_headsign" "領石通（はりまや橋・文珠通 経由）" 25
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 26
"trips.txt" "trip_headsign" "ごめん（はりまや橋・文珠通・領石通 経由）" 27
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 28
"trips.txt" "trip_headsign" "桟橋通五丁目（はりまや橋 経由）" 29
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 30
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 31
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 32
"trips.txt" "trip_headsign" "朝倉（はりまや橋・鏡川橋 経由）" 33
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 34
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 35
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 36
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 37
"trips.txt" "trip_headsign" "朝倉（はりまや橋・鏡川橋 経由）" 38
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 39
"trips.txt" "trip_headsign" "ごめん（はりまや橋・文珠通・領石通 経由）" 40
"trips.txt" "trip_headsign" "桟橋通五丁目（はりまや橋 経由）" 41
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 42
"trips.txt" "trip_headsign" "鏡川橋（はりまや橋 経由）" 43
"trips.txt" "trip_headsign" "文珠通（はりまや橋 経由）" 44
"trips.txt" "trip_headsign" "ごめん（はりまや橋・文珠通・領石通 経由）" 45
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 46
"trips.txt" "trip_headsign" "朝倉（はりまや橋・鏡川橋 経由）" 47
"trips.txt" "trip_headsign" "桟橋通五丁目（はりまや橋 経由）" 48
"trips.txt" "trip_headsign" "高知駅（はりまや橋 経由）" 49
non_ascii_or_non_printable_char WARNING 31342

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 31342 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" "105729-土日祝"
"calendar.txt" 3 "service_id" "105729-平日"
"calendar_dates.txt" 2 "service_id" "105729-●"
"calendar_dates.txt" 3 "service_id" "105729-●"
"calendar_dates.txt" 4 "service_id" "105729-●"
"calendar_dates.txt" 5 "service_id" "105729-●"
"calendar_dates.txt" 6 "service_id" "105729-●"
"calendar_dates.txt" 7 "service_id" "105729-●"
"calendar_dates.txt" 8 "service_id" "105729-●"
"calendar_dates.txt" 9 "service_id" "105729-●"
"calendar_dates.txt" 10 "service_id" "105729-●"
"calendar_dates.txt" 11 "service_id" "105729-●"
"calendar_dates.txt" 12 "service_id" "105729-●"
"calendar_dates.txt" 13 "service_id" "105729-●"
"calendar_dates.txt" 14 "service_id" "105729-●"
"calendar_dates.txt" 15 "service_id" "105729-●"
"calendar_dates.txt" 16 "service_id" "105729-●"
"calendar_dates.txt" 17 "service_id" "105729-●"
"calendar_dates.txt" 18 "service_id" "105729-●"
"calendar_dates.txt" 19 "service_id" "105729-●"
"calendar_dates.txt" 20 "service_id" "105729-●"
"calendar_dates.txt" 21 "service_id" "105729-●"
"calendar_dates.txt" 22 "service_id" "105729-●"
"calendar_dates.txt" 23 "service_id" "105729-●"
"calendar_dates.txt" 24 "service_id" "105729-●"
"calendar_dates.txt" 25 "service_id" "105729-●"
"calendar_dates.txt" 26 "service_id" "105729-●"
"calendar_dates.txt" 27 "service_id" "105729-●"
"calendar_dates.txt" 28 "service_id" "105729-●"
"calendar_dates.txt" 29 "service_id" "105729-●"
"calendar_dates.txt" 30 "service_id" "105729-●"
"calendar_dates.txt" 31 "service_id" "105729-●"
"calendar_dates.txt" 32 "service_id" "105729-●"
"calendar_dates.txt" 33 "service_id" "105729-●"
"calendar_dates.txt" 34 "service_id" "105729-●"
"calendar_dates.txt" 35 "service_id" "105729-●"
"calendar_dates.txt" 36 "service_id" "105729-●"
"calendar_dates.txt" 37 "service_id" "105729-●"
"calendar_dates.txt" 38 "service_id" "105729-●"
"calendar_dates.txt" 39 "service_id" "105729-●"
"calendar_dates.txt" 40 "service_id" "105729-●"
"calendar_dates.txt" 41 "service_id" "105729-●"
"calendar_dates.txt" 42 "service_id" "105729-●"
"calendar_dates.txt" 43 "service_id" "105729-●"
"calendar_dates.txt" 44 "service_id" "105729-●"
"calendar_dates.txt" 45 "service_id" "105729-●"
"calendar_dates.txt" 46 "service_id" "105729-●"
"calendar_dates.txt" 47 "service_id" "105729-●"
"calendar_dates.txt" 48 "service_id" "105729-●"
"calendar_dates.txt" 49 "service_id" "105729-●"
platform_without_parent_station INFO 6

platform_without_parent_station

A platform has no parent_station field set.

This is different from location_without_parent_station since it is less severe.

You can see more about this notice here.

csvRowNumber (?) Row number of the faulty record. stopId (?) The id of the faulty record. stopName (?) The stop name of the faulty record.
68 "105729-1034_01" "はりまや橋"
69 "105729-1034_02" "はりまや橋"
70 "105729-1101_01" "デンテツ・ターミナルビル前"
71 "105729-1101_02" "デンテツ・ターミナルビル前"
139 "105729-1204_01" "はりまや橋"
140 "105729-1204_02" "はりまや橋"