Feed status · checked 2026-08-01
Dutchess County
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in New York.
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 79 minutes ago; last changed 41 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
330 of 330 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
765 of 765 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 +15 points in its category
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points in its category
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
- 330 of 330 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
- 765 of 765 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
- The feed contains no fare information.
- Next action
- 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.
- 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. Make this change in whatever tool produces your feed, then re-export.
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. Make this change in whatever tool produces your feed, then re-export.
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.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 states that service is published through 2051-09-30. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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 your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 9 kinds of issue across 154 instances (0 error, 139 warning, 15 informational).
Service is published through 2051-09-30. It may be intentional, but confirm the end date before treating the feed as maintained.
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
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (A EXP, F, G MS, G MS1, J MS, and more).
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.
269 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Church St & Market St", "Route 9 S & Sharon Drive", "Route 9 S & Beechwood Avenue", 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 330 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.
- G MS (pink)
- L AMS (orange)
- G MS1 (pink)
- E SUN (red)
- A EXP (teal)
- A MS (green)
- A SUN (green)
- B MS (teal)
- B SUN (teal)
- C (red)
- D (pink)
- E MS (red)
- F (purple)
- J MS (purple)
- K MS (yellow)
- L SN (orange)
- L SMS (orange)
- M MF (teal)
- P MF (green)
| Route | Type | Line color |
|---|---|---|
| G MS G (BEACON FREE LOOP) MON - SAT | Bus | pink |
| L AMS L (POUGHKEEPSIE MAIN STREET - ADAMS) MON - SAT | Bus | orange |
| G MS1 G (BEACON FREE LOOP) SUN | Bus | pink |
| E SUN E (POUGHKEEPSIE - PAWLING) SUN | Bus | red |
| A EXP POUGHKEEPSIE - AMAZON EXPRESS | Bus | teal |
| A MS A (POUGHKEEPSIE - FISHKILL) MON - SAT | Bus | green |
| A SUN A (POUGHKEEPSIE - FISHKILL) SUN | Bus | green |
| B MS B (POUGHKEEPSIE - BEACON) MON - SAT | Bus | teal |
| B SUN B (POUGHKEEPSIE - BEACON) SUN | Bus | teal |
| C C (POUGHKEEPSIE - TIVOLI) MON -SAT | Bus | red |
| D D (POUGHKEEPSIE - MILLBROOK) MON - SAT | Bus | pink |
| E MS E (POUGHKEEPSIE - PAWLING) MON - SAT | Bus | red |
| F F (BEACON - HOPEWELL JUNCTION) MON - SAT | Bus | purple |
| J MS J (POUGHKEEPSIE NORTHSIDE) MON - SAT | Bus | purple |
| K MS K (POUGHKEEPSIE SOUTHSIDE) MON - SAT | Bus | yellow |
| L SN L (POUGHKEEPSIE MAIN ST - STOP & SHOP/ADAMS) SUN | Bus | orange |
| L SMS L (POUGHKEEPSIE MAIN ST - STOP & SHOP) MON - SAT | Bus | orange |
| M MF M (POUGHKEEPSIE EASTSIDE) MON - FRI | Bus | teal |
| P MF P (POUGHKEEPSIE WESTSIDE) MON - FRI | Bus | green |
List every stop
- Transit Hub
- Route 9 S & Speedway
- Pine Street & Katherine Street
- Astor
- Route 9 N & East Market Street
- Rt 9 N & Mulberry St (Dutchess County Fairgrounds)
- Tops Supermarket
- Northern Dutchess Hospital (DC Fairgrounds)
- Route 9 S & Hyde Park Mall
- Route 9 S & East Market Street
- Route 9 N & Route 199 (Firehouse Plaza)
- Route 9 N & East Market Street
- Route 9 S & IBM Road (Hudson Valley Credit Union)
- Route 9 N & Mills Cross Road
- Route 9 S & Education Lane (Anderson Center)
- Route 9 S & West Market Street
- Route 9 & Crumwold Place
- Route 9 S & St Andrews Road
- CR 41 (East Market Street) W & Route 9G (Violet Avenue)
- Fulton Street E & Beck Place (Marist College)
- Route 9 S & West Dorsey Lane (CIA)
- Route 9G (Violet Ave.) & West Dorsey Lane
- Route 9 S & Anthony Drive
- Fulton Street W & Route 9G (Violet Ave.)
- Fulton Street W (across from Beck Place)
- Washington Street & Verrazano Boulevard
- Route 9 S & Route 9G (Across Wey Road)
- FDR Home
- Route 44/55 West & Corlies Avenue
- Route 44/55 West & Maplewood Apartments
- Route 44/55 West & Smith Street
- Veteran's One Stop
- Route 9 S & Neptune Road
- Church Street East & Market Street
- Route 44 & Burnett Blvd
- Route 44 & Rochdale Road
- Route 44 & Town Hall
- Route 44 & Washington Hollow Plaza East
- CR 95 & Eastern Dutchess Govt. Center
- Front Street & Franklin Avenue
- Route 44 & Arlington Square
- Route 9 S (Across from Olive Garden)
- Route 44 & Arnoff
- Route 44 & ACME
- Vassar Garden Apartments
- Route 44 & Chase Bank
- Route 44 & Washington Hollow Plaza West
- Poughkeepsie Galleria
- Route 44 & Pleasant Valley Bike Shop
- Route 44 & Hillside Terrace Apts.
- Route 44 & Magurno Lane
- Adams Fairacre Farms & Route 44
- Route 44 & Dutchess Center
- iPark Blvd S & Route 52
- iPark Blvd S & South Drive
- iPark
- Amazon (Across from parking lot)
- The Shoppes at South Hills @ ShopRite
- Route 55 W & Hudson River Housing
- Route 55 E & Burnett Boulevard
- Route 55 E (Cutout) & Old Manchester Road
- Rt 55 W & Commerce Street
- Tops / Daily Planet
- Route 55 West & Route 82
- Route 55 & CR 21 (Bruzgal Road)
- Beekman Stop & Shop
- Route 216 & Route 55 West
- Chamber of Commerce
- Route 9 N & Olive Garden
- King's Apartments
- Hannaford
- Church Street East & May Street
- Route 22 North (Across from Big W BBQ)
- Cousins Cafe
- Big W BBQ
- Rt 55 East & Firemens Way (Cutout)
- Route 55 East & Route 82
- Route 55 East & E. Noxon Road
- Route 55 East & Route 216
- Route 9 N (Across from Neptune Road)
- iPark Blvd N & Route 52
- iPark Blvd N & Old Lime Kiln Road
- iPark (Across from East Drive)
- Amazon (parking lot side)
- Hopewell - Acme Plaza
- Route 9 N & Elm Street
- Main St & Route 9
- Route 9 S & Elm Street
- Route 9 N & Casperkill Golf Club
- Route 52 W (Main Street) & Church Street
- Route 52 (Fishkill Ave) & Main Street
- Teller Avenue & Main Street
- Westage Drive & Route 9 South
- Route 9 N & Schuyler Blvd Hotels
- Mill Street & Dongan Place
- Route 9 N & Kingwood Park
- Beacon Post Office - Veterans Place & Henry Street
- Beacon Train Station
- Dia
- Beacon Theater
- Main Street & Route 52 (Fishkill Avenue)
- East Main Street & Main Street
- Route 376 & CR 77 (Vassar Road) Eastside
- CR 77 (Vassar Road) & Route 9
- Route 9D (Wolcott Avenue) & Jordan Road
- Route 9D & Beacon Street
- Route 9 N & Verizon
- Teller Ave & Fowler St
- Howland Avenue & East Main Street
- Route 9D (Wolcott Avenue) & Howland Avenue (Mount Beacon)
- Tioranda Avenue & Route 9D (Wolcott Avenue)
- CR 77 (Vassar Road) & Route 376
- Route 9 N & CR 77 (Vassar Road)
- Route 9 N & Poughkeepsie Plaza
- DCC - Washington Hall
- Fairmont Avenue & Main Street
- Hudson Plaza @ Price Chopper
- Route 9 S & Red Robin
- Barnes & Noble @ Post Road Plaza
- Poughkeepsie Plaza - Marshalls
- Route 9 N & Beechwood Ave
- Stop & Shop @ Post Road Plaza
- Fairmont Avenue & Route 44/55
- Washington Street & Department of Mental Health
- Route 9 N & Ledges Drive (Royal Ledges)
- Route 9 N & Education Ln (Across Anderson Center)
- Rt 9 N & Anderson School Rd (Across Renaissance)
- Rt 9 S & Anderson School Rd (Renaissance Center
- Route 9 N & Sharon Drive
- Route 9 S & Old Post Road (Mills Mansion)
- Route 9 N & Haggerty Hill Road
- Route 9 S & Fox Hollow Road
- Route 9 N (Across FDR Drive)
- Route 9 S & FDR Drive
- MidHudson Regional Hospital (Helipad)
- West Cedar Street W & Garden Street Ext
- West Cedar Street W & North Road
- West Cedar Street E & North Road
- West Cedar Street E & Garden Street Ext
- South Avenue/Market Street & Montgomery Street
- Montgomery Street W & South Hamilton Street
- Hooker Avenue & Ferris
- Hooker Avenue & South Grand Avenue
- Vassar Farm Project
- Rt 9 S & Westside Plaza
- Rt 9 S & Colonial Dr
- South Clinton & Hooker
- Poughkeepsie Library North
- Route 9G (Violet Ave) & Bahret Avenue
- Route 9N & Fulton St (Across from Marist)
- Route 9 S @ Marist North Road Gate
- Washington Street & Clark Street
- Washington Street (Across from Clark Street)
- Rt 9 S & Wenliss Terrace
- MidHudson Regional Hospital (Gazebo)
- Cottage Road W & Cheney Drive
- ShopRite @ Hudson Heritage
- Washington St & Mansion St-Across from Interfaith
- Washington Street & Mansion Street (Interfaith Towers)
- Mansion Street & Washington Street
- Mill Street & Charles Street
- Route 9 S & Middlebush Road
- Vassar Brothers Medical Center
- St. Simeon Apt - Second Mile Drive
- Sharon Drive & Spring Manor W
- Sharon Drive & Spring Manor E
- Ferris Lane & Hooker Avenue
- St. Simeon Apt - Maple Grove Lane
- Route 9 N & Hudson Heritage
- Poughkeepsie Train Station
- Rt 9 S & Hark Plaza
- Main Street & South Perry Street
- Main Street & Market Street
- Main Street E & South Hamilton Street
- Main Street E & South Cherry Street
- Main Street E & Church Street
- Main Street E & Worrall Avenue
- Fairmont Ave & Collegeview Ave (Vassar College)
- Collegeview Ave & Fairmont Ave (Vassar College)
- Main Street E & Raymond Avenue
- Rt 9 S & Church St
- Route 44 W & Burnett Boulevard
- Stop & Shop
- Kmart
- Main Street W & Raymond Avenue
- Main Street W & North Grand Avenue
- Main Street W & Innis Avenue
- Main Street W & Jewett Avenue
- Merritt Blvd. Rt. 9 North (Across from Walmart)
- Main Street W & North Cherry Street
- Main Street W & North Hamilton Street
- Raymond Avenue & Lagrange Avenue
- Raymond Avenue & Collegeview Avenue
- Main Street E & Streit Avenue
- Main Street E & Academy Street
- Main Street W & Catharine Street
- North Hamilton St (Across from Family Partnership)
- Walmart (Fishkill)
- Route 44/55 W (Maple Street) & Innis Avenue
- Innis Ave - Ridgefield Apartments (North Entrance)
- Innis Avenue & Salt Point Tpk
- Hudson Avenue W (Across from Howard Street)
- Weed Street & Smith Street
- Mansion Street W & Smith Street
- Mansion Street W & North Clinton Street
- Mansion Street E & North Hamilton Street
- Mansion Street E & Smith Street
- Smith Street & Weed Street
- Dutchess Mall
- Lakeview Arms Apartments
- Salt Point Tpk & Innis Avenue
- Innis Avenue - Royal Cove Apartments
- Innis Ave S & Main St
- College Avenue E & Meyer Avenue
- College Avenue W & Worrall Avenue
- Meyer Avenue & Hooker Avenue
- Hooker Avenue & Wilbur Boulevard
- Main Street & Veterans Place
- Cannon St & Clinton St
- Montgomery Street W - Eastmin & Bixby
- Mansion Street E & North Clinton Street
- Fulton Avenue & Worral Avenue
- Worrall Avenue & Main Street
- Montgomery Street E & South Hamilton Street
- Forbus Street W - Poughkeepsie HS
- Poughkeepsie Middle School
- Rt 9 N & Red Line Diner
- Whinfield Street & Delafield Street
- Spruce Street E & Delafield Street
- Bain Avenue E & Talmadge Street
- Forbus Street W & South Cherry Street
- Forbus Street E (Across from Poughkeepsie HS)
- Forbus Street & South Cherry Street
- Innis Ave - Ridgefield Apartments (South Entrance)
- King Street & Innis Avenue
- Mansion Street E & Garden Street
- Rt 9 S & W Merritt Blvd
- College Ave (across from Poughkeepsie MS)
- Rinaldi Boulevard N & Main Street
- Mansion Street E & Catharine Street
- Orchard Place & Taylor Avenue
- Washington Street & Bain Avenue
- Bain Avenue W & Talmadge Street
- Spruce Street W & Delafield Street
- Mill Street & North Clover Street
- North Clover Street & Main Street
- Rt 9 N & Commonwealth Ave (ShopRite)
- Rinaldi Blvd S & Main
- Gerald Drive E & Rinaldi Boulevard
- Gerald Drive E & Rinaldi Boulevard
- and 80 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 63.3 | first check |
| 2026-07-30 | 63.3 | no change |
| 2026-07-31 | 63.3 | no change |
| 2026-08-01 | 63.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-31.
Same feed file as 2026-07-31; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
13 findings, ordered by severity.
Show every finding
- Warning765 instances
765 of 765 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)
- Warning330 instances
330 of 330 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)
- Warning85 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning19 instances
Some rider-facing names are in ALL CAPS or all lowercase.
ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning18 instances
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning11 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 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 · 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 · 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 · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info12 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
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. (Varies.)
Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info3 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)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Finding code: scorecard_no_feed_contact · 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 765 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 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 11 of 330 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. 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 61 / 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 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.
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/dutchess-county/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.