Feed status · checked 2026-10-07
Delmarva Community Transit
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-10-06
Cataloged 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.4, validator 8.0.1.
Checked for changes 39 minutes ago; last changed 104 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.
About this feed
Delmarva Community Transit’s published feed lists 20 bus routes, 180 scheduled trips and 212 stops. Its service dates run from 2018-12-20 through 2022-02-26. The published file has not changed since our first check on 2026-06-19.
Top things to fix
Correct feed_end_date in feed_info.txt. Set it to 2022-02-28, the last day in your calendar, or to the last day your schedule is reliable.Likely your export tool
feed_info.txt says this feed ends on 2022-02-26. Your service calendar runs to 2022-02-28. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.
This one is about the feed as a whole, so there is no share of it to count.
⏱ One field in feed_info.txt, often an export setting.worth about +100 points in its category
Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop time timepoint without times (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 +24 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
212 of 212 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 212 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 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.
- Maryland as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.
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 published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Fix 01 · Read the fix guide for scorecard_feed_end_date_before_calendar
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_boarding_unknown
Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.
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 was 1684 days ago.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0.6% 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 your vendor a fix request
This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 9 kinds of issue across 1529 instances (1474 error, 50 warning, 5 informational).
Your feed_info end date, 2022-02-26, is earlier than your service calendar, which runs to 2022-02-28. The feed is read as ending on that earlier date, 1684 day(s) ago.
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 (7).
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.
84 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Goldsborough & Calvert", "High & Choptank", "612/Greyhound", 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 212 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.
- 4 (red)
- 10 (white)
- 11 (blue)
- 12 (pink)
- St. Michaels Shuttle (black)
- Denton - Easton AM Shuttle (orange)
- Saturday Denton - Easton Shuttle (orange)
- C (orange)
- D (orange)
- Cambridge Central (green)
- Kent County Community Center Shuttle (green)
- Cambridge South (green)
- 5 (orange)
- 6 (yellow)
- 7 (purple)
- 8A (yellow)
- 8 (yellow)
- 9 (green)
- 9A (green)
| Route | Type | Line color |
|---|---|---|
| 4 Route 4 - Rock Hall - Chestertown - Centreville - Easton | Bus | red |
| 10 Route 10 - Cambridge - Vienna - Mardela Springs - Salisbury | Bus | white |
| 11 Route 11 - Cambridge - Secretary - East New Market - Hurlock - Preston - Easton | Bus | blue |
| 12 Route 12 - Chesapeake College Shuttle | Bus | pink |
| St. Michaels Shuttle | Bus | black |
| Denton - Easton AM Shuttle | Bus | orange |
| Saturday Denton - Easton Shuttle | Bus | orange |
| C Route C Easton | Bus | orange |
| D Route D Easton | Bus | orange |
| Cambridge North | Bus | green (no shape in feed) |
| Cambridge Central | Bus | green |
| Kent County Community Center Shuttle | Bus | green |
| Cambridge South | Bus | green |
| 5 Route 5 - Denton - Easton | Bus | orange |
| 6 Route 6 - Denton - Federalsburg - Preston - Easton | Bus | yellow |
| 7 Route 7 - Greensboro - Denton - Easton | Bus | purple |
| 8A Route 8A - 5:00 AM Cambridge Route | Bus | yellow |
| 8 Route 8 - Cambridge - Hurlock - Secretary - East New Market - Federalsburg | Bus | yellow |
| 9 Route 9 - Cambridge - Trappe - Easton | Bus | green |
| 9A Route 9A - Cambridge - Trappe - Easton | Bus | green |
List every stop
- Kramer Center
- 2 Martin Court
- Shore Stop SB
- DCT Depot
- American Legion
- High's Citgo
- Cambridge Visitor's Center
- High & Choptank WB
- Goldsborough and Calvert EB
- Veterans Clinic Cambridge
- Beaver Neck Village EB
- Shell Station EB
- YMCA
- Railroad Ave. EB
- Transfer/Calvert St.
- Railroad Ave. WB
- Shell Station WB
- Beaver Neck Village WB
- Veterans Clinic Cambridge WB
- Main St. East New Market EB
- B & G
- Waddells Corner
- Old Provident State Bank
- Senior Center
- Main St. Preston
- New Provident State Bank
- Waddells Corner SB
- Easton Post Office
- 301 Bay St. (Social Services) Easton
- Target
- St. Michaels Village
- Choptank Community
- Inn at Perry Cabin
- 113 Mitchells St.
- The Greens
- St. Michaels Library
- Grauls Market
- Target
- Post Office EB
- Mulberry Hill
- Pippin Farm
- Corner Carry Out
- Easton Neighborhood Service Center
- Chatham Village
- Magnolia Meadows
- Chesapeake College
- The Greens
- The Comfort Inn
- Bob Evans/Panera Bread
- 612/Greyhound/MVA
- Airport Industrial Park
- Denton Plaza
- Easton Giant
- Doverbrook
- Rite Aid (Easton Plaza)
- Kohl's - Easton
- Hyatt
- Food Lion - Easton
- Acme - Easton
- Parkview
- Panera Bread
- Commerce Dr.
- St. Mark's Village
- Easton Safeway
- Easton Library
- East Ave. at Goldsborough
- Crusader & Meteor
- Walmart
- Crusader & Roslyn
- Maryland & Killarney
- Maryland & Dorchester
- Dorchester General Hospital Byrn & Aurora
- Byrn & Hayward
- Spring St / Library
- Long Wharf
- Water St. (Yacht Club)
- West End & School
- School & Belvedere
- Fresh and Green's
- Somerset & Glasgow
- Judy Center
- Talbot & Tubman (YMCA)
- Travers & West End
- Zip Mart
- DGH Byrn & Aurora EB
- Maryland & Dorchester EB
- Dorchester & Cedar (Health Department)
- Shoal Creek Mall EB
- Food Lion
- Shoal Creek Mall
- Washington & Front
- Bradford House (Across St.)
- Fassett Magee
- High & Park
- Washington & High
- Washington & Leonard
- Conifer Village II
- Conifer Village I
- Washington & Foxtail
- Washington & Greenwood
- Bayside Foods
- Greenwood & Cosby
- Glenburn & Glover
- Race @ Craigs
- Race @ Tolleys
- Community Action Center
- Washington & Goodwill
- Peachblossom & Robbins
- Robbins & Pine
- High & Robbins
- Pine & Bradley
- Dutchmans Lane
- Baywood Court
- Goldsborough & Bayly
- Bayly & Maces
- Cambridge Commons
- Chesapeake at DCT
- Rt. 16 & Stone Boundary
- Cambridge Club Apts.
- Stepping Stones (ESHC)
- Southside & Gypsy
- Lance & Shane
- Rebecca & Southside
- Rose's Store
- Fieldcrest Dr. (Detention Ctr.)
- Woods at CorPak
- Marshy Hope
- Dollar General
- Southern States
- Rhode's Store SB
- Shopping Center
- Goldsborough & Calvert
- High & Choptank
- 612/Greyhound
- Shopping Center NB
- 510 Idlewild Ave
- Rhode's Store NB
- Kingstown Apartments
- Kent County Library
- Kent County Community Center
- Village Circle
- HAPS Building
- Town Parking Lot
- Bethlehem Store
- Preston Shore EB
- Federalsburg Town Parking
- Cynwood
- Caroline Apartments
- Laurel Grove Apartments
- Garden Court
- Federal Manor & East Main
- Federalsburg Town Parking WB
- Preston Shore Stop
- Bethlehem Post Office
- Walmart
- Vaughn St. & School St.
- Greensboro Parking Lot
- Purdy
- Kinnamon's Gas Station
- Royal Farms Store
- Rte. 480 & Central Ave.
- Ridgely Town Hall
- Tuckahoe Garden Apartments
- Queen Anne Post Office
- Allen Harim Foods
- Allen Harim Foods NB
- Queen Anne Post Office NB
- Ridgely Town Hall NB
- Marvel Court
- Rte. 480 and Central Ave. NB
- Town Parking Lot NB
- Royal Farms Store NB
- Kinnamon's Gas Station NB
- Greensboro Parking Lot NB
- Vaughn St. and School St. NB
- Bayly & Goldsborough
- Bayly & Pine
- Pine & Robbins
- Robbins & Phillips
- Memorial Hospital (Easton)
- Phillips & Washington
- Washington & High
- Washington & Rigby
- Washington & Greenwood
- Greenwood & Cornish
- Greenwood & Park Lane
- Park & Leonard
- Leonard & Cosby
- Cornish & Rigby
- Rigby & Fairmont
- Digestive Center
- High & Park
- Race & Muir
- Race at Bradford House
- Race at Route 16
- Walmart
- Walmart EB
- Secretary Main St.
- Dockins Market
- Amick Farms Hurlock
- Goose Creek/Food Rite
- Diagnostic Center
- Federalsburg Industrial Park
- Amick Farms Hurlock WB
- Goose Creek/Food Rite WB
- Dockins Market WB
- Secretary Main St. WB
- Shore Stop
- Trappe Post Office
- Lover's Lane
- Lover's Lane SB
- Post Office SB
Over time
Overall score across the last 2 checks — unchanged since 2026-10-06.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-06 | 31.4 | first check |
| 2026-10-07 | 31.4 | 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-10-06 to 2026-10-07 (2 checks) | 207bcc4222c8 | 2022-02-26 | Current rubric: see the trend above |
| 2026-08-06 to 2026-08-07 (2 checks) | 207bcc4222c8 | 2022-02-26 | F, 31.4 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-10 (21 checks) | 207bcc4222c8 | 2022-02-26 | F, 31.4 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-06.
Same feed file as 2026-10-06; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
14 findings, ordered by severity.
Show every finding
- Error1474 instances
Stop time timepoint without times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_time_timepoint_without_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: stop_time_timepoint_without_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
feed_info.txt says this feed ends on 2022-02-26. Your service calendar runs to 2022-02-28.
The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.
Fix: Correct feed_end_date in feed_info.txt. Set it to 2022-02-28, the last day in your calendar, or to the last day your schedule is reliable. (One field in feed_info.txt, often an export setting.)
Finding code: scorecard_feed_end_date_before_calendar · Read the fix guide for scorecard_feed_end_date_before_calendar · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning212 instances
212 of 212 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)
- Warning179 instances
179 of 180 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)
- Warning21 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning20 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 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 for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date7_days · Read the fix guide for feed_expiration_date7_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: missing_feed_contact_email_and_url · Read the fix guide for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide for trip_coverage_not_active_for_next7_days · 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)
- Info4 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · Read the fix guide for service_window_outside_feed_period · 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.)
Finding code: unknown_column · Read the fix guide for unknown_column · 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. Small errors then sit in the feed for months.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1684 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 1684 days ago, so FTA would find the link out of date.
- 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 Needs attention
- 159 of 180 trips have a shape; 21 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.
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 does not meet the conformance requirements yet. Here is what the mark needs: 1 validator error to resolve. Service data expired 1684 days ago. States wheelchair access on 0% of stops and 1% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 1684 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 1% 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 1474 validator errors, 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 45 / 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 0 / 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 38 / 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.
Part of the Maryland portfolio: the same scorecards for every feed we track in that group, on one free page.
For programs that support several agencies
This scorecard and the board one-pager for Delmarva Community Transit are free, and they stay free. If you support several agencies, as a state program, a technical-assistance center, a feed vendor, or a consultancy, you can buy the program report bundle. It puts this agency's board report in one archive with the reports for the other agencies you support, and each cover carries your program's name, logo, and accent color.
The report for Delmarva Community Transit uses the same numbers as this page: grade F (31.4 out of 100) as of the check on 2026-10-07, its category scores, its top fixes, and its score at each check.
One bundle, up to 25 agencies: $149, paid once, delivered within 2 business days or refunded. Other plans, including a monthly refresh, are on the bundle page.
See a sample bundle report: a real agency's current grade, with placeholder branding.
A purchase buys no influence over grades, methodology, or which agencies are listed. The grade on this page comes from the check on 2026-10-07, scored with rubric v1.4 and MobilityData gtfs-validator 8.0.1. Based on the feed source on file; publisher ownership is not verified. Read how the grade is calculated.
Similar feeds in Maryland
Other scorecards in Maryland, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/delmarva-community-transit/2026-10-07.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-10-07. 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.