Call-prep brief · checked 2026-09-06
コミュニティバス「のるmycar」 (滑川市)
Grade F · 43.9 / 100
Down 0.4 points since 2026-09-05 (F to F).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
Top three things to fix
Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 24 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Effort: One export setting.
Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Add the required column named in the finding to the flagged file.
A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.
Effort: Often an export setting; ask your vendor if it recurs.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data runs out in 24 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Duplicate key (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- A file is missing a column that GTFS requires.
- Next action
- Add the required column named in the finding to the flagged file.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Ready to send to the agency
Hi コミュニティバス「のるmycar」 (滑川市) team, Service data runs out in 24 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/namerikawacity-norumycar/
Key facts
- Feed URL
- https://api.gtfs-data.jp/v2/organizations/namerikawacity/feeds/norumycar/files/feed.zip?rid=current
- Last checked
- 2026-09-06
- Service window
- 24 days of service data remain. Last service date 2026-09-30.
- Feed version
- 20251001_2025年10月01日（滑川市コミュニティバス のる my car） その筋屋 1.473
- Location
- Toyama, Japan
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.