GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T21:05:06Z,
for the dataset file:///shared/fxc.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:
2025-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. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 8
  • Shapes: 11
  • Stops: 217
  • Trips: 1016

Specification Compliance report

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

Notice Code Severity Total
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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" "20251231" "20260104"
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 11

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.
"agency.txt" "agency_name" "株式会社フジエクスプレス ちぃばす" 2
"stops.txt" "stop_name" "麻布十番駅前(一の橋)" 18
"stops.txt" "stop_name" "麻布十番駅前(一の橋)" 19
"stops.txt" "stop_name" "東麻布二丁目(田町ルート)" 34
"stops.txt" "stop_name" "東麻布二丁目( 麻布東ルート)" 103
"stops.txt" "stop_name" "東麻布一丁目(東京タワー下)" 125
"stops.txt" "stop_name" "東麻布一丁目(東京タワー下)" 126
"trips.txt" "trip_headsign" "麻布十番駅前(一の橋)行" 516
"trips.txt" "trip_headsign" "麻布十番駅前(一の橋)行" 529
"trips.txt" "trip_headsign" "麻布十番駅前(一の橋)行" 839
"trips.txt" "trip_headsign" "麻布十番駅前(一の橋)行" 852