Feed status · checked 2026-08-02
Whatcom Transportation Authority
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-08-01
Catalogued in Washington.
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 2 hours ago; last changed 42 days 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
Review the flagged fields and fill in the ones your riders would use.
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.
⏱ A field at a time; not urgent.worth about +4 points in its category
Add feed_contact_email or feed_contact_url to feed_info.txt.Likely your export tool
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.
⏱ One field, set once in export settings.worth about +4 points in its category
Add feed_contact_email to feed_info.txt.
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.
⏱ One field.worth about +8 points in its category
This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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
- Some files leave out fields that GTFS asks for but does not require.
- Next action
- Review the flagged fields and fill in the ones your riders would use.
- 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
- feed_info.txt lists no contact email and no contact URL.
- Next action
- Add feed_contact_email or feed_contact_url to feed_info.txt.
- 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
- feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
- Next action
- Add feed_contact_email to feed_info.txt.
- 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.
Review the flagged fields and fill in the ones your riders would use. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Add feed_contact_email or feed_contact_url to feed_info.txt. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Add feed_contact_email to feed_info.txt. · Read the fix guide
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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 48 days.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 100% 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
This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 2 kinds of issue across 3 instances (0 error, 3 warning, 0 informational).
Service data covers the next 48 days.
100% of stops state wheelchair accessibility (44% marked accessible, 56% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (44% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (14, 15, 190, 232, 27, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
837 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Bakerview Rd at Fred Meyer", "Cornwall Ave at E St", "Northwest Ave at Birchwood Center", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 880 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.
- 1 (white)
- 10 (yellow)
- 14 (teal)
- 15 (orange)
- 18 (gray)
- 190 (teal)
- 232 (gray)
- 24 (green)
- 26 (brown)
- 27 (gray)
- 29 (green)
- 3 (yellow)
- 331 (yellow)
- 45 (orange)
- 47 (white)
- 48 (orange)
- 49 (red)
- 5 (blue)
- 50 (yellow)
- 512 (pink)
- 525 (purple)
- 533 (white)
- 540 (purple)
- 6 (green)
- 7 (blue)
- 71X (brown)
- 72X (brown)
- 75 (pink)
- 80X (gray)
- 9 (pink)
| Route | Type | Line color |
|---|---|---|
| 1 Fairhaven&Downtown | Bus | white |
| 10 Eldridge&Downtown | Bus | yellow |
| 14 Fairhaven&Downtown | Bus | teal |
| 15 Cordata/WCC&Downtown | Bus | orange |
| 18 Hospital&Cordata/WCC | Bus | gray |
| 190 Lincoln St&Downtown | Bus | teal |
| 232 Cordata/WCC&Downtown | Bus | gray |
| 24 Cordata | Bus | green |
| 26 Lynden&Cordata/WCC | Bus | brown |
| 27 Ferndale&Cordata/WCC | Bus | gray |
| 29 Cordata/Kline | Bus | green |
| 3 Airport/Cordata&Airport/Downtown | Bus | yellow |
| 331 Cordata/WCC&Downtown | Bus | yellow |
| 45 KingMountain&Cordata/WCC | Bus | orange |
| 47 Harbor&Downtown | Bus | white |
| 48 Cordata/WCC&Bakerview Spur | Bus | orange |
| 49 Downtown&Bakerview Spur | Bus | red |
| 5 Samish/Fairhaven&Samish/Downtown | Bus | blue |
| 50 LummiNation&Cordata/WCC | Bus | yellow |
| 512 Sudden Valley&Downtown | Bus | pink |
| 525 Barkley&Downtown | Bus | purple |
| 533 Yew St | Bus | white |
| 540 Sunset&Downtown | Bus | purple |
| 6 Fraser&Downtown | Bus | green |
| 7 Samish/WWU&Samish/Downtown | Bus | blue |
| 71X Everson/Nooksack/Sumas&Cordata | Bus | brown |
| 72X Kendall&Bellingham | Bus | brown |
| 75 Blaine/Birch Bay&Bellingham | Bus | pink |
| 80X Mt. Vernon&Bellingham | Bus | gray |
| 9 Hospital&Downtown | Bus | pink |
List every stop
- Bellingham Station
- Northwest Ave at Birchwood Center
- Alabama St at James St
- Kendall Rd at Balfour Valley Dr
- Northwest Dr at 4700 Block
- Line Rd at Kamm Rd
- Peace Portal Dr at Hughes Ave
- 12th St at McKenzie Ave
- McLeod Rd at Sunset Dr
- Peace Portal Dr at Hughes Ave
- Meridian St at Birchwood Ave
- Kendall Rd at Mt Baker Hwy
- Fraser St at Haskell
- Fraser St at Haskell
- Cordata Pkwy at Stuart Rd
- Mt Baker Hwy at Mosquito Lake Rd
- State St at Cedar St
- Kellogg Rd at Village Dr
- June Rd at Fuchsia Dr
- June Rd at Aldrich Rd
- Aldrich Rd at Northwest Dr
- Aldrich Rd at Northwest Rd
- June Rd at Aldrich Rd
- June Rd at Fuchsia Dr
- Kellogg Rd at Village Dr
- Cordata Pkwy at Cordata Park
- Cordata Pkwy at Stuart Rd
- Lakeway Dr at Woburn St
- Commercial St at Central Ave
- Commercial St at Young St
- Commerical St at Central Ave
- Horton Rd at Cordata Pkwy
- Horton Rd at Aldrich Rd
- Kline Rd at Green Vista Way
- Kline Rd at Spring Vista Way
- Kline Rd at Springside St
- 4700 Block Northwest Dr
- Cable St at Geneva St
- Deming Rd at Macaulay Rd
- Birch Bay Village
- Birch Bay Dr at Birch Point Loop
- 2nd St at C St
- C St at 5th
- C St at 5th St
- 2nd St at C St
- Deming Rd at Macaulay Rd
- Lake Louise Rd at Gate 13
- Bay-Lyn Dr at Grocery Outlet
- Bakerview Rd at Deemer Rd
- Bakerview Rd at Deemer Rd
- Forest St at Holly St
- Roeder Ave at Bellwether Way
- Roeder Ave at F St
- Squalicum Harbor
- Laurel St at Cornwall Ave
- Lake Whatcom Blvd at Gate 1
- Granary Ave at Chestnut St
- Granary Ave at Chestnut St
- Laurel St at Cornwall Ave
- Cornwall Ave at Chestnut St
- Samish Way at Pasco St
- Samish Way at Consolidation Ave
- State St at Rose St
- Hughes Ave at Odell St
- Hughes Ave at Odell St
- James St at Creston Way
- Cable St at Austin St
- James St at Creston Way
- Cornwall Ave at Maple St
- Bell Rd at Peace Portal Dr
- Bell Rd at Peace Portal Dr
- James St at King Ave
- James St at Foothill Ct
- Creston Way at Kellogg Rd
- Kellogg Rd at Archer Dr
- Kellogg Rd at Tull Rd
- Kellogg Rd at Tull Rd
- Lakeway Dr at Undine St
- Kellogg Rd at Archer Dr
- Creston Way at Kellogg Rd
- James St at Foothills Ct
- James St at King Ave
- James St at Meador Ave
- James St at Meador Ave
- Lakeway Dr at Birch St
- Squalicum Pkwy at St. Joseph Hospital
- Performing Arts Center
- Donovan Ave at Happy Valley Park
- Donovan Ave at Happy Valley Park
- Holly St at J St
- Old Fairhaven Pkwy at 2700 Block
- Old Fairhaven Pkwy at 16th St
- Old Fairhaven Pkwy at 19th St
- Old Fairhaven Pkwy at 22nd St
- Old Fairhaven Pkwy at 24th St
- Old Fairhaven Pkwy at 30th St
- Austin St at Fir Tree Way
- Austin St at Fremont St
- Lake Louise Rd at Gate 9
- Electric Ave at Fraser St
- Electric Ave at Flynn St
- Electric Ave at Bloedel Donovan
- Britton Rd at Barkley Blvd
- Electric Ave at Bloedel Donovan
- Electric Ave at Flynn St
- James St at Alabama St
- Electric Ave at Fraser St
- Woburn St at Lakeway Dr
- Woburn St at Fraser St
- Woburn St at Kentucky St
- Woburn St at Kentucky St
- Woburn St at Fraser St
- Old Woburn St at Sweet Bay Dr
- Lakeway Dr at Birch St
- Bennett Dr at McAlpine Rd
- Donovan Ave at 31st St
- Britton Rd at Barkley Blvd
- Hwy 9 at Rutsatz Rd
- Woburn St at Old Woburn St
- Mt Baker Hwy at Smith Rd
- Lake Louise Rd at Stimpson Family Nature Reserve
- Mt Baker Hwy at Noon Rd
- Mt Baker Hwy at Nugents Corner
- Mt Baker Hwy at Nugents Corner
- Deming Rd at Mount Baker High School
- Deming Rd at Mount Baker High School
- Harris Ave at 21st St
- Deming Rd at Water St
- Kendall Rd at Kendall Elementary School
- Shamrock Rd at Azure Way
- Golden Valley Dr at Cimarron Way
- Chestnut Dr at Dolphin Way
- James St at Carolina St
- James St at Kentucky St
- State St at Kansas St
- James St at Kentucky St
- 12th St at McKenzie Ave
- James St at Texas St
- Sunset Dr at 2500 block
- Sunset Dr at Woburn St
- James St at Connecticut St
- Sunset Dr at Racine St
- Sunset Dr at Woburn St
- Noon Rd at Mt Baker Hwy
- Oregon Trail at Kendall Rd
- Peaceful Valley Dr at Clear Valley Dr
- Deep Valley Dr at Red Valley Ln
- 24th St at Donovan Ave
- King Valley Dr at Green Valley Ct
- Hwy 9 at Van Zandt Community Hall
- Chestnut Dr at Golden Valley Dr
- Kendall Rd at Mt Baker Hwy
- Kellogg Rd at Meridian St
- Champion St at Unity St
- Girard St at C St
- Girard St at G St
- Girard St at J St
- Haggard Hall
- Meridian St at Broadway
- Meridian St at North St
- Meridian St at Oregon St
- Meridian St at Victor St
- Meridian St at Orchard Dr
- Meridian St at McLeod Rd
- Meridian St at Victor St
- Meridian St at Oregon St
- Meridian St at North St
- Meridian St at Monroe St
- Meridian St at Illinois St
- Girard St at J St
- Girard St at H St
- Girard St at D St
- Nooksack Valley High School
- Nooksack Rd at Madison St
- Nooksack Rd at Columbia St
- Main St at Kirsch Rd
- Main St at Kirsch Dr
- Meridian St at Illinois St
- Everson Rd at Kale Rd
- Everson Rd at Kale Rd
- Everson Rd at Roeder St
- Everson Rd at Strandell St
- Mission Rd at Chestnut St
- Mission Rd at Chestnut St
- Mission Rd at Suchanon Dr
- Guide Meridian at Horton Rd
- Guide Meridian at Kline Rd
- Guide Meridian at Smith Rd
- Kellogg Rd at Meridian St
- Guide Meridian at Laurel Rd
- Everson-Goshen Rd at Pole Rd
- Pole Rd at Everson Goshen Rd
- Mission Rd at Silves Ct
- Mission Rd at Silves Ct
- Mission Rd at Suchanon Dr
- Guide Meridian at Ten Mile Rd
- Guide Meridian at Laurel Rd
- Guide Meridian at Axton Rd
- Guide Meridian at Smith Rd
- Meadowbrook Ct at Tremont Ave
- Guide Meridian at Kline Rd
- Guide Meridian at Horton Rd
- Champion St at Grand Ave
- Cordata Pkwy at Whatcom Community College
- Nooksack Rd at Columbia St
- Nooksack Rd at Madison St
- Nooksack Valley Middle School
- Nooksack Valley Middle School
- Horton Rd at Pacific Rim Way
- Meridian St at Baker St
- Kellogg Rd at Whatcom Community College
- Peace Portal Dr at 4th St
- Peace Portal Dr at 4th St
- Grandview Rd at Enterprise Rd
- Portal Way at 6300 Block
- Portal Way at 6000 Block
- Grandview Rd at Enterprise Rd
- Grover St at 4th St
- Enterprise Rd at Matz Rd
- Portal Way at 6300 Block
- Portal Way at 6200 Block
- Axton Rd at Barrett Rd
- Birch Bay Lynden Rd at Anchor Pkwy
- Harborview Rd at Drayton Harbor Rd
- Drayton Harbor Rd at Blaine Rd
- Peace Portal Dr at Bell Rd
- Peace Portal Dr at Mitchell Ave
- Peace Portal Dr at Clark St
- Lynden Station
- Peace Portal Dr at Clark St
- Peace Portal Dr at Garfield Ave
- Peace Portal Dr at Bell Rd
- Drayton Harbor Rd at Blaine Rd
- Drayton Harbor Rd at Harborview Rd
- Birch Bay Lynden Rd at Anchor Pkwy
- Cable St at Lake Whatcom Blvd
- Lakeway Dr at Oriental Ave
- Lakeway Dr at Lowell Ave
- Lakeway Dr at Euclid Ave
- Guide Meridian at Pole Rd
- Lake Louise Rd at Gate 5
- Lake Whatcom Blvd at Gate 2
- Lake Whatcom Blvd at S Lakewood
- Lake Whatcom Blvd at N Lakewood
- Lake Whatcom Blvd at Woodcliff Ln
- Lake Whatcom Blvd at 2600 Block
- Lake Whatcom Blvd at E Strawberry Pt
- Lake Whatcom Blvd at W Strawberry Pt
- Lake Whatcom Blvd at Eagle Point
- Lake Whatcom Blvd at Cherry Ln
- and 630 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-08-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 92.5 | first check |
| 2026-07-30 | 90.4 | down 2.1 |
| 2026-08-01 | 89.6 | down 0.8 |
| 2026-08-02 | 89.2 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-08-01.
Same feed file as 2026-08-01; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade A. On 2026-08-01 the grade moved from A to B. As of 2026-08-02 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-08-01 Grade went A to B, freshness fell 3 points.
Everything we checked
3 findings, ordered by severity.
Show every finding
- Warning2 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)
- 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)
- 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.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 48 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 2545 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 48 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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 48 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, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
A local transit-data support resource is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies. This resource supports agencies; it is not a scoring authority.
- Correctness 92 / 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. FTA NTD readiness also checks that the published feed is valid.
- Freshness 80 / 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. FTA NTD readiness also checks that the published feed is current.
- Rider experience 92 / 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/whatcom-transportation-authority/2026-08-02.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-08-02. 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.