Feed status · checked 2026-09-18
City of Hattiesburg
Based on the official feed source on file
Service mode Bus
First scorecard for this agency
Catalogued in Mississippi.
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.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
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
190 of 190 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
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
Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Same name and description for stop (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +8 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
- 190 of 190 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
- 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
- Feed evidence
- Same name and description for stop (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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 for scorecard_wheelchair_boarding_unknown
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 for scorecard_no_fare_data
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.
Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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's last published service date is in 370 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 89.3% 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 4 kinds of issue across 190 instances (0 error, 189 warning, 1 informational).
Service data covers the next 370 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 (Blue Line).
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.
172 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Main St and W Front", "Main St and New Orleans St", "On McLeod St By Fire Station No.1", 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 190 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.
- Blue Line (teal)
- Green Line (green)
- Gold Line (yellow)
- Red Line (red)
- Orange Line (orange)
- Brown Line (black)
- Purple Line (purple)
| Route | Type | Line color |
|---|---|---|
| Blue Line Hardy Street | Bus | teal |
| Green Line 4th Street | Bus | green |
| Gold Line USM | Bus | yellow |
| Red Line Country Club Road | Bus | red |
| Orange Line Broadway Drive | Bus | orange |
| Brown Line 7th Street | Bus | black |
| Purple Line Palmer's Crossing | Bus | purple |
List every stop
- Train Depot
- Main St and W Front
- Main St and New Orleans St
- On McLeod St By Fire Station No.1
- On Hardy St @ Main Library
- Hardy St and Hutchinson Ave.
- Hardy and 17th St. (Across Zoo)
- Hardy St and Park Ave.
- Hardy St and 20th Ave
- Hardy St and 25th Ave
- Hardy St and USM Rose Garden
- Hardy St and 30th St (JR Gas Station)
- Hardy St and Ross S t(34h St)
- Hardy St and 36th St
- Hardy St and 38th St
- Hardy St and N 40th Ave
- Hardy St and Coco Cola Ave
- Hardy St (Across from McDonalds)
- Wesley (Green Eye Institute)
- Wesley (Front Entrance)
- Wesley (Millsaps Dr)
- Turtle Creek mall 1
- Turtle Creek Mall 2
- Turtle Creek Mall 3
- Cross Creek Parkway (Across Bed Bath and Beyond)
- Walmart
- Hardy St (Lowes)
- Hardy St (TJ Max)
- Hardy St (Shell Gas station)
- Hardy St (McDonald's)
- Service Rd (Best Buy)
- Georgia Blue
- Hardy St and 38th Ave
- Hardy St and 34th Ave
- Hardy St and 30th Ave
- Hardy St and 29th Ave
- 28th Ave @ Pine Grove Health Center
- Hardy and 28th Av
- Hardy St and 25th Ave
- Hardy and 21st Ave
- Hardy St and Park Ave(Shelter)
- Hardy and 17th Ave. (Zoo)
- Hardy St and Hutchinson Ave.
- Hardy St and Pinehurst St
- Hardy St and Mamie St
- Hardy St and 1st Ave
- Front St and Forrest St.
- Main St and Short St
- Buschman St and River Av
- Walmart @ 49
- Mc Innis St and Washington St
- Service Dr @ Glory Bound
- Service Rd @ Hillcrest
- 4th St and Eagle Walk
- W 4th St and USM Coliseum
- Thornhill Dr @ Mark IV Apartments
- Grand Theatre
- Montague Blvd and 40th Ave
- Pearl St and 38th Ave
- N 38th Av and Hardy
- River Ave and Williams St
- Mc Innis and Tipton
- Tipton St and Rebecca St
- Tipton St and Alcorn St
- James St and Alcorn St
- Edwards St and Duke St
- Edwards St and Tuscan Av
- Cypress St and Penton St
- Wills Av and John St
- Katie St and Charles St
- Hall St and Dabbs St
- 6th Av and W Pine St
- Edwards St and Katie St
- William Carey and Tuscan Av
- Broadway Dr and Corinne St
- Broadway Dr and Timothy Ln
- Bartur St and Broadway St
- On Service Rd at Waffle House
- On Service Rd near Popeye's Chicken
- Service Road and Cloverleaf Dr
- On Service Rd by Walmart
- Roosevelt Blvd Before Lincoln Rd
- Lincoln Rd at Central Sunbelt Bank
- W Pine St by Service Dr
- W Pine St by Health Dept
- Timothy Ln and Broadway
- Broadway Dr and Florence Ave
- W Pine St and 6th Ave
- W Pine St and 1st Ave
- Briarfield Apt and E 2nd
- E 2nd St and Mobile St
- Mobile St and E 4th St
- Mobile St and E 7th St
- E 7th St and Fairley St
- E 9th St and Bouie St
- E 9th St and Mobile St
- E 9th St and Memphis
- Coit St and Lula
- Coit st and Hwy 42
- US Hwy 42 and Redus St
- US Hwy 42 and Glendale Ave
- US Hwy 42 and Pritchard St
- US Hwy 42 and Cahal St
- US Hwy 42 at Health Dept.
- Service Dr and N 31st Ave
- N 31st and Hwy 49
- Campbell Dr at Mark Apartment
- Campbell Dr and Overlook Apartments
- Beverly Hills Dr and Plantation Apartments
- Bevelry Hills and 37th
- W 7th St and N 31st Ave
- W 7th St and Service Dr
- W 7th St and 25th Ave
- W 7th St and 19th St
- W 7th St and Oliver Av
- W 7th St and North St
- W 7th St and Main St
- Main St and 4th St
- Main St and Eaton St
- Hillcrest
- Stadium Ave @ Athletic Center
- Eagle Walk and College Dr
- Southern Miss Dr and W Memorial Dr
- W Memorial Dr @ Hardy St
- North 31st @ Pearl St
- Pearl St @ N 34th Ave
- N 35th Ave @ Montague Blvd
- Montague Blvd @ CuBard School
- Golden Eagle Ave @ Montague Blvd
- Golden Eagle Ave @ Charles Lane Dr
- 4th Street @ Moffet Health Center
- On Service Rd near Cspire
- On Service Rd near Popeye's Chicken
- Bartur St and Broadway St
- S 17th St and Service Rd
- Service Dr and W Pine St
- Lincoln Rd and Hill St (Central Sunbelt)
- Lincoln Rd and Roosevelt Blvd (dollar general)
- 28th Ave at Winn Dixie
- 28th Ave and McInnis Loop
- McInnis Loop at Greenbriar Apts
- McInnis Loop near Disability office
- McInnis Loop and Country Club Rd
- Country Club Rd at Bonhomie Apartments
- Country Club Rd at Pineview Apartments
- Country Club Rd at the park
- Country Club Rd and Killingsworth Dr
- Dumas Av and Martin Luther King Av
- Martin Luther king Av and Tuscan Av
- William Carey Pkwy and Tuscan
- William Carey Pkwy at Wisteria Apartments Entrance 1
- William Carey Pkwy at Wisteria Apartments Entrance 3
- William Carey Pkwy and Dosset St
- William Carey Pkwy at JR (Just before entering HWY 49)
- Service Dr and Fred's Pharmacy
- Service Dr and Carriage Inn
- Main St and Buschman St
- Bay St and Rebecca Av
- Lilac St and Hattiesburg St
- Edwards St and Dixie Pine Rd
- Edwards St and Fellowship Center
- Edwards St and Barkley Rd
- Edwards St and Central School Rd
- Old Airport Rd and Edwards St
- Old Airport Rd at Family Health Center
- Old Airport Rd and Chancellor Rd
- Old Airport Rd and Hattiesburg Ave
- Sullivan St at Palmer's Crossing Apartments
- Tatum Rd and Hood Rd
- Tatum Rd and Stepts Ave
- Travillion Rd and Stepts Ave
- Tatum Industrial Dr at Georgia Pacific
- Tatum Industrial Dr at Kohler
- Woodall Tech Center
- S Hill Dr and Tatum Industrial Dr
- JM Tatum Industrial Dr at DMV
- PRCC
- Edwards St and Central School Rd
- Edwards St and Barkley Rd
- McCall St and Collins Rd
- McCall St and Dixie Pine Rd
- Lilac St and Hattiesburg St
- Tuscan St and Edwards St
- Edwards St and Duke Av
- Edwards St and Katie St
- Bay St and Rebecca Av
- Main St and Buschman St
- Midtown stop 28th st
- Mamie St and Hospital Entrance
- 4th St and Virginia Dr
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
8 findings, ordered by severity.
Show every finding
- Warning190 instances
190 of 190 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)
- Warning180 instances
Same name and description for stop (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_name_and_description_for_stop · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning14 instances
14 of 131 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)
- Warning8 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)
- 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
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)
- 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 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 370 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 131 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
One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 89% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 370 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 89% 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 370 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 82 / 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 51 / 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/city-of-hattiesburg/2026-09-18.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-09-18. 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.