Feed status · checked 2026-08-01
Atomic City Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in New Mexico.
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 days ago; last changed 38 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
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
215 of 216 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
1898 of 2428 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 +12 points in its category
Re-generate shape_dist_traveled on export so stop and shape distances use the same units.Likely your export tool
On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.
⏱ Usually an export-tool fix, not hand editing.worth about +8 points in its category
This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
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
- 215 of 216 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
- 1898 of 2428 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
- On some trips the stop distances run a little past the end of the route line.
- Next action
- Re-generate shape_dist_traveled on export so stop and shape distances use the same units.
- 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. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
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. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
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.
Re-generate shape_dist_traveled on export so stop and shape distances use the same units. · Read the fix guide
Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.
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 152 days.
- Published accessibility data
- Accessibility information is stated for 0.5% of stops and 21.8% 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 exported from Remix. If your planners work in Remix, the change happens in your own workspace; otherwise forward this to whoever maintains your Remix data. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 4 kinds of issue across 2578 instances (0 error, 148 warning, 2430 informational).
Service data covers the next 152 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.
2 accessibility depth signals
3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (12, 8, 2T).
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.
210 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Grand Canyon & Meadow", "Grand Canyon & Balboa", "Diamond Dr & Golf Course Outbound", 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 216 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 (red)
- 10 (teal)
- 11 (green)
- 12 (orange)
- 2C (green)
- 2T (gray)
- 4 (yellow)
- 5 (teal)
- 6 (pink)
- 7 (purple)
- 8 (orange)
- 9 (brown)
| Route | Type | Line color |
|---|---|---|
| 1 Downtown Circulator | Bus | red |
| 10 Barranca Mesa Express | Bus | teal |
| 11 White Rock Express | Bus | green |
| 12 Bandelier | Bus | orange |
| 2C White Rock Concert Svc | Bus | green |
| 2T White Rock Truck Route | Bus | gray |
| 4 North Community | Bus | yellow |
| 5 Barranca Mesa | Bus | teal |
| 6 North Mesa | Bus | pink |
| 7 North Mesa Express | Bus | purple |
| 8 North Community Express | Bus | orange |
| 9 Aspen Area Express | Bus | brown |
List every stop
- Transit Center
- 35th St & Diamond Dr AM
- 2502 35th St AM
- 2522 35th St AM
- North Rd & Mountain School Inbound
- North Rd & Urban St Inbound
- Brisa Del Bosque & Quemazon
- Quemazon & Esperanza
- Diamond & Sandia
- Diamond Dr & Sullivan Field Inbound
- North Rd & 42nd Outbound
- North Rd & Urban St Outbound
- North Rd & Mountain School Outbound
- North Road & Yucca
- 45th St & Alabama St Outbound
- Arizona Ave & 45th St Outbound
- 4117 Arizona Ave Outbound
- Arizona Ave & 36th St Outbound
- Arizona & 35th
- 2529 35th St Inbound
- 2511 35th St Inbound
- 35th St & Diamond Dr Inbound
- Diamond Dr & Arkansas Ave Inbound
- Diamond Dr & Sycamore St Inbound
- Trinity Dr & Diamond Dr Outbound
- Trinity Dr & 41st St Outbound
- Trinity Dr & 43rd St Outbound
- Trinity Dr & 46th St Outbound
- 48th St & 47th St Outbound
- Sandia Dr & 45th St Outbound
- Sandia & 42nd
- Sandia Dr & 40th St Outbound
- Diamond Dr & Golf Course Outbound
- San Ildefonso & Chamisa St Outbound
- Barranca & San Ildefonso
- Barranca Rd & El Rayo St Outbound
- Barranca Rd & Venado St Outbound
- Barranca Rd & El Conejo St Outbound
- Barranca Rd & Dos Brazos St Outbound
- Barranca Rd & Camino Encantado Outbound
- Barranca Rd & Loma Del Escolar St Out
- Barranca Rd & Cascabel St Outbound
- Barranca Rd & La Cueva St Outbound
- Barranca Rd & Navajo Rd Outbound
- Navajo Rd & Osito St Outbound
- Navajo Rd & Coyote St Outbound
- Navajo Rd & San Juan St Outbound
- Navajo Rd & El Nido St Outbound
- Navajo Rd & Totavi St Outbound
- Navajo Rd & Los Pueblos St Outbound
- Los Pueblos & Navajo
- Los Pueblos St & San Juan St Inbound
- Los Pueblos St & Zuni St Inbound
- Barranca Rd & La Cueva St Inbound
- Barranca Rd & Cascabel St Inbound
- Barranca Rd & Loma Del Escolar St In
- Barranca Rd & Camino Encantado Inbound
- Barranca Rd & Dos Brazos St Inbound
- Barranca Rd & El Conejo St Inbound
- Barranca Rd & Venado St Inbound
- Barranca Rd & El Rayo St Inbound
- Barranca & San Ildefonso
- San Ildefonso Rd & Chamisa St Inbound
- Diamond Dr & Club Rd Inbound
- Diamond Dr & 35th St Inbound
- Sandia Dr & 40th St Inbound
- Sandia & 42nd
- Sandia Dr & 45th St Inbound
- Sandia Dr & 48th St Inbound
- 48th St & Trinity Dr Inbound
- Trinity Dr & 46th St Inbound
- Trinity Dr & 43rd St Inbound
- Trinity Dr & 41st St Inbound
- Trinity Dr & Diamond Dr Inbound
- Villa St & 37th St Outbound
- 2248 35th St Outbound
- 35th St & Diamond Dr Outbound
- San Ildefonso Rd (S of Roundabout) Out
- San Ildefonso Rd & Camino Redondo Out
- San Ildefonso & Hawk Dr
- San Ildefonso Rd & Camino Uva Outbound
- San Ildefonso Rd & Mountain Vista Out
- San Ildefonso Rd & Broadview Dr Outbound
- San Ildefonso Rd & La Mesa Cir Outbound
- San Ildefonso Rd & Alamo Rd Outbound
- 1299 San Ildefonso Rd Outbound
- Stoneview & Big Rock
- 1230 Big Rock Loop Inbound
- Big Rock Loop & San Ildefonso Rd Inbound
- San Ildefonso Rd & Alamo Rd Inbound
- San Ildefonso Rd & La Mesa Cir Inbound
- San Ildefonso Rd & Broadview Dr Inbound
- San Ildefonso Rd & Mountain Vista In
- San Ildefonso Rd & Baseball Field In
- San Ildefonso Rd & Camino Uva Inbound
- San Ildefonso & Hawk Dr
- San Ildefonso Rd & Camino Redondo In
- San Ildefonso Rd (S of Roundabout) In
- 35th St & Diamond Dr Inbound
- 2253 35th St Inbound
- Villa St & 37th St Inbound
- 38th St & Diamond Dr Inbound
- East Rd (NM502) & East Park Pool
- State Road 4 & Rover Blvd
- SR 4 & Sherwood
- White Rock Library
- Meadow Lane & Chiquita Dr
- Meadow Ln & Isleta Dr (Cmsa Elem Schl)
- Meadow Ln & Mimbres Dr
- Meadow Ln & Overlook Rd
- Meadow & Overlook
- Grand Canyon & Meadow
- Grand Canyon Dr & Ridgecrest Ave
- Grand Canyon Dr & Paige Lp W
- Grand Canyon Dr & Aragon Ave
- Aragon Ave & Canyon Vista Pool
- Aragon Ave & Rover Pk Path (332 Aragon)
- Aragon Ave & Rover Blvd
- Rover Blvd & Azure Dr
- Rover Blvd & Aragon Ave
- Grand Canyon Dr & Beryl Ave
- Grand Canyon & Sherwood
- Grand Canyon Dr & Canada Way
- Grand Canyon Dr & Monte Vista St
- Grand Canyon Dr & Mesa Verde St
- Grand Canyon Dr & La Paloma Dr
- State Rd 4 & Rover Blvd Inbound
- East Dr & Airport Rd
- East Dr & Tewa Lp Inbound
- East Rd (NM502) & Canyon Rd Inbound
- E Jemez Rd & Royal Crest
- North Rd & Mountain Elem
- Loma del Escolar & Barranca Elem
- Frey Trail
- Bandelier Visitor Center Dropoff
- Grand Canyon Dr & Beryl Ave
- Rover & SR 4
- Sandia Dr & 46th St Outbound
- Bandelier Visitor Center Pickup
- Quemazon & Tranquilo
- Brisa Del Bosque & Sinuoso
- Corona & Quemazon
- Quemazon & Sinuoso
- Iroquois & Seminole St
- Arkansas Ave & 41st St
- North Road & Yucca
- Villa & 33rd
- Villa St & 35th St N
- Villa St & 34th St S
- Central Ave & Oppenheimer Dr Inbound
- Arizona & 35th
- Arizona Ave & Woodland Rd S
- Arizona Ave & Woodland Rd N
- Arizona & 35th
- Arizona Ave & Country Ln N
- Arizona Ave & Country Ln S
- Club Rd & Woodland Rd W
- Club Rd & Woodland Rd E
- Entrada Dr & Camino Entrada
- Entrada & Camino Entrada
- Rover & SR 4
- Meadow Ln & Delicado Dr N
- Meadow Ln & Isleta Dr (Cmsa Elem Schl) N
- Meadow Ln & Joya Loop E
- Meadow Ln & Overlook Rd E
- Meadow & Overlook
- Grand Canyon & Meadow
- Grand Canyon & Ridgecrest S
- Grand Canyon & Layton S
- Grand Canyon & Aragon S
- Aragon Ave & Canyon Vista Pool E
- Aragon Ave & Rover Pk Path S
- Aragon & Rover
- Rover Blvd & Azure Dr W
- Grand Canyon & Sherwood
- Brisa Del Bosque & Sereno
- North Road & Urban Park
- 1157 San Ildefonso Rd Outbound
- Central Ave & 20th St
- Rover Blvd & 222 Rover
- Sherwood & SR 4
- Aztec & Sherwood
- Aztec & Rover Blvd
- Grand Canyon & SR 4
- Grand Canyon Dr & Mesa Verde
- Grand Canyon & Monte Vista
- Grand Canyon & Canada
- Grand Canyon & Balboa
- SR 4 & Community Garden
- Trinity & 20th (Temp. Concert)
- Trinity & Diamond
- 3773 Trinity Dr
- Trinity Dr & 35th St
- Trinity Dr & Timber Ridge Rd
- Trinity & Oppenheimer
- Trinity Dr & Ashley Pond (Gas Station)
- Trinity Dr & 20th St
- Trinity Dr & 15th St
- Trinity Dr & Knecht St
- Trinity & DP Rd
- Central & 6th
- Central Ave & 9th St Inbound
- Central & Municipal
- Central Ave & 20th St
- Central & Mesa Library
- Canyon Rd & Aquatic Center Inbound
- Canyon Rd & Canyon Village Apts Inbound
- Canyon Rd & Catholic Church Inbound
- Canyon & Diamond
- Diamond Dr & Lemon Lot
- Diamond Dr & West Rd
- Central & Municipal
- Diamond Dr & High School Gym Outbound
- Diamond & Orange
- Diamond Dr & Pueblo Complex Outbound
- Diamond Dr & 38th St Outbound
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 82.7 | first check |
| 2026-07-30 | 82.7 | no change |
| 2026-07-31 | 82.7 | no change |
| 2026-08-01 | 82.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
6 findings, ordered by severity.
Show every finding
- Warning1898 instances
1898 of 2428 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)
- Warning215 instances
215 of 216 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)
- Warning143 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2428 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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)
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 152 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 2428 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 Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 22% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 152 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 22% 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 151 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.
- Correctness 86 / 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 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. FTA NTD readiness also checks that the published feed is current.
- Rider experience 63 / 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/atomic-city-transit/2026-08-01.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-01. 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.