Feed status · checked 2026-11-21
Cecil Transit
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-11-20
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://www.cecilcountymd.gov/DocumentCenter/View/5246/Cecil-County-MD---GTFS
Watch this feed for free: we email you before it expires or when its grade drops.
Top things to fix
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.
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.
⏱ Varies.worth about +12 points in its category
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
109 of 109 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.
Fixing this covers all 109 stops in the feed.
⏱ 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
266 of 266 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 266 trips in the feed.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- No need reading for this feed was on hand when this was built, so transit need is not known.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. See this feed's finding-clearance log.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown
Make the change. This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.
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. See this feed's finding-clearance log.
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 405 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- 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 Passio a fix request
This feed is generated by your Passio system. Copy this and send it to your Passio contact; the fixes apply to the route and stop data behind your AVL setup. Each fix names the validator notice and a guide link.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
Cecil Transit’s published feed lists 3 bus routes, 266 scheduled trips and 109 stops. Its service dates run from 2026-11-17 through 2027-12-31. The published file last changed on 2026-11-19.
Score by category
The MobilityData validator flagged 4 kinds of issue across 29 instances (1 error, 28 warning, 0 informational).
Service data covers the next 405 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (GC).
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.
41 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("200 Chesapeake Blvd", "4th St and Ave D", "Abbey Manor/Elkton Rehabilitation", 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.
This feed has 109 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.
- XC (blue)
- GC (red)
- New (purple)
| Route | Type | Line color |
|---|---|---|
| XC Cross-County Connection | Bus | blue |
| GC Glasgow Connection | Bus | red |
| New Newark | Bus | purple |
List every stop
- 150 East Main Street
- 200 Chesapeake Blvd
- 214 North Street
- 4th St and Ave D
- Abbey Manor/Elkton Rehabilitation
- Acme - Big Elk Mall
- Rt 40 - Hertrich Ford
- Activity Center EB
- CubeSmart
- Rt 40 - Barrington Woods
- Blue Ball Rd & Elkton Blvd
- Bridge Street Plaza (Flag)
- Broad St Across from Boxcar Ave
- Cecil College - Main Campus
- Cecil College - Elkton Station
- Chesapeake Blvd (MVA)
- Chesapeake Blvd (Shelter)
- NE - Crouch Ln & Mauldin Ave
- Concord Apartments
- Cottages at Chesapeake
- Davita Dialysis (Call in)
- Rt 40 - Dominos Pizza
- Elkton Library
- Elkton Senior Apartments
- Elkton Walmart
- Fairgreen Apartments
- Rt 40 - Food Lion
- Rt 40 - PVL Food Lion
- Gardens at Chesapeake
- Golden Kay Apts Eastbound
- Golden Kay Apts Westbound
- Green Turtle - Rt 279
- Rt 40 - Lone Star Traders
- Rt 40 - Apple Auto
- Rt 40 - Walgreens
- High & South Sts
- Hollingsworth Manor & Landing Ln
- NE - Howards Market
- Industrial Park - DE
- Interchange Business Park
- Rt 40 - John Deere
- Judy Center
- Ollie's - Big Elk Mall
- Rt 40 - Kohl's
- Landing Ln & Rt 40
- Lindy's Market - Aiken Ave
- Newark Main St
- Rt 40 - Maloney Rd
- NE - Mauldin Ave and Jethro St
- Rt 40 - Ocean State Job Lot
- Rt 40 - After Montgomery Drive
- Rt 40 - New Eastern Motel
- Newark Park & Ride
- Newark Rail Station
- Newark Transit Hub
- NE - Main St 5 & 10
- NE - Walmart
- NE - Walgreens/Food Lion
- Old Elk Neck Rd & Route 40
- Peoples Plaza - DART Stop
- Perry Point Building 361
- Perryville Library
- Perryville MARC Station
- Perryville Post Office
- Principio Health Center WB
- Principio Parkway @ Amazon
- Redner's (Call in)
- Rt 40 - Taco Bell
- Rt 213 - Royal Farms
- Rt 272 - Lums Rd Northbound
- Rt 272 - Lums Rd Southbound
- Rt 279 - Belle Hill Rd
- Rt 279 - Amstel Ave
- Rt 279 - Fletchwood Rd (Wawa)
- Rt 40 - Chili's
- Rt 40 - La Grange
- Rt 40 - Across from Stony Run
- Rt 40 - Chesapeake Landing Dr
- Rt 40 - After Coudon Blvd
- Rt 40 - After Mill Creek Rd
- Rt 40 - APGFCU
- Rt 40 - Cedar Corner Rd
- Rt 40 - Charlestown Crossing
- Rt 40 - Jackson Station Rd (EB)
- Rt 40 - Jackson Station Rd (WB)
- Rt 40 - North Bay Medical Center
- Rt 40 - Pats Pizza
- Rt 40 - Restoration Hardware
- Rt 40 - Ritchie Brothers
- Rt 40 - Serenity Health
- Rt 40 - Normira Ave
- Rt 40 - Belvidere Rd EB
- Rt 40 - Belvidere Rd WB
- Rt 40 - Nottingham Rd
- Safeway
- Shop Rite
- Skipjack Ct
- Springford Gardens
- Rt 40 - Stony Run Apts (Bus Shelter)
- Suburban Plaza
- Rt 40 - The Woodlands
- Union Hospital
- United Methodist Church (Bus Shelter)
- W Main St and Maffitt St
- Walmart @ Bakers Ln
- Razor Strap Rd @ Walmart
- Rt 40 - Weavers Liquors
- Ikea
- Rt 40 - Flea Market
Over time
Overall score across the last 13 checks — unchanged since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 68.5 | first check |
| 2026-11-10 | 68.1 | down 0.4 |
| 2026-11-11 | 67.6 | down 0.5 |
| 2026-11-12 | 67.2 | down 0.4 |
| 2026-11-13 | 66.8 | down 0.4 |
| 2026-11-14 | 66.4 | down 0.4 |
| 2026-11-15 | 66.0 | down 0.4 |
| 2026-11-16 | 65.6 | down 0.4 |
| 2026-11-17 | 65.1 | down 0.5 |
| 2026-11-18 | 64.7 | down 0.4 |
| 2026-11-19 | 67.0 | up 2.3 |
| 2026-11-20 | 67.0 | no change |
| 2026-11-21 | 67.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-19 to 2026-11-21 (3 checks) | e1acc00d21ae | 2027-12-31 | Current rubric: see the trend above |
| 2026-11-09 to 2026-11-18 (10 checks) | a3264bf705fb | 2026-12-31 | Current rubric: see the trend above |
| 2026-10-28 to 2026-11-06 (10 checks) | a3264bf705fb | 2026-12-31 | D, 69.7 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-02 to 2026-10-27 (26 checks) | 40b0565160a0 | 2025-12-18 | F, 40 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | 40b0565160a0 | 2025-12-18 | F, 40 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-14 to 2026-07-24 (9 checks) | 40b0565160a0 | 2025-12-18 | F, 40 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-13 (25 checks) | 40b0565160a0 | 2025-12-18 | F, 40 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
8 findings, ordered by severity.
Show every finding
- Error1 instance
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning266 instances
266 of 266 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning254 instances
254 of 266 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning109 instances
109 of 109 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning22 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning5 instances
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.)
Finding code: stop_too_far_from_shape · Read the fix guide for stop_too_far_from_shape · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · 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.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
How we measured this
Checked for changes 18 hours ago; last changed 2 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
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.5, validator 8.0.1.
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Ready
- Service data covers the next 405 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 266 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
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 405 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% 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 404 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.
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 74 / 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 31 / 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.
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/cecil-transit-3178/2026-11-21.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-11-21. 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.