Feed status · checked 2026-07-19
Ishikari City Itsumo AI On-Demand Transit (石狩市AIデマンド交通「いつモ」)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Hokkaido, Japan.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.
Checked for changes 5 hours ago; last changed 5 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +18 points in its category
Review the rule documentation for 'invalid_float' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid float (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
134 of 134 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Re-generate shape distances in your export; flag to your vendor if it persists.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Review the rule documentation for 'invalid_float' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 255 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v1.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 6 kinds of issue across 2019 instances (12 error, 2005 warning, 2 informational).
Service data covers the next 255 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 本町花川線 | Bus | green (no shape in feed) |
| 厚田花川線 | Bus | green (no shape in feed) |
This feed has 134 stops.
List every stop
- ３線（本町花川線）
- ３線（本町花川線）
- ４線（本町花川線）
- ４線（本町花川線）
- ５線（本町花川線）
- ５線（本町花川線）
- ６線（本町花川線）
- ６線（本町花川線）
- ７線（本町花川線）
- ７線（本町花川線）
- 石狩工業団地（本町花川線）
- 石狩工業団地（本町花川線）
- ９線（本町花川線）
- ９線（本町花川線）
- １０線（本町花川線）
- １０線（本町花川線）
- 花畔中央（本町花川線）
- 花畔中央（本町花川線）
- 石狩庁舎前（本町花川線）
- 石狩庁舎前（本町花川線）
- 石狩（本町花川線）
- 石狩（本町花川線）
- 花川北中学校前（本町花川線）
- 花川北中学校前（本町花川線）
- 石狩病院（本町花川線）
- 石狩病院（本町花川線）
- ラルズ花川南店（本町花川線）
- ラルズ花川南店（本町花川線）
- 道の駅石狩「あいろーど厚田」（厚田花川線）
- 道の駅石狩「あいろーど厚田」（厚田花川線）
- 厚田支所（厚田花川線）
- 厚田支所（厚田花川線）
- 別狩中央（厚田花川線）
- 別狩中央（厚田花川線）
- 別狩（厚田花川線）
- 別狩（厚田花川線）
- 青島（厚田花川線）
- 青島（厚田花川線）
- 小谷中央（厚田花川線）
- 小谷中央（厚田花川線）
- 押琴（厚田花川線）
- 押琴（厚田花川線）
- 石狩温泉前（本町花川線）
- 石狩温泉前（本町花川線）
- 古潭（厚田花川線）
- 古潭（厚田花川線）
- 嶺泊北（厚田花川線）
- 嶺泊北（厚田花川線）
- 嶺泊（厚田花川線）
- 嶺泊（厚田花川線）
- 望来大橋（厚田花川線）
- 望来大橋（厚田花川線）
- 戸田墓園入口（厚田花川線）
- 戸田墓園入口（厚田花川線）
- 本覚寺前（厚田花川線）
- 本覚寺前（厚田花川線）
- 望来１０５番地（厚田花川線）
- 望来１０５番地（厚田花川線）
- 望来（厚田花川線）
- 望来（厚田花川線）
- 望来坂下（厚田花川線）
- 望来坂下（厚田花川線）
- 望来郵便局（厚田花川線）
- 望来郵便局（厚田花川線）
- 親船町（本町花川線）
- 親船町（本町花川線）
- 望来坂上（厚田花川線）
- 望来坂上（厚田花川線）
- 聚富北部（厚田花川線）
- 聚富北部（厚田花川線）
- 聚富（厚田花川線）
- 聚富（厚田花川線）
- 聚富会館前（厚田花川線）
- 聚富会館前（厚田花川線）
- 石狩霊園前（厚田花川線）
- 石狩霊園前（厚田花川線）
- 聚富団体（厚田花川線）
- 聚富団体（厚田花川線）
- 聚富中央（厚田花川線）
- 聚富中央（厚田花川線）
- 新開地（厚田花川線）
- 新開地（厚田花川線）
- トーメン団地（厚田花川線）
- トーメン団地（厚田花川線）
- 緑ケ原１丁目（厚田花川線）
- 緑ケ原１丁目（厚田花川線）
- 治水事務所前（本町花川線）
- 治水事務所前（本町花川線）
- トーメン団地入口（厚田花川線）
- トーメン団地入口（厚田花川線）
- 石狩八幡町（厚田花川線）
- 石狩八幡町（厚田花川線）
- 八幡町入口（厚田花川線）
- 八幡町入口（厚田花川線）
- 矢臼場（厚田花川線）
- 矢臼場（厚田花川線）
- １線（厚田花川線）
- １線（厚田花川線）
- ２線（厚田花川線）
- ２線（厚田花川線）
- ３線（厚田花川線）
- ３線（厚田花川線）
- ４線（厚田花川線）
- ４線（厚田花川線）
- ５線（厚田花川線）
- ５線（厚田花川線）
- ６線（厚田花川線）
- ６線（厚田花川線）
- 市営住宅（本町花川線）
- 市営住宅（本町花川線）
- ７線（厚田花川線）
- ７線（厚田花川線）
- 石狩工業団地（厚田花川線）
- 石狩工業団地（厚田花川線）
- ９線（厚田花川線）
- ９線（厚田花川線）
- １０線（厚田花川線）
- １０線（厚田花川線）
- 花畔中央（厚田花川線）
- 花畔中央（厚田花川線）
- 石狩庁舎前（厚田花川線）
- 石狩庁舎前（厚田花川線）
- 花川北中学校前（厚田花川線）
- 花川北中学校前（厚田花川線）
- 石狩病院（厚田花川線）
- 石狩病院（厚田花川線）
- 親船東３条１丁目（本町花川線）
- 親船東３条１丁目（本町花川線）
- 中央バス札幌整備工場前（本町花川線）
- 中央バス札幌整備工場前（本町花川線）
- 親船東１条１丁目（本町花川線）
- 親船東１条１丁目（本町花川線）
- 石狩中学校（本町花川線）
- 石狩中学校（本町花川線）
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Error11 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Validator rule: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid float (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_float' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: invalid_float · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1815 instances
Some internal IDs use characters outside the basic text set.
These IDs are valid UTF-8 data. This warning is only about support in older apps. It does not mean that names in other languages are wrong.
Fix: Only change the flagged IDs if an app needs basic ASCII values. Update each place that uses the ID. Keep all names and headsigns in their original language. (A planned ID change, not a quick text cleanup.)
Validator rule: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning189 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning134 instances
134 of 134 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning54 instances
54 of 54 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some files contain columns that are not part of the GTFS spec.
Harmless to riders, but apps ignore these columns and they can hide typos in real column names.
Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)
Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
This feed is close to the conformance mark. 2 validator errors to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 2 validator errors to resolve.
- Current Met
- Service data covers the next 255 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Clears the Google and Apple Maps four-week coverage bar. This feed has 255 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 12 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance. Read the full standards crosswalk.
- Correctness 50 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners.
- Rider experience 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/ishikari-itsumo-demand/2026-07-19.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-19. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.