Prep for a call: printable one-page brief · For your board packet: printable one-pager · Fix log: every issue this feed has cleared · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Light Rail
Based on the feed this agency publishes
down 4.2 since 2026-07-08
Ahead of 61% of all tracked agencies and 59% of mid-size agencies. Operates in Maryland.
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.1, validator 8.0.1.
Checked for changes 18 minutes ago; last changed 18 minutes 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
Add feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.worth about +15 points
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
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
67 of 161 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 +10 points
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +8 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Add feed_info.txt with feed_start_date and feed_end_date to your export. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. See this feed's dated fix log.
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 10 kinds of issue across 1034 instances (0 error, 1028 warning, 6 informational).
Service data covers the next 175 days.
58% of stops state wheelchair accessibility (58% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
58% of stops state accessibility (58% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (LIGHT RAILLINK).
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.
14 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Camden Station / Camden Yards (Northbound)", "Cultural Center / State Center (Northbound)", "Mt. Royal / MICA (Northbound)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
This agency publishes realtime, but the feed needs an access key we don't have 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- LIGHT RAILLINK (teal)
| Route | Type | Line color |
|---|---|---|
| LIGHT RAILLINK BWI Airport / Glen Burnie - Hunt Valley | Tram / light rail | teal |
This feed has 161 stops.
List every stop
- Glen Burnie (Cromwell) (Northbound)
- Ferndale (Northbound)
- BWI Airport (Northbound)
- BWI Business District (Northbound)
- Linthicum (Northbound)
- North Linthicum (Northbound)
- Nursery Road (Northbound)
- Baltimore Highlands (Northbound)
- Patapsco (Northbound)
- Cherry Hill (Northbound)
- Westport (Northbound)
- Hamburg Street (Northbound)
- Camden Station / Camden Yards (Northbound)
- Convention Center (Northbound)
- Baltimore Arena (University Center) (Northbound)
- Lexington Market (Northbound)
- Mt. Vernon (Centre Street) (Northbound)
- Cultural Center / State Center (Northbound)
- Mt. Royal / MICA (Northbound)
- Penn Station (Northbound)
- North Avenue (Northbound)
- MTA Light Rail Division
- Woodberry (Northbound)
- Cold Spring Lane (Northbound)
- Mt. Washington (Northbound)
- Falls Road (Northbound)
- Lutherville (Northbound)
- Timonium (Northbound)
- Fairgrounds (Northbound)
- Warren Road (Northbound)
- Gilroy Road (Northbound)
- McCormick Road (Northbound)
- Pepper Road (Northbound)
- Hunt Valley (Northbound)
- Hunt Valley (Southbound)
- Pepper Road (Southbound)
- McCormick Road (Southbound)
- Gilroy Road (Southbound)
- Warren Road (Southbound)
- Fairgrounds (Southbound)
- Timonium (Southbound)
- Lutherville (Southbound)
- Falls Road (Southbound)
- Mt. Washington (Southbound)
- Cold Spring Lane (Southbound)
- Woodberry (Southbound)
- North Avenue (Southbound)
- Penn Station (Southbound)
- Mt. Royal / MICA (Southbound)
- Cultural Center / State Center (Southbound)
- Mt. Vernon (Centre Street) (Southbound)
- Lexington Market (Southbound)
- Baltimore Arena (University Center) (Southbound)
- Convention Center (Southbound)
- Camden Station / Camden Yards (Southbound)
- Hamburg Street (Southbound)
- Westport (Southbound)
- Cherry Hill (Southbound)
- Patapsco (Southbound)
- Baltimore Highlands (Southbound)
- Nursery Road (Southbound)
- North Linthicum (Southbound)
- Linthicum (Southbound)
- BWI Business District (Southbound)
- BWI Airport (Southbound)
- Ferndale (Southbound)
- Glen Burnie (Cromwell) (Southbound)
- Glen Burnie - shuttle bus 1
- Ferndale SB - shuttle bus 1
- Ferndale NB - shuttle bus 2
- BWI Airport - shuttle bus 1
- BWI Business Park - shuttle bus 1
- Linthicum NB - shuttle bus 1
- Linthicum SB - shuttle bus 2
- North Linthicum - shuttle bus 1
- Nursery Road SB - shuttle bus 1
- Nursery Road NB - shuttle bus 2
- Baltimore Highlands SB - shuttle bus 1
- Baltimore Highlands NB - shuttle bus 2
- Patapsco - shuttle bus 1
- Cherry Hill NB - shuttle bus 1
- Cherry Hill SB - shuttle bus 2
- Westport NB - shuttle bus 1
- Westport SB - shuttle bus 2
- Hamburg NB - shuttle bus 1
- Hamburg SB - shuttle bus 2
- Camden SB - shuttle bus 1
- Camden NB - shuttle bus 2
- Convention Center SB - shuttle bus 1
- Convention Center NB - shuttle bus 2
- Arena NB - shuttle bus 1
- Arena SB - shuttle bus 2
- Lexington Market 1 NB - shuttle bus 1
- Lexington Market 1 SB - shuttle bus 2
- Lexington Market 2 NB - shuttle bus 3
- Lexington Market 2 SB - shuttle bus 4
- Centre St NB - shuttle bus 1
- Centre St SB - shuttle bus 2
- Cultural Center NB - shuttle bus 1
- Cultural Center SB - shuttle bus 2
- Mt Royal SB - shuttle bus 1
- Mt Royal NB - shuttle bus 2
- North Avenue - shuttle bus 1
- Woodberry NB - shuttle bus 1
- Woodberry SB - shuttle bus 2
- Shuttle Stop - shuttle bus 1
- Shuttle Stop - shuttle bus 2
- Coldspring NB - shuttle bus 3
- Coldspring SB - shuttle bus 4
- Mt. Washington NB - shuttle bus 1
- Mt. Washington SB - shuttle bus 2
- Falls Road - shuttle bus 1
- Lutherville - shuttle bus 1
- Timonium SB - shuttle bus 1
- Timonium NB - shuttle bus 2
- Fairgrounds - shuttle bus 1
- Warren Rd NB - shuttle bus 1
- Warren Rd SB - shuttle bus 2
- Gilroy Rd NB - shuttle bus 1
- Gilroy Rd SB - shuttle bus 2
- McCormick Road NB - shuttle bus 1
- McCormick Road SB - shuttle bus 2
- Pepper Road NB - shuttle bus 1
- Pepper Road SB - shuttle bus 2
- Hunt Valley - shuttle bus 1
- Courtesy Stop - shuttle bus 1
- Courtesy Stop - shuttle bus 2
- Glen Burnie (Cromwell)
- Ferndale
- BWI Airport
- BWI Business District
- Linthicum
- North Linthicum
- Nursery Road
- Baltimore Highlands
- Patapsco
- Cherry Hill
- Westport
- Hamburg Street
- Camden Station
- Convention Center
- Baltimore Arena (University Center)
- Lexington Market
- Mt. Vernon (Centre Street)
- Cultural Center / State Center
- Mt. Royal / MICA
- Penn Station
- North Avenue
- Woodberry
- Cold Spring Lane
- Mt. Washington
- Falls Road
- Lutherville
- Timonium
- Fairgrounds
- Warren Road
- Gilroy Road
- McCormick Road
- Pepper Road
- Hunt Valley
- Penn Station
Over time
Overall score across the last 20 checks — down 4.2 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 70.7 | first check |
| 2026-06-20 | 70.7 | no change |
| 2026-06-21 | 70.7 | no change |
| 2026-06-22 | 70.7 | no change |
| 2026-06-23 | 70.7 | no change |
| 2026-06-24 | 70.7 | no change |
| 2026-06-25 | 70.7 | no change |
| 2026-06-26 | 70.7 | no change |
| 2026-06-27 | 70.7 | no change |
| 2026-06-28 | 70.8 | up 0.1 |
| 2026-06-29 | 70.8 | no change |
| 2026-06-30 | 70.8 | no change |
| 2026-07-01 | 70.8 | no change |
| 2026-07-02 | 70.7 | down 0.1 |
| 2026-07-04 | 70.7 | no change |
| 2026-07-05 | 70.8 | up 0.1 |
| 2026-07-06 | 70.8 | no change |
| 2026-07-07 | 70.8 | no change |
| 2026-07-08 | 74.9 | up 4.1 |
| 2026-07-09 | 70.7 | down 4.2 |
What changed since your last check
- Correctness up 4.5
- Freshness down 15.0
- Rider experience down 7.5
What changed in this feed
Overall score fell 4.2 points since 2026-07-08.
The feed file was re-published since 2026-07-08 (+127 KB).
New since 2026-07-08 (3 findings)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Validator rule: scorecard_missing_feed_info_dates · 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).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Changed counts
- down Some rider-facing names are in ALL CAPS or all lowercase. (782 → 700) (mixed_case_recommended_field)
- down Stop too far from shape using user distance (flagged by the MobilityData validator). (240 → 165) (stop_too_far_from_shape_using_user_distance)
Resolved since 2026-07-08 (3 findings)
- Stops match shape out of order (flagged by the MobilityData validator). (stops_match_shape_out_of_order)
- Some service calendars have no days of the week switched on. (service_has_no_active_day_of_the_week)
- Feed valid beyond total service window (flagged by the MobilityData validator). (feed_valid_beyond_total_service_window)
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-06-19 this feed started at grade C. On 2026-07-08 it cleared missing_recommended_file, scorecard_missing_feed_info_dates, scorecard_no_feed_contact. On 2026-07-09 it cleared feed_valid_beyond_total_service_window, service_has_no_active_day_of_the_week, stops_match_shape_out_of_order. As of 2026-07-09 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-07-09 Score fell 4 points, freshness fell 15 points.
- 2026-07-08 Score rose 4 points, freshness rose 15 points.
Everything we checked
- Warning700 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)
- Warning165 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning100 instances
Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning67 instances
67 of 161 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)
- Warning60 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Agencies here usually clear this within about 1 week (based on 11 observed fixes).
Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Agencies here usually clear this within about 2 weeks (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: scorecard_missing_feed_info_dates · 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 connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info3 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)
- Info2 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Unused station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unused_station · 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 with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
The feed publishes fare products but no fare_media.txt declaring how riders can pay.
Consider: Add fare_media.txt listing your accepted payment methods, including contactless EMV if riders can tap to pay.
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 175 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 699 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 and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 Not yet
This feed is close to the conformance mark. States wheelchair access on 58% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 175 days.
- Accessible Not yet
- States wheelchair access on 58% of stops and 100% 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 60 of 127 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 175 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 54 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 85 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 82 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily 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/maryland-transit-administration-469/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, 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.