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
Durango Transit
Based on the feed this agency publishes
up 1.7 since 2026-07-08 · B → B
Ahead of 95% of all tracked agencies and 96% of mid-size agencies. Operates in Colorado.
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 15 minutes ago; last changed 15 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 fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points
Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stops match shape out of order (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +4 points
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing feed contact email and url (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +4 points
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
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 fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · 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.
Review the rule documentation for 'stops_match_shape_out_of_order' 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.
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.
Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · 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 6 kinds of issue across 8 instances (0 error, 4 warning, 4 informational).
Service data covers the next 540 days.
94% of stops state wheelchair accessibility (93% marked accessible, 1% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
94% of stops state accessibility (94% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
57 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Main Ave. & 9th St.", "Main Ave. & 19th St.", "Main Ave. & Earl St.", 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- Route 4 (green)
- Route 2 (blue)
- FLC XP (blue)
- Route 5 (teal)
- Route 1 (red)
- Route 3 (orange)
| Route | Type | Line color |
|---|---|---|
| Route 4 Crestview - 160 W | Bus | green |
| Route 2 Fort Lewis College | Bus | blue |
| FLC XP Fort Lewis Express | Bus | blue |
| Route 5 Mercy / Three Springs | Bus | teal |
| Route 1 Main Ave Trolley | Bus | red |
| Route 3 Walmart | Bus | orange |
This feed has 107 stops.
List every stop
- Transit Center
- Main Ave. & 9th St.
- Buckley Park
- Auto Zone
- Main Ave. & 19th St.
- Adobe Inn
- Durango High School
- Rec Center
- Travellodge
- North City Market
- Main Ave. & Earl St.
- Main Ave. & Animas View Dr.
- North Animas View Dr.
- United Campground
- Redwood Lodge
- Recodo Del Rio
- Animas Trailer Park
- Hampton Inn
- Main Ave. & Durango Joe's
- Spanish Trails
- Main Ave. & 29th St.
- Main Ave. & 27th St.
- Brookside Park
- Main Ave. & 21st ST
- Valero Fuel Station
- Main Ave. & 14th St.
- Main Ave. & 11th St.
- Main Ave. & 9th St.
- Main Ave. & 7th St.
- College Dr. & Main Ave.
- College Dr. & 4th Ave.
- College Dr. & 8th Ave
- Valle De Merced Apartments
- Ferringway Apartments
- Fort Lewis College
- Hillcrest Apartments.
- Hillcrest Dr.
- Rim Dr.
- N College Dr. & Willow Pl. NB
- N College Dr. & Florida Rd.
- Ptarmigan Center
- 32nd & Holly
- Florida & Oak
- Florida & Aspen
- Florida & Colorado
- Florida & Folsom
- Island Cove
- Tamarin Square Apt.
- Rocket Point South
- Rocket Point North
- Wilson Gulch
- CR 233
- Mercy Hospital
- Confluence Ave & Heritage Ln
- Mercado & Confluence
- Forest Ave & Avenida Del Sol
- Avenida Del Sol & Falcon Way
- Manna
- Roosa Ave & 9th Street
- Tech Center
- Westwood
- Four Winds
- Speedway
- Lightner Creek Village
- Marathon
- Residences at Durango
- Westside Mobile Park
- 5th Ave. & 5th St.
- 5th Ave. & 3rd St.
- 2nd St. & 6th Ave.
- 2nd St. & 8th Ave.
- Centennial Center
- Bodo Dr.
- Bodo Dr. & Turner Dr.
- Turner Dr. & Sawyer Dr.
- Turner Dr. & Sheppard Dr.
- Walmart
- Trans Lux Dr.
- Serious Texas BBQ
- Big 5 Sporting Goods
- Nature's Oasis
- 22nd St. & 2nd Ave.
- Arroyo Dr. & Delwood Ave.
- Delwood Ave. & Crestview Dr.
- Forest Ave. & Crestview Dr.
- Forest Ave. & Kearney St.
- Mercury Village Dr
- Sunnyside
- Home Depot
- Pinion Terrace
- Subaru
- Miremonte
- East Animas
- E. 3rd Ave. & 31st.
- Memorial Park
- Riverview Dr. & Mesa Ave.
- Riverview Dr. & N Animas Pl.
- Riverview Dr. & S Animas Pl.
- Florida Rd. & Chapman Hill
- Florida Rd. & Colorado Ave.
- Florida Rd. & Aspen Dr.
- Florida Rd. & Oak Dr.
- Florida Rd. & N College Dr.
- N College Dr. & Willow Pl. SB
- Rim Drive
- Goeglein & Linda Court
- Goeglein & Fort Lewis Dr.
Over time
Overall score across the last 20 checks — up 1.7 since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 84.9 | first check |
| 2026-06-20 | 84.9 | no change |
| 2026-06-21 | 84.9 | no change |
| 2026-06-22 | 84.9 | no change |
| 2026-06-23 | 84.9 | no change |
| 2026-06-24 | 84.9 | no change |
| 2026-06-25 | 84.9 | no change |
| 2026-06-26 | 84.9 | no change |
| 2026-06-27 | 84.9 | no change |
| 2026-06-28 | 84.9 | no change |
| 2026-06-29 | 84.9 | no change |
| 2026-06-30 | 84.9 | no change |
| 2026-07-01 | 84.9 | no change |
| 2026-07-02 | 84.9 | no change |
| 2026-07-04 | 84.9 | no change |
| 2026-07-05 | 84.9 | no change |
| 2026-07-06 | 84.9 | no change |
| 2026-07-07 | 84.9 | no change |
| 2026-07-08 | 84.9 | no change |
| 2026-07-09 | 86.6 | up 1.7 |
What changed since your last check
- Correctness up 4.0
- Freshness no change
- Rider experience no change
What changed in this feed
Overall score rose 1.7 points since 2026-07-08.
The feed file was re-published since 2026-07-08 (+4 KB).
Resolved since 2026-07-08 (1 finding)
- Some files are missing recommended (not required) fields. (missing_recommended_field)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning6 instances
6 of 107 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)
- Warning2 instances
Stops match shape out of order (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stops_match_shape_out_of_order' 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: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' 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: 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
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)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info2 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' 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 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Feed valid beyond total service window (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' 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 5 observed fixes).
Validator rule: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
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).
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)
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 540 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 196 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 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 540 days.
- Accessible Met
- States wheelchair access on 94% 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 540 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.
Your state runs a transit-data program that can help: CDOT Digital Transit Mobility. Colorado's program coordinating GTFS data across transit providers. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 86 / 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 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 76 / 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/durango-transit/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.