Feed status · checked 2026-08-01
Citibus (Narbonne)
Based on the feed this agency publishes
Service mode Bus
down 0.4 since 2026-07-31
Catalogued in Occitanie, France.
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 5 hours ago; last changed 4 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
496 of 511 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 +24 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
1335 of 1335 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
- 496 of 511 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
- 1335 of 1335 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. See this feed's finding-clearance log.
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. See this feed's finding-clearance log.
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. 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 30 days.
- Published accessibility data
- Accessibility information is stated for 2.9% 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 13 kinds of issue across 3180 instances (0 error, 3174 warning, 6 informational).
Service data covers the next 30 days.
3% of stops state wheelchair accessibility (3% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
3% of stops state accessibility (3% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10, TPMR).
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.
1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Collège St Louis de Gonzague").
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 511 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (yellow)
- 10 (red)
- 11 (yellow)
- 12 (white)
- 13 (green)
- 14 (purple)
- 15 (brown)
- 16 (yellow)
- 17 (gray)
- 2 (teal)
- 3 (pink)
- 4 (yellow)
- CIT1 (red)
- CIT2 (green)
- 18 (yellow)
- TAD_Corbieres (yellow)
- TAD_Littoral (teal)
- TAD_Minervois (pink)
- TPMR (pink)
| Route | Type | Line color |
|---|---|---|
| 1 Bonne Source - Saint-Jean Saint-Pierre / Centre Commercial La Coupe | Bus | yellow |
| 10 Narbonne - Coursan - Salles-d'Aude - Fleury d'Aude - Saint-Pierre-la-Mer | Bus | red |
| 11 Narbonne - Armissan - Narbonne-Plage | Bus | yellow |
| 12 Narbonne - Gruissan | Bus | white |
| 13 Narbonne - Prat-de-Cest - Sigean / Leucate | Bus | green |
| 14 Narbonne - Bages - Peyriac-de-Mer - Portel-des-Corbières - Sigean - Port-La Nouvelle | Bus | purple |
| 15 Narbonne - Montredon-des-Corbières | Bus | brown |
| 16 Narbonne - Moussan - Saint-Marcel-sur-Aude - Marcorignan | Bus | yellow |
| 17 Narbonne - Cuxac-d'Aude - Ouveillan | Bus | gray |
| 2 Bonne Source - Centre Commercial La Coupe | Bus | teal |
| 3 Sainte-Louise - Réveillon | Bus | pink |
| 4 Montesquieu - Crabit | Bus | yellow |
| CIT1 Citadine 1 - Centre-ville de Narbonne | Bus | red |
| CIT2 Citadine 2 - Parking relais Maraussan - Parking relais Carnot | Bus | green |
| 18 Gruissan - Narbonne-Plage - Saint-Pierre-la-Mer | Bus | yellow |
| TAD_Corbieres TAD Corbières | Bus | yellow |
| TAD_Littoral TAD Littoral | Bus | teal |
| TAD_Minervois TAD Minervois | Bus | pink |
| TPMR | Bus | pink |
List every stop
- Bonne Source
- Maréchal Juin
- Karl Marx
- Route de Saint Pons
- Beaumont
- Sécurité Sociale
- Coopérative
- Lacroix
- Forum Sud
- Fresquet
- Tamaroque
- France Travail
- Coopérative
- Jean Jaurès
- ZI Plaisance
- Aire
- La Pascuale
- Charles Trenet
- Aire
- Quatourze
- Gare SNCF
- Alaric
- ZI Plaisance
- Pierre Curie
- Tennis
- Clos des Palombes
- Arago
- Centre Commercial Plage
- Route des Plages
- Commerces
- Espace de Liberté
- Hôpital
- Ulysse
- Votaire
- Gare Routière
- Louise Michel
- Jean Jaurès
- Palais du Travail
- Gare Condorcet
- Europe
- République
- Les 3 Moulins
- Route de Perpignan
- Louise Michel
- Les pêcheurs
- BAGES Prat de Cest
- Horte Neuve
- Primevères
- Saint-Jean Saint-Pierre
- Centre Hospitalier
- Le Lavoir
- Jardins de la Mer
- Gare SNCF
- Pierre Curie
- Maison de la Mer
- La Poste
- Cimetière de Bourg
- Cave Coopérative
- Noctambules
- PEYRIAC-DE-MER Tramontane
- Boulevard 1830
- ZI Peyriac
- Roches Grises
- La Corniche
- Lavoisier
- Elysiques
- Mairie
- Brunelière
- Le Parc
- Anatole France
- Lebrettes
- Gare SNCF
- Le Lavoir
- Cimetière de L'Ouest
- La Placette
- Palais de Justice
- Ferroul
- La Poste
- Cave Coopérative
- Razimbaud
- Espace de Liberté
- Ortuno
- Le Parc
- Perles d'Azur
- Cave Coopérative
- Tamaroque
- Théâtre
- Chemin de Ronde
- La Ginesto
- Maison des Associations
- Les Platanes
- Soleil
- Gare Carnot
- ZA Mangefer
- Boulevard 1830
- Brunelière
- Bas de Razimbaud
- Pôle d'échange Montredon
- Soleil
- Clos des Lentisques
- Les Platanes
- Chemin de la Caune
- Lavoisier
- Lamartine
- Cimetière
- Paul Vidal
- Pont de Carcassonne
- Révolution
- Saint Vincent
- Pôle d'échange Planasse
- Pôle d'échange François Mitterrand
- Alzeau
- Réveillon 1
- Technoparc Pech Perry
- Paul Carrière
- Copacabana
- Office du Tourisme
- Brassens
- Passerelle Victor Hugo
- Turenne
- Cauquillous
- Le Lamparo
- Paul Carrière
- Croix Blanche
- La Poste
- Hôpital
- Parc des Sports
- Jean Camp
- La Saignée
- Alzeau
- Cave Coopérative
- Lilas
- Réveillon 2
- Chèvrefeuille
- La Poste
- Saint Vincent
- Pont de Carcassonne
- La Croix d'Anglade
- Paul Vidal
- Lamartine
- Charles Trenet
- Chemin de Ronde
- Pharmacie
- Les Aspres
- Collège des Corbières
- Pompidor
- Camping
- Pierre de Coubertin
- Théatre
- Centre de Tri
- Les Karantes
- Pic de Nore
- Saint Augustin
- Casino
- Catalogne
- Coquelicots
- ZA Grand Canal
- Maison de Santé
- Les Cormorans
- Piscine
- PORT-LA NOUVELLE Perles d'Azur
- Cram
- Cap Soleil
- Boulevard Eschasseriaux
- Front de Mer
- Saint Cyr
- Route de Saint Pons
- La Région
- Provence
- Boulevard du Monument
- GRUISSAN CRAM
- Les Romarins
- Gare SNCF
- Pavillon
- Stade
- Pierre de Coubertin
- Office du Tourisme
- Pastouret
- Citronnier
- Chemin de la Caune
- Les Aspres
- Narbo Via
- Boulevard du Monument
- Coubertin
- La Région
- Saint Cyr
- Front de Mer
- Ovilius
- Centre Commercial Plage
- Boulevard Eschasseriaux
- Cap Soleil
- Mairie
- Baliste
- Piscine
- La Motte
- Comète
- Maison de Santé
- Chemin des Vignes
- Balnéoludique
- Catalogne
- Médiathèque
- Lacroix Gymnase
- Cave Coopérative
- Pôle Universitaire
- Grande Bleue
- NARBONNE PLAGE Office du Tourisme
- Les Hauts de Saint-Pierre
- Les Sylphides
- Cauquillous
- Jardins de la Mer
- Rives des Corbières
- Copacabana
- Saint Augustin
- Route de Perpignan
- Casino
- Cinéma
- Ecole de Voile
- Gendarmerie
- Collège St Louis de Gonzague
- Village
- Boulodrome
- Chapelle
- LEUCATE Vénus
- Chapelle
- Saint-Jean Saint-Pierre
- Centre Commercial
- La Poste
- Pic de Nore
- République
- Gare SNCF
- Las Pitchinos
- Boulodrome
- Bonne Source
- Cave Coopérative
- Gare SNCF
- République
- Centre Commercial
- OMS
- Chapelle
- Ecole de Voile
- Piscine
- Cinéma
- La Rouquette
- Rives des Corbières
- Weilheim
- BAGES Prat de Cest
- La Croix d'Anglade
- Cimetière de Bourg
- Les Hauts de Narbonne
- Vixiège
- and 261 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — down 0.4 since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 44.0 | first check |
| 2026-07-30 | 45.6 | up 1.6 |
| 2026-07-31 | 45.2 | down 0.4 |
| 2026-08-01 | 44.8 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed over time
On 2026-07-25 this feed started at grade F. On 2026-08-01 feed entered the expiry window (30 days of service left). As of 2026-08-01 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-01 Feed entered the expiry window (30 days of service left).
Everything we checked
17 findings, ordered by severity.
Show every finding
- Warning2946 instances
Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1335 instances
1335 of 1335 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)
- Warning496 instances
496 of 511 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)
- Warning144 instances
Some route lines list the same point twice in a row.
Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.
Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)
Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning71 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)
- Warning5 instances
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · 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
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)
- Warning1 instance
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)
- Warning1 instance
Transfer distance too large (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'transfer_distance_too_large' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: transfer_distance_too_large · 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)
- Info3 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Unsorted stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 · 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)
Conformance mark Not yet
This feed is close to the conformance mark. Service data runs out in 30 days; renew to qualify. States wheelchair access on 3% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 30 days; renew to qualify.
- Accessible Not yet
- States wheelchair access on 3% 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 29 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. Read the full standards crosswalk.
- Correctness 46 / 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.
- Freshness 50 / 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.
- 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/citibus-narbonne/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.