Feed status · checked 2026-09-05
Hirosaki City Shared Taxi (弘前市乗合タクシー・北星交通)
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Aomori, 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.3, validator 8.0.1.
Checked for changes 1 hours ago; last changed 1 hours ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
564 of 564 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
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
82 of 82 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
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.
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.
⏱ A planned ID change, not a quick text cleanup.worth about +8 points in its category
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
- 564 of 564 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 82 of 82 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Some internal IDs use characters outside the basic text set.
- Next action
- 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.
- 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
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.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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.
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.
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 207 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 9 kinds of issue across 3109 instances (0 error, 3103 warning, 6 informational).
Service data covers the next 207 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.
1 accessibility depth signal
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, 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.
This feed has 564 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 石川地区線（石川方面） | Bus | white (no shape in feed) |
| 小友地区線（農村環境改善センター行き） | Bus | white (no shape in feed) |
| 福村新里地区線A（JR弘前駅行き） | Bus | white (no shape in feed) |
| 福村新里地区線a（JR弘前駅行き） | Bus | white (no shape in feed) |
| 船沢地区線（マックスバリュー弘前城北店前行き） | Bus | white (no shape in feed) |
| 船沢地区線（船沢地区行き） | Bus | white (no shape in feed) |
| 三ツ森地区線（マックスバリュー弘前城北店前行き） | Bus | white (no shape in feed) |
| 三ツ森地区線（三ツ森地区行き） | Bus | white (no shape in feed) |
| 弥生葛原地区線（市街地方面行き） | Bus | white (no shape in feed) |
| 弥生葛原地区線（弥生葛原方面行き） | Bus | white (no shape in feed) |
| 石川地区線（市街地・大鰐方面） | Bus | white (no shape in feed) |
| 堀越地区線（市街地方面） | Bus | white (no shape in feed) |
| 堀越地区線（堀越方面） | Bus | white (no shape in feed) |
| 鳥井野地区線（城西四丁目行き） | Bus | white (no shape in feed) |
| 鳥井野地区線（岩木庁舎前行き） | Bus | white (no shape in feed) |
| 笹館地区線（市街地方面行き） | Bus | white (no shape in feed) |
| 笹館地区線（笹館地区行き） | Bus | white (no shape in feed) |
| 小友地区線（板柳行き） | Bus | white (no shape in feed) |
List every stop
- JR石川駅
- 弘南鉄道新里駅
- 小島入口
- 小島入口
- 小島
- 小島
- 富栄
- 富栄
- 折笠
- 折笠
- 宮舘
- 宮舘
- 中別所
- 中別所
- 向野
- 向野
- ① 杉山町会 弥生北口停留所（旧 弥生北口バス停）
- ① 杉山町会 弥生北口停留所（旧 弥生北口バス停）
- ② 杉山町会 ごみ集積所A
- ② 杉山町会 ごみ集積所A
- ③ 杉山町会 ごみ集積所B（旧 弥生平バス停付近）
- ③ 杉山町会 ごみ集積所B（旧 弥生平バス停付近）
- 弘南鉄道新里駅
- 川合
- ④ 弥生町会 弥生南口停留所（旧 弥生南口バス停）
- ④ 弥生町会 弥生南口停留所（旧 弥生南口バス停）
- ⑤ 弥生町会 ごみ集積所A
- ⑤ 弥生町会 ごみ集積所A
- ⑥ 弥生町会 ごみ集積所B（弥生会館付近）
- ⑥ 弥生町会 ごみ集積所B（弥生会館付近）
- ⑦ 弥生町会 ごみ集積所C（旧 弥生バス停付近）
- ⑦ 弥生町会 ごみ集積所C（旧 弥生バス停付近）
- ⑧ 上弥生町会 スクールバス停留所
- ⑧ 上弥生町会 スクールバス停留所
- ⑨ 弥生町会 外ヶ沢入口停留所（旧 外ヶ沢入口バス停）
- ⑨ 弥生町会 外ヶ沢入口停留所（旧 外ヶ沢入口バス停）
- ⑪ 折笠町会 ごみ集積所A
- ⑪ 折笠町会 ごみ集積所A
- ⑫ 折笠町会 ごみ集積所B（折笠町民会館付近）
- ⑫ 折笠町会 ごみ集積所B（折笠町民会館付近）
- ⑬ 折笠町会 折笠停留所（乗合タクシー船沢線 折笠停留所と兼用）
- ⑬ 折笠町会 折笠停留所（乗合タクシー船沢線 折笠停留所と兼用）
- ⑭ 折笠町会 富栄停留所（乗合タクシー船沢線 富栄停留所と兼用）
- ⑭ 折笠町会 富栄停留所（乗合タクシー船沢線 富栄停留所と兼用）
- 川合
- 元門外
- ⑮ 折笠町会 ごみ集積所C（船沢こども園の裏）
- ⑮ 折笠町会 ごみ集積所C（船沢こども園の裏）
- ⑯ 鼻和町会 ごみ集積所A
- ⑯ 鼻和町会 ごみ集積所A
- ⑰ 鼻和町会 ごみ集積所B（旧 鼻和バス停付近）
- ⑰ 鼻和町会 ごみ集積所B（旧 鼻和バス停付近）
- ⑱ 鼻和町会 鼻和南口停留所（旧 鼻和南口バス停）
- ⑱ 鼻和町会 鼻和南口停留所（旧 鼻和南口バス停）
- ⑲ 細越町会 ごみ集積所A（細越町民会館付近）
- ⑲ 細越町会 ごみ集積所A（細越町民会館付近）
- ⑳ 細越町会 ごみ集積所B
- ⑳ 細越町会 ごみ集積所B
- ㉑ 愛宕町会 ごみ集積所A
- ㉑ 愛宕町会 ごみ集積所A
- ㉒ 愛宕町会 ごみ集積所B
- ㉒ 愛宕町会 ごみ集積所B
- ㉓ 葛原町会 ごみ集積所A（葛原健康増進センター付近）
- ㉓ 葛原町会 ごみ集積所A（葛原健康増進センター付近）
- ㉔ 葛原町会 四ツ谷停留所（旧 四ツ谷バス停）
- ㉔ 葛原町会 四ツ谷停留所（旧 四ツ谷バス停）
- 元門外
- 門外
- ㉕ 新岡町会 新岡温泉前停留所（旧 新岡温泉前バス停）
- ㉕ 新岡町会 新岡温泉前停留所（旧 新岡温泉前バス停）
- ㉖ 新岡町会 ごみ集積所A
- ㉖ 新岡町会 ごみ集積所A
- ㉗ 新岡町会 ごみ集積所B（新岡公民館付近）
- ㉗ 新岡町会 ごみ集積所B（新岡公民館付近）
- ㉘ 愛宕町会 ごみ集積所C
- ㉘ 愛宕町会 ごみ集積所C
- ㉙ 愛宕町会 ごみ集積所D（愛宕多目的集会所付近）
- ㉙ 愛宕町会 ごみ集積所D（愛宕多目的集会所付近）
- ㉚ 愛宕町会 ごみ集積所E（旧 愛宕東口バス停付近）
- ㉚ 愛宕町会 ごみ集積所E（旧 愛宕東口バス停付近）
- ㉛ 八幡町会 ごみ集積所A
- ㉛ 八幡町会 ごみ集積所A
- ㉜ 八幡町会 ごみ集積所B（旧 八幡バス停付近）
- ㉜ 八幡町会 ごみ集積所B（旧 八幡バス停付近）
- ㉝ 八幡町会 ごみ集積所C（消防屯所付近）
- ㉝ 八幡町会 ごみ集積所C（消防屯所付近）
- ㉞ 八幡町会 ごみ集積所D（幸仙橋付近）
- ㉞ 八幡町会 ごみ集積所D（幸仙橋付近）
- 門外
- 小笠原ｸﾘﾆｯｸ前
- 岩木庁舎前
- 岩木庁舎前
- JR石川駅
- JR石川駅
- 石川西口
- 石川西口
- 弘南鉄道石川駅
- 弘南鉄道石川駅
- 工藤医院前
- 工藤医院前
- 石川学校前
- 石川学校前
- 乳井神社前
- 乳井神社前
- 乳井入口
- 乳井入口
- 薬師堂
- 薬師堂
- 薬師堂北口
- 薬師堂北口
- 小笠原ｸﾘﾆｯｸ前
- 堀越小学校前
- 弘南鉄道新里駅
- 弘南鉄道新里駅
- 川合
- 川合
- 元門外
- 元門外
- 門外
- 門外
- 小笠原ｸﾘﾆｯｸ前
- 小笠原ｸﾘﾆｯｸ前
- 堀越小学校前
- 堀越小学校前
- 健生病院前
- 健生病院前
- いとくｱﾙｶﾃﾞｨｱ店
- いとくｱﾙｶﾃﾞｨｱ店
- 佐藤長前
- 佐藤長前
- JR弘前駅城東口
- JR弘前駅城東口
- 堀越小学校前
- 健生病院前
- JR弘前駅城東口
- JR弘前駅城東口
- カブセンター前
- カブセンター前
- 東部児童センター
- 東部児童センター
- 田園5丁目
- 田園5丁目
- 福田
- 福田
- 福村小学校前
- 福村小学校前
- 福村
- 福村
- 保育所前
- 保育所前
- ESTクリニック前
- ESTクリニック前
- 城東タウンプラザ
- 城東タウンプラザ
- 健生病院前
- いとくｱﾙｶﾃﾞｨｱ店
- 二ツ屋
- 二ツ屋
- 新里
- 新里
- 福田子入口
- 福田子入口
- 高田
- 高田
- JR弘前駅城東口
- JR弘前駅城東口
- 岩木庁舎前
- 岩木庁舎前
- 津軽中学校通り
- 津軽中学校通り
- 岩木郵便局前
- 岩木郵便局前
- 岩木小学校前
- 岩木小学校前
- 二本木十文字
- 二本木十文字
- いとくｱﾙｶﾃﾞｨｱ店
- 佐藤長前
- 一町田南口
- 一町田南口
- 海洋センター前
- 海洋センター前
- 兼平
- 兼平
- 兼平集会所前
- 兼平集会所前
- 派立北口
- 派立北口
- 中央派立
- 中央派立
- 派立南口
- 派立南口
- 鳥井野
- 鳥井野
- 鳥井野北口
- 鳥井野北口
- 竜ノ口南口
- 竜ノ口南口
- 佐藤長前
- JR弘前駅城東口
- 竜ノ口北口
- 竜ノ口北口
- 真土
- 真土
- 大川
- 大川
- 駒越平田
- 駒越平田
- 近名
- 近名
- 樋の口イオンタウン
- 樋の口イオンタウン
- 城西4丁目
- 城西4丁目
- 板柳案内所
- 板柳案内所
- 栄町
- 栄町
- 板柳駅通り
- 板柳駅通り
- JR弘前駅城東口
- JR石川駅
- 石川西口
- JR弘前駅城東口
- 板柳十文字
- 板柳十文字
- 下青女子
- 下青女子
- 新和小学校前
- 新和小学校前
- 新和支所前
- 新和支所前
- 種市十文字
- 種市十文字
- 桂橋前
- 桂橋前
- 桂
- 桂
- 上中畑
- 上中畑
- 川合
- 川合
- 三和小学校前
- 三和小学校前
- JR弘前駅城東口
- カブセンター前
- 川村
- 川村
- 川村西口
- 川村西口
- and 314 more (see the full list on the map or in the GeoJSON)
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
14 findings, ordered by severity.
Show every finding
- Warning1522 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.)
Finding code: non_ascii_or_non_printable_char · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1319 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning564 instances
564 of 564 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning240 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning82 instances
82 of 82 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.)
Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning15 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some values have extra spaces at the start or end.
A stray space can break a match, so a stop or route may fail to link across files.
Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)
Finding code: leading_or_trailing_whitespaces · See MobilityData GTFS Validator rules (opens the validator rules 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.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info116 instances
About 116 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info5 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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · 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).
App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 207 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 207 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 57 / 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 49 / 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/hirosaki-hokusei-shared-taxi/2026-09-05.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-09-05. 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.