Feed status · checked 2026-08-31
Réseau interurbain - Deux-Sèvres (79)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-08-30
Catalogued in Nouvelle-Aquitaine, 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 3 hours ago; last changed 12 days ago.
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
Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool
Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.
⏱ Usually an export-tool fix, not hand editing.worth about +18 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
496 of 496 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 feed_info.txt with feed_start_date and feed_end_date to your export.Likely your export tool
feed_info.txt is missing its start/end dates (the file itself is absent) Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
⏱ Two fields, set once in export settings.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
- Some trips have stop times whose distances along the route go backwards.
- Next action
- Re-generate shape distances in your export; flag to your vendor if it persists.
- 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
- 496 of 496 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
- feed_info.txt is missing its start/end dates (the file itself is absent)
- Next action
- Add feed_info.txt with feed_start_date and feed_end_date to your export.
- 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.
Re-generate shape distances in your export; flag to your vendor if it persists.
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 feed_info.txt with feed_start_date and feed_end_date to your export. · 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's last published service date is in 341 days.
- Published accessibility data
- Accessibility information is stated for 87.7% 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 11 kinds of issue across 1042 instances (31 error, 450 warning, 561 informational).
Service data covers the next 341 days.
88% of stops state wheelchair accessibility (0% marked accessible, 88% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
88% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (101, 102, 103, 109, 145, 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.
27 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Pôle Multimodal/SNCF/CV (2)", "RD 744", "CIMETIERE - LEP RD939", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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 603 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.
- 102 (brown)
- 10246 (white)
- 100 (pink)
- 146 (orange)
- 145 (green)
- 103 (purple)
- 144 (white)
- 147 (red)
- 148 (blue)
- 149 (red)
- 104 (yellow)
- 101 (gray)
- 109 (blue)
- 950 (white)
- 7 (gray)
| Route | Type | Line color |
|---|---|---|
| 102 Ligne 102 Thouars Parthenay | Bus | brown |
| 10246 Ligne 102-146 Thouars/Niort | Bus | white |
| 100 Ligne 100 Bressuire Parthenay Poitiers | Bus | pink |
| 146 Ligne 146 Parthenay Niort | Bus | orange |
| 145 Ligne 145 Bressuire Niort | Bus | green |
| 103 Ligne 103 Bressuire Cholet | Bus | purple |
| 144 Ligne 144 Cerizay Coulonges sur l'Autize Niort | Bus | white |
| 147 Ligne 147 St Maixent l'Ecole Niort | Bus | red |
| 148 Ligne 148 Sauzé Vaussais Melle Niort | Bus | blue |
| 149 Ligne 149 Chef Boutonne Niort | Bus | red |
| 104 Ligne 104 Bressuire Thouars | Bus | yellow |
| 101 Ligne 101 Thouars Poitiers | Bus | gray |
| 109 Ligne 109 St Maixent l'Ecole Parthenay | Bus | blue |
| 950 Ligne virtuelle | Bus | white |
| 7 Ligne 7 Poitiers Nantes | Bus | gray |
List every stop
- Place des tanneries
- CENTRE BOURG
- place du Boël St-Charles
- place de la mairie
- collège François Villon
- CENTRE-BOURG
- Bouillé D28
- Soulièvres Repéroux route d'Airvault
- Le Chillas rue des forgerons
- La Roche D121
- Bouillé route de Niort
- Soulièvres Barroux place de l'église
- Route de Parthenay
- Soussigny route d'Airvault
- place du cygne
- LA RIMOIRE ABRIBUS
- centre bourg
- lycée Jean Moulin
- pont Desmoulines
- gare
- LEP GRIPPEAUX
- Repéroux place de la mare
- ZAC DES LOGES
- place du Boël les halles
- Boucoeur route de Saumur
- CAMPUS DES METIERS
- Vallon-Thiors
- Avenue des platanes
- Route de St-Varent
- gare avenue Victor Hugo
- GARE ROUTIERE
- l'Herpinière
- collège Jean Rostand
- Riblaire route de Parthenay D 938
- gare sncf
- Place du 14 juillet
- la Bourelière ancienne école
- LYCEE ERNEST PEROCHON
- GARE
- MONTPLAISIR ABRIBUS
- PAUL GUERIN Cour
- BASE DE LOISIRS
- PLACE DES MARRONNIERS
- CENTRE
- BIZARD
- Z.A DES LUCS
- MAIL LUCIE AUBRAC
- CURIE
- PLACE DE STRASBOURG
- PLACE DU CHAMP DE FOIRE
- SAINT-PARDOUX RAMBAUDIERES
- AVENUE FRANCOIS MITTERRAND
- PLACE DE LA BRECHE
- MONTPLAISIR RD743
- ST DENIS
- ANDROLET ABRIBUS
- St J.de Compos/St Eloi
- Avenue de Nantes
- Les Treilles (2)
- Pôle Multimodal
- VILLENEUVE BOURG
- CENTRE TER
- Gare SNCF
- MOULIN JACQUET
- Les Treilles
- VILLENEUVE
- LA RACONNIERE RN149
- GARE ROUTIÈRE TER QUAI B1
- Campus des Sicaudières
- Place Malabry
- LES TREILLES
- VIADUC LEON BLUM
- POLE MULTIMODAL
- Avenue de Nantes (2)
- Centre (2)
- TERRES ROUGES
- Pôle Multimodal/SNCF/CV (2)
- AVENUE DE NANTES
- CENTRE
- ZONE ARTISANALE
- Centre
- CENTRE BOURG
- Pôle Multimodal (2)
- CENTRE BOURG GYM
- RUE FLEMMING
- Gare Viaduc
- HOPITAL
- LA GRIMAUDIERE
- St J.de Compos/St Eloi (2)
- LES VAUX CRF N149
- POLE CLEMENCEAU
- LE BREUIL CRAMARD
- Le Dolmen (DISS)
- Le Dolmen (DISS) (2)
- Pôle Multimodal/SNCF/CV
- Gare SNCF
- LABORDE
- CENTRE BOURG
- EREA F DOLTO
- CENTRE BOURG
- LEO DESAIVRES
- ST ANDRE NIORT
- RD 744
- LYCEE VENISE VERTE
- CENTRE-BOURG
- ECOLE PUBLIQUE
- COLLEGE LOUIS MERLE
- COLLEGE SAINT JOSEPH
- ROUVRE-ECOLE
- JEAN MACE
- CENTRE BOURG
- PLACE DE L'EGLISE
- CENTRE-BOURG
- PLACE MAIRIE ABRIBUS
- Rorthais Centre Bourg
- ALPHAPARC
- LA FAYE ABRIBUS
- GARE SNCF
- MOUTON BLANC
- LE PEU
- PLACE SAINT HUBERT
- BROSSARDIERE
- AVENUE DES CALINS
- EDOUARD COLBERT
- BEGROLLES
- ECOLE ABRIBUS
- LE VIVIER
- LEP HORTICOLE
- RABELAIS
- GRIGNON
- SALLE COMMUNALE
- LES CINQ CHEMINS
- CENTRE
- CENTRE-BOURG
- GUILBEAU
- LE MAZUREAU
- ESPACE JACQUES BREL
- CENTRE BOURG
- CENTRE-BOURG
- BUFFEVENT
- LES DEVISES BDC
- LE BOUT DU JOUR
- ECOLES
- GENÈVE
- TOURTERON
- CHAMPBERTRAND
- COLLEGE HENRI MARTINEAU
- LE PAIN PERDU
- Centre Bourg
- EGLISE
- MAIRIE
- MAGNE
- MAIRIE
- EGLISE
- MAISONS ROUGES
- Rochereaux
- LES VERDILLONS
- LEP JEAN MAIN
- LE BREUIL ABRIBUS
- ROUTE DE FOMPERRON
- PLACE DENFERT ROCHEREAU
- BONNEUIL CRF
- LES GROIES PERRONS
- Z.A. CHAMPS ALBERT
- L'HELIANTE
- RTE DE LA MOTHE
- RUFFIGNY ABRIBUS
- LE FRAPPIER
- CENTRE BOURG
- LA GUITTIERE
- KADORE
- BELLUNE ST ANDRE
- CENTRE-BOURG
- CENTRE ROUTIER
- ZA DE BAUSSAIS
- GARE SNCF
- MAIRIE
- PAUL GUERIN Champommier
- ROUTE DE NIORT
- PETITE ISLE
- LA VILLEDIEU DE COMBLE CHAPELLE
- PLACE ABRIBUS
- AVENUE DE PARIS
- NOUVELLES HALLES
- PANIER FLEURI
- LES BROUSSES ABRIBUS
- PLACE SAINTE-MELAINE
- LYCEE AGRICOLE MELLE
- LYCEE DESFONTAINES
- PLACE DE LA GARE
- GASCOUGNOLLES
- LA VERDINIERE ABRIBUS
- PARKING RESTAURANT
- Mougon Chêne Gaurichon
- GARE SNCF
- CHAIGNEPAIN CRF GOUVANIERE
- PLACE GROUSSARD
- POLE D'ECHANGE DARWIN
- MONUMENT AUX MORTS
- LE PARAPLUIE D948
- Thorigné Croix Pillet
- MA CAMPAGNE LISA
- LA REVETIZON
- CIMETIERE - LEP RD939
- LEP LOUISE MICHEL
- Mougon Place de la Gasse
- MONUMENT AUX MORTS
- PLACE DE LA POSTE
- PLACE DU CHAMP DE FOIRE
- COLLEGE LE PINIER
- SALLE DES FETES
- LA BARBOUTE D14
- MAIRIE ABRIBUS
- LE PARAPLUIE LOT PEROT
- PARKING
- LA COLONNE ABRIBUS
- THEIL ABRIBUS D113
- PLACE DE LA POSTE
- MAT/PRIM LIMALONGES
- SALLE DES FETES ABRIBUS
- AIRE DE BRIETTE
- BOUSSANTAIN
- PLACE DES 5 VILLAGES
- COLLEGE FRANCOIS TRUFFAUT
- PLACE DE LA MAIRIE
- PLACE CAIL
- LUSSAIS ABRIBUS
- ZONE ARTISANALE
- VILAINE ABRIBUS
- LES VERGERS
- SAINT MÉDARD ROUTE DE NIORT
- CENTRE BOURG
- PLANTES
- POINTE DU MOULIN
- PLACE DE LA MAIRIE
- JAVARZAY
- LEP JEAN FRANCOIS CAIL
- LES GRAPAUDIERES
- AVAILLES
- CENTRE BOURG
- LES PLACES
- CHAMBELLE
- LA MINE D'OR
- CENTRE BOURG
- FIEF CHEVALIER
- LA PIERRIERE
- CAT RUE DU MOULIN
- CHIRON MALLET
- centre bourg
- Noirterre Centre Bourg
- and 353 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 5 checks — unchanged since 2026-08-30.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 64.5 | first check |
| 2026-08-07 | 64.5 | no change |
| 2026-08-10 | 64.5 | no change |
| 2026-08-30 | 53.8 | down 10.7 |
| 2026-08-31 | 53.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade D. On 2026-08-30 the grade moved from D to F. As of 2026-08-31 it holds grade F.
A plain-language history of this feed, newest first.
- 2026-08-30 Grade went D to F, correctness fell 24 points.
Everything we checked
18 findings, ordered by severity.
Show every finding
- Error31 instances
Some trips have stop times whose distances along the route go backwards.
Apps can show buses jumping backwards or mis-order stops.
Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)
Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning496 instances
496 of 496 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)
- Warning393 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)
- Warning74 instances
74 of 603 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)
- Warning41 instances
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 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)
- Warning4 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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)
- Warning1 instance
Between two distant stops, the times imply a speed no bus reaches.
A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.
Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.
Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)
Finding code: scorecard_missing_feed_info_dates · 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)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info491 instances
Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info450 instances
About 450 stop names are written in ALL CAPS.
Mixed-case names are easier to read in apps and are read more naturally by screen readers.
Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)
Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info70 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · 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).
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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Conformance mark Not yet
Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. States wheelchair access on 88% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 341 days.
- Accessible Not yet
- States wheelchair access on 88% 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 340 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 31 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. Read the full standards crosswalk.
- Correctness 40 / 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 85 / 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 48 / 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/fr-pan-82334/2026-08-31.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-31. 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.