{"agency":{"id":"durango-transit","name":"Durango Transit","subdivision_code":"US-CO","subdivision_name":"Colorado"},"categories":{"completeness":{"details":{"accessibility":{"measures":"presence_not_usability","score":96.5,"stops_marked_accessible_pct":93.5,"stops_marked_not_accessible_pct":0.9,"stops_stated_pct":94.4,"trips_stated_pct":100.0},"accessibility_measures":"presence_not_usability","cemv":{"declared":false,"supported":false},"components":{"contact":7.5,"fares":15.0,"headsigns":15.0,"stop_names":15.0,"wheelchair_stops":23.6,"wheelchair_trips":15.0},"fare_free":false,"fares":{"applied":true,"has_leg_rules":true,"has_products":true,"has_transfer_rules":true,"model":"v2","product_count":2},"flex":{"booking_reachable":false,"booking_rule_count":0,"has_booking_rules":false,"has_flex":false},"has_fares":true,"headsign_applicable_trips":196,"headsign_loop_exempt_trips":0,"headsign_pct":100.0,"headsign_scored_pct":100.0,"headsign_stop_headsign_trips":0,"mixed_case_stop_name_pct":100.0,"pathways":{"has_entrances":false,"has_levels":false,"has_pathways":false,"has_stations":false,"has_step_free":false,"pathway_count":0},"stops":107,"translations":{"feed_lang":"EN","has_translations":false,"languages":[],"translated_tables":[],"translation_count":0},"trips":196,"unmeasured_components":[],"wheelchair_accessible_pct":100.0,"wheelchair_boarding_pct":94.4,"wheelchair_marked_accessible_pct":93.5,"wheelchair_marked_not_accessible_pct":0.9},"findings":[{"code":"scorecard_wheelchair_boarding_unknown","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_wheelchair_boarding_unknown","line":"Fixing this covers 6 of 107 stops, about 6% of them.","reach":{"affected":6,"basis":"stops","basis_label":"stops","reason":"","share":0.0561,"total":107,"total_source":"geo.stop_count"},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":6,"effort":"A column in stops.txt; your scheduling software likely has it.","fix":"Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.","owner":"Likely your team","points":1.4,"severity":"WARNING","what":"6 of 107 stops don't say whether a wheelchair user can board there.","why":"Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all."},{"code":"scorecard_no_feed_contact","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_no_feed_contact","line":"This one is about the feed as a whole, so there is no share of it to count.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"feed_level","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"One field.","fix":"Add feed_contact_email to feed_info.txt.","owner":"","points":7.5,"severity":"INFO","what":"feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).","why":"App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months."}],"name":"completeness","score":91.1,"status":"measured","summary":"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 published.","weight":0.25},"correctness":{"details":{"distinct_codes":7,"instances_by_severity":{"ERROR":0,"INFO":6,"WARNING":4},"validator_version":"8.0.1"},"findings":[{"code":"stops_match_shape_out_of_order","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"stops_match_shape_out_of_order","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":2,"effort":"A few minutes per flagged trip.","fix":"Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.","owner":"Likely your export tool","points":4.0,"severity":"WARNING","what":"On some trips the stops fall along the route line in a different order than the schedule lists.","why":"Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map."},{"code":"missing_feed_contact_email_and_url","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"missing_feed_contact_email_and_url","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"One field, set once in export settings.","fix":"Add feed_contact_email or feed_contact_url to feed_info.txt.","owner":"Likely your export tool","points":4.0,"severity":"WARNING","what":"feed_info.txt lists no contact email and no contact URL.","why":"Without a contact, apps like Google Maps can't reach you when they find a problem in the feed."},{"code":"mixed_case_recommended_field","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"mixed_case_recommended_field","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"Often a bulk fix in your scheduling software.","fix":"Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').","owner":"Likely your export tool","points":4.0,"severity":"WARNING","what":"Some rider-facing names are in ALL CAPS or all lowercase.","why":"ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers."},{"code":"service_extends_far_in_the_future","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"service_extends_far_in_the_future","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":2,"effort":"Varies.","fix":"Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.","owner":"","points":0.5,"severity":"INFO","what":"Service extends far in the future (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."},{"code":"service_window_outside_feed_period","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"service_window_outside_feed_period","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":2,"effort":"Two fields in feed_info.txt, or one export setting.","fix":"Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.","owner":"Likely your export tool","points":0.5,"severity":"INFO","what":"Some service dates fall outside the date window set in feed_info.txt.","why":"feed_info.txt should span every day your service runs, so apps know when the data applies."},{"code":"feed_valid_beyond_total_service_window","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"feed_valid_beyond_total_service_window","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"Varies.","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.","owner":"","points":0.5,"severity":"INFO","what":"Feed valid beyond total service window (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."},{"code":"unknown_column","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"unknown_column","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"A quick look at the flagged files.","fix":"Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.","owner":"","points":0.5,"severity":"INFO","what":"Some files contain columns that are not part of the GTFS spec.","why":"Harmless to riders, but apps ignore these columns and they can hide typos in real column names."}],"name":"correctness","score":86.0,"status":"measured","summary":"The MobilityData validator flagged 7 kinds of issue across 10 instances (0 error, 4 warning, 6 informational).","weight":0.35},"freshness":{"details":{"days_until_expiry":1136,"effective_expiry_date":"2029-12-31","expiry_limited_by":"service_calendar","feed_end_date":"2030-01-31","feed_start_date":"2022-03-03","feed_version":"2026.11 Trolley-Loop-Fix","has_feed_info":true,"last_service_date":"2029-12-31","seasonal_boundary":false,"service_horizon_review_years":10,"service_horizon_status":"within_review_threshold","service_type":"fixed"},"findings":[],"name":"freshness","score":100.0,"status":"measured","summary":"Service data covers the next 1136 days.","weight":0.2},"realtime":{"name":"realtime","status":"not_yet_measured","summary":"Not scored yet. Nothing here counts against the grade.","weight":0.2}},"confidence":{"feed_age_days":0,"fetch_source":"origin","level":"medium","measured_categories":3,"notes":["Realtime quality was not measured this run. It does not count against the grade.","The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified."],"rt_windows":0,"total_categories":4},"conformance":{"awarded":true,"criteria":[{"detail":"Passes validation with no errors.","key":"valid","met":true},{"detail":"Service data covers the next 1136 days.","key":"current","met":true},{"detail":"States wheelchair access on 94% of stops and 100% of trips.","key":"accessible","met":true}],"status":"awarded","summary":"This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.","version":2},"feed":{"license_note":"No stated data license in the Mobility Database; verify before publishing.","reachable":true,"sha256":"6e97adaef48e2a2c6ad9fd23df9def3655f8fb052a85969eba8a3c8554a60856","size_bytes":48776,"source_provenance":"unverified","static_url":"https://durangogov.org/DocumentCenter/View/17688/Durango-Transit-GTFS-Data"},"fetch":{"final_url":"https://www.durangoco.gov/DocumentCenter/View/17688/Durango-Transit-GTFS-Data","max_attempts":4,"reader_archive_profile":"raw-v1","source":"origin","user_agent":"gtfs-scorecard/1.5.1 (+https://gtfsscorecard.org/fetcher/)"},"generated_at":"2026-11-21T00:00:00+00:00","geo":{"bbox":[-107.91359,37.22303,-107.82029,37.3224],"lat":37.27974,"lon":-107.87005,"stop_count":107},"mode_profile":{"ferry_only":false,"graded":false,"has_ferry":false,"is_multimodal":false,"measured":true,"modes":[{"key":"bus","label":"Bus","route_count":6,"trip_count":196,"trip_share_pct":100.0}],"primary_mode":"bus","primary_mode_label":"Bus","route_count":6,"trip_count":196},"ntd_id_alignment":{"detail":"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.","feed_agency_ids":["DRT"],"status":"unknown"},"ntd_readiness":{"pillars":[{"detail":"Published at a public URL.","key":"published","status":"ready"},{"detail":"Passes validation with no errors.","key":"valid","status":"ready"},{"detail":"Service data covers the next 1136 days.","key":"current","status":"ready"},{"detail":"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.","key":"agency_id","status":"ready"}],"status":"ready","summary":"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."},"overall":{"grade":"A","margin_to_lower_band":1.1,"margin_to_next_band":null,"score":91.1},"recommendations":[{"category":"accessibility","code":"scorecard_stop_name_needs_tts","count":57,"effort":"A short text field per affected stop; start with the busiest.","fix":"Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.","owner":"","points":0.0,"severity":"INFO","what":"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).","why":"A screen reader speaks the raw name. 'Main St & 2nd Ave' can come out as 'Main saint', or lose the ampersand."}],"routability":{"boardable_stops":107,"findings":[],"orphan_stops":0,"single_stop_trips":0,"trips_total":196},"route_map":{"drawn_route_count":6,"has_shapes":true,"path":"data/artifacts/durango-transit/geometry.geojson","route_count":6,"routes":[{"color":"57E93A","color_name":"green","has_shape":true,"id":"107427","label":"Route 4","long":"Crestview - 160 W","short":"Route 4","text_color":"FFFFFF","type_label":"Bus"},{"color":"290CAD","color_name":"blue","has_shape":true,"id":"FTL","label":"Route 2","long":"Fort Lewis College","short":"Route 2","text_color":"FFFFFF","type_label":"Bus"},{"color":"290CAD","color_name":"blue","has_shape":true,"id":"FTLCS","label":"FLC XP","long":"Fort Lewis Express","short":"FLC XP","text_color":"FFFFFF","type_label":"Bus"},{"color":"0054A6","color_name":"teal","has_shape":true,"id":"MTS","label":"Route 5","long":"Mercy / Three Springs","short":"Route 5","text_color":"FFFFFF","type_label":"Bus"},{"color":"E91E15","color_name":"red","has_shape":true,"id":"TR","label":"Route 1","long":"Main Ave Trolley","short":"Route 1","text_color":"000000","type_label":"Bus"},{"color":"BF6113","color_name":"orange","has_shape":true,"id":"WM","label":"Route 3","long":"Walmart","short":"Route 3","text_color":"000000","type_label":"Bus"}],"stop_count":107,"stop_points_capped":false},"rubric_version":"1.5","schema_version":"1.20","scoring_profile":{"id":"gtfs-scorecard-1.5","provenance":"GTFS Scorecard's project-authored weights, deductions, thresholds, grade bands, and fix ranking, informed by the California Transit Data Guidelines and the MobilityData gtfs-validator. It is not a worldwide standard or a compliance determination.","rubric_version":"1.5"},"shapes_readiness":{"detail":"All 196 trips have a shape in shapes.txt.","status":"ready","total_trips":196,"trips_with_shape":196},"snapshot_date":"2026-11-21","top_fixes":[{"code":"stops_match_shape_out_of_order","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"stops_match_shape_out_of_order","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":2,"effort":"A few minutes per flagged trip.","fix":"Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.","owner":"Likely your export tool","points":4.0,"rank":1,"severity":"WARNING","what":"On some trips the stops fall along the route line in a different order than the schedule lists.","why":"Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map."},{"code":"missing_feed_contact_email_and_url","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"missing_feed_contact_email_and_url","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"One field, set once in export settings.","fix":"Add feed_contact_email or feed_contact_url to feed_info.txt.","owner":"Likely your export tool","points":4.0,"rank":2,"severity":"WARNING","what":"feed_info.txt lists no contact email and no contact URL.","why":"Without a contact, apps like Google Maps can't reach you when they find a problem in the feed."},{"code":"mixed_case_recommended_field","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"mixed_case_recommended_field","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"Often a bulk fix in your scheduling software.","fix":"Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').","owner":"Likely your export tool","points":4.0,"rank":3,"severity":"WARNING","what":"Some rider-facing names are in ALL CAPS or all lowercase.","why":"ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers."}],"validator_version":"8.0.1"}