aguni-village — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T15:17:28Z,
for the dataset file:///shared/aguni-village_0800cd77.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
特定非営利活動法人OTTOP
Publisher URL:
https://ottop.org
Feed Email:
transit@ottop.org
Feed Language:
Japanese
Feed Start Date:
2026-01-30
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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 3
  • Shapes: 2
  • Stops: 19
  • Trips: 17

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 6

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 "泊発_通常運行_2021年5月~2022年3月"
5 "全日(バス用)"
7 "粟国発_特別運行日_2026年2月3月"
8 "粟国発_特別運航_2025年9月27日"
11 "粟国発_特別運行日_2025年1月30日"
12 "粟国発_特別運行日_2025年3月30日"
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 "20260323" "20260331" "20260422"
missing_bike_allowance WARNING 9

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 "347" "941f459146a2ad9c6966da563ec4059f"
3 "347" "e13e6d6b2a023ff564381a955b3fcf22"
4 "347" "f39ad2557061d79ed610933bb23a49e6"
5 "347" "7db5bfc2653f9276ef9d91c4b67b75a8"
6 "347" "608e966ae35d9150cd5eded7f9fd198f"
7 "348" "431b5abd3bcef51d7185c865a1b0b1cd"
8 "348" "aac47592ddf1d94f0649a2ddb9960307"
9 "348" "03dea811098fec226a5a5ba35e22972c"
10 "348" "3e4d08b986593d0378cdee08d54e33a7"
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.
"feed_info.txt" 2 "feed_version"
mixed_case_recommended_field WARNING 3

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_long_name" "泊発-粟国着" 3
"stops.txt" "stop_name" "泊港(フェリー粟国乗船所)" 3
non_ascii_or_non_printable_char WARNING 101

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 101 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_dates.txt" 2 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 3 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 4 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 5 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 6 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 7 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 8 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 9 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 10 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 11 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 12 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 13 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 14 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 15 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 16 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 17 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 18 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 19 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 20 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 21 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 22 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 23 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 24 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 25 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 26 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 27 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 28 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 29 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 30 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 31 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 32 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 33 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 34 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 35 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 36 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 37 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 38 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 39 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 40 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 41 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 42 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 43 "service_id" "泊発_通常運行_2021年5月~2022年3月"
"calendar_dates.txt" 44 "service_id" "粟国発_特別運行日_2025年1月30日"
"calendar_dates.txt" 45 "service_id" "粟国発_特別運行日_2025年3月30日"
"calendar_dates.txt" 46 "service_id" "粟国発_特別運航_2025年9月27日"
"calendar_dates.txt" 47 "service_id" "泊発_通常運行_2022年4月~"
"calendar_dates.txt" 48 "service_id" "泊発_通常運行_2022年4月~"
"calendar_dates.txt" 49 "service_id" "泊発_通常運行_2022年4月~"
"calendar_dates.txt" 50 "service_id" "泊発_通常運行_2022年4月~"
"calendar_dates.txt" 51 "service_id" "泊発_通常運行_2022年4月~"