Feed status · checked 2026-07-19
Corolis (Beauvais)
Based on the feed this agency publishes
Service mode Bus
First scorecard for this agency
Catalogued in Hauts-de-France, 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.2, validator 8.0.1.
Checked for changes 5 hours ago; last changed 5 hours 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
248 of 248 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 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
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
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.
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.
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's last published service date is in 165 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% 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 5 kinds of issue across 644 instances (0 error, 631 warning, 13 informational).
Service data covers the next 165 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
7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (3, 4, 5, 7, 8, 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.
3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Dr Schweitzer", "Institution du St Esprit", "Dr Schweitzer").
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 3 (yellow)
- 4 (teal)
- 5 (yellow)
- 6 (purple)
- 7 (orange)
- 8 (gray)
- C1 (red)
- C2 (teal)
- GB (pink)
- NA (green)
| Route | Type | Line color |
|---|---|---|
| 3 Ruisselets - Délie | Bus | yellow |
| 4 Elispace/Parc Dassault - Maladrerie | Bus | teal |
| 5 Châtaigniers - Moulin de Bracheux | Bus | yellow |
| 6 Hôtel de Ville - Tillé Aéroport | Bus | purple |
| 7 Hôpital - Délie | Bus | orange |
| 8 Hôtel de Ville - Plan d'Eau du Canada | Bus | gray |
| C1 Argentine - Saint-Jean | Bus | red |
| C2 Campus Unilasalle/Hôpital - Délie | Bus | teal |
| GB Parking Saint Quentin - Hôtel de Ville | Bus | pink |
| NA Navette Express Hôtels - Tillé Aéroport | Bus | green |
This feed has 248 stops.
List every stop
- Anne Frank
- Anne Frank
- Amyot d'Inville
- Amyot d'Inville
- Allendé
- Allendé
- Ancienne Mairie
- Ancienne Mairie
- Parc des Eaux
- Parc des Eaux
- Argentine
- Argentine
- ASCA
- ASCA
- Banque de France
- Beauséjour
- Beauséjour
- Berlioz
- Berlioz
- Besnard
- Besnard
- Bizet
- Blum
- Blum
- Bois du Parc
- Bosquet
- Blancs Pains
- Blancs Pains
- Bracheux
- Bracheux
- Brière SNCF
- Brière SNCF
- Briqueterie
- Briqueterie
- Brisson
- Brisson
- Bas Romains
- Bois Brûlet
- Bois Brûlet
- Boislisle
- Boislisle
- Buzanval
- Cagneux
- Cagneux
- Calais
- Calais
- Calvaire
- Calvaire
- Préfecture
- Préfecture
- Capucines
- Caron
- Cathédrale
- Tilloy
- Tilloy
- Tilloy
- Tilloy
- Chambre des Métiers
- Chambre des Métiers
- Clos Forest
- Clos Forest
- Châtaigniers
- Chopin
- Cimetière
- Cimetière
- Cinespace
- Cinespace
- Clermont
- Clermont
- Côte d'Amiens
- Communeau
- Communeau
- Crèvecoeur
- Crèvecoeur
- Dardignac
- Dardignac
- Délie
- Délie
- Délie
- Délie
- Descartes
- Dr Schweitzer
- Dr Schweitzer
- Pressoir Coquet
- Echangeur
- Echangeur
- École
- École
- Eglise
- Église
- Elispace - Parc Dassault
- Elispace - Parc Dassault
- École Maternelle
- Esterel
- Esterel
- Europe
- Europe
- Fauqueux
- Fauqueux
- Félix Faure
- Félix Faure
- Blaise Pascal
- Blaise Pascal
- Flandres
- Franc Marché
- Gare Routière
- Gare Routière Interurbaine
- Gare Routière
- Gide
- Gide
- Gay Lussac
- Gay Lussac
- Collège G. Sand
- Halles
- Hôtel de Ville
- Hôtel de Ville
- Hôtel de Ville
- Hôtel de Ville
- Hôtel de Ville
- Hôtel de Ville
- Beauvais Centre - Hôtel de Ville
- 8 Mai 1945
- 8 Mai 1945
- Hôpital - Quai B
- Hôpital -Quai A
- Hortensias
- Hortensias
- Hostivas
- Hostivas
- Ile de France
- Ile de France
- Ile de France
- Industrie
- Industrie
- Isaac
- Isaac
- Jacinthes
- Bellevue
- Jeu de Paume
- Jeu de Paume
- J. Goddet
- Jeanne Hachette
- Jeanne Hachette
- Jean Moulin
- Jean Moulin
- Jean Racine
- Saint-Jean
- Kennedy
- Lainé
- Lainé
- Langevin
- Langevin
- Léon Bernard
- Léon Bernard
- Lebesgue
- Lebesgue
- La Garenne
- La Garenne
- La Grive
- La Grive
- Longue Haye
- Longue Haye
- Lilas
- Lilas
- Campus UniLaSalle
- Madeleine
- Maillart
- Maillart
- Maladrerie
- Maladrerie
- Marissel
- Marissel
- Marissel
- Marronniers
- Marronniers
- Moulin de Bracheux
- Moulin de Bracheux
- Aquaspace - Parc Marcel Dassault
- Métiers
- Métiers
- Montaigne
- Montaigne
- Pont d'Arcole
- Pont d'Arcole
- Aquaspace - Parc Marcel Dassault
- Paré
- Paré
- Paris
- Paris
- Pressoir Coquet
- Palais de Justice
- Place de Noailles
- Place de Noailles
- Pellerin Université
- Pellerin Université
- Peupliers
- Parc Kennedy
- Parc Kennedy
- Plan d'eau du Canada
- Prache
- Prayon
- Prayon
- Parking Saint-Quentin
- Parking Saint-Quentin
- Paul Vaillant Couturier
- Paul Vaillant Couturier
- Rimbaud
- Rimbaud
- Rostand
- Rostand
- Rousseau
- Rousseau
- Ruisselets
- Saint-Antoine
- Saint-Antoine
- Savignies
- Savignies
- Cours Scellier
- Cours Scellier
- Institution du St Esprit
- Saint-Jacques
- Saint-Jacques
- Gare SNCF
- Gare SNCF
- Songeons
- Songeons
- Stade
- Stade
- Saint-Quentin
- Saint-Quentin
- Teinturiers
- Thiérache
- Thiérache
- Tilleuls
- Tilleuls
- Trépinière
- Trépinière
- Victor Hugo
- Victor Hugo
- Vignes
- Violettes
- Vivaldi
- Vivaldi
- Zeude
- Zeude
- Aéroport
- Centre
- Église
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
9 findings, ordered by severity.
Show every finding
- Warning627 instances
On some trips the stop distances run a little past the end of the route line.
The stop and shape distance values don't quite line up, so any math that uses them can drift.
Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)
Validator rule: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning248 instances
248 of 248 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2 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.)
Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · 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.)
Validator rule: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Validator rule: route_color_contrast · 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.)
Validator rule: 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info13 instances
Some trip headsigns name a stop along the way, not the final destination.
The sign should tell riders where the bus ends up, so a midpoint name can send them the wrong way.
Fix: Set trip_headsign to the trip's last stop or its overall destination. (Usually a bulk edit in your scheduling software.)
Validator rule: trip_headsign_matches_intermediate_stop · 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.)
Validator rule: 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. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 165 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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 165 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 79 / 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 52 / 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/corolis-beauvais/2026-07-19.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-07-19. 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.