Feed status · checked 2026-09-02
TIC (Compiègne)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-01
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.3, validator 8.0.1.
Checked for changes 13 hours ago; last changed 31 hours 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
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +18 points in its category
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
266 of 266 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
1214 of 1214 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
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
- Trip distance exceeds shape distance (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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
- Feed evidence
- 266 of 266 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
- 1214 of 1214 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
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.
Review the rule documentation for 'trip_distance_exceeds_shape_distance' 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. See this feed's finding-clearance log.
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.
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 70 days.
- 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 6 kinds of issue across 965 instances (47 error, 918 warning, 0 informational).
Service data covers the next 70 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
9 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (3, 4, Sco BACb, Sco DEB4b, Sco DEN b, 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.
7 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Ecole St Germain", "Ecole St Germain", "Eglise St Germain", 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 266 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)
- 2 (teal)
- 3 (red)
- 4 (purple)
- 5 (green)
- 6 (yellow)
- D1 (orange)
- D2 (teal)
- Navette HMb (brown)
- Sco BACb (gray)
- Sco DEB4b (gray)
- Sco DEN b (gray)
- Sco LYC b (gray)
- Sco MAL b (gray)
- Sco MON b (gray)
| Route | Type | Line color |
|---|---|---|
| 1 Gare - Hôpital | Bus | yellow |
| 2 Clairoix Centre - Centre Comercial Jaux-Venette | Bus | teal |
| 3 Ferdinand De Lesseps - Bellicart | Bus | red |
| 4 Gare - Bois de Plaisance | Bus | purple |
| 5 Gare - Hôpital | Bus | green |
| 6 Gare - Bois de Plaisance | Bus | yellow |
| D1 Multiplexe - Bellicart | Bus | orange |
| D2 Multiplexe - Bellicart | Bus | teal |
| Navette HMb Navette Hauts de Margny BUS | Bus | brown |
| Sco BACb Collège Ferdinand Bac - Choisy au Bac | Bus | gray |
| Sco DEB4b Collège Claude Debussy - Margny Lès Compiègnes | Bus | gray |
| Sco DEN b Collège Gaëtan Denain | Bus | gray |
| Sco LYC b Lycées de Compiègne | Bus | gray |
| Sco MAL b Collège André MALRAUX | Bus | gray |
| Sco MON b Collège Jacques Monod | Bus | gray |
List every stop
- Abbaye
- Abbaye
- Rue de l'Aisne
- Gare-Rue d'Amiens Quai B
- Gare-Rue d'Amiens Quai A
- Anatole France
- Anatole France
- Ancien hôpital
- Ancien hôpital
- Chemin d'Armancourt
- Armistice
- Opella
- Opella
- Bannière du roi
- Barbillon
- Bataillon de France
- Bataillon de France
- Belin
- Bellicart
- Bellicart
- Bernard Morançais
- Bernard Morançais
- Bournonville
- Bournonville
- Blaise Pascal
- Blaise Pascal
- Grande-Bretagne
- Grande-Bretagne
- Bournonville 2
- Bournonville 2
- Cailloux
- Cailloux
- Docteur Calmette
- Docteur Calmette
- Camp du Roy
- Capucins
- Carnot
- Carnot
- Collège Ferdinand Bac
- CIMA
- Cimetiere Nord
- Cimetiere Nord
- Clos des Roses
- Clos des Roses
- Collège Malraux
- Saint Côme
- Saint Côme
- Vivier Corax
- Vivier Corax
- Paul Cosyns
- Roger Couttolenc
- Roger Couttolenc
- Camp de Royallieu
- Camp de Royallieu
- Croix-Rouge
- Croix-Rouge
- Joseph Cugnot
- Joseph Cugnot
- Joseph Cugnot
- Centre culturel
- Centre culturel
- Delaidde
- Delaidde
- Guy Deniélou
- Guy Deniélou
- Guy Deniélou
- Robert Desnos
- Robert Desnos
- De Lattre de Tassigny
- De Lattre de Tassigny
- Domeliers Abribus
- Domeliers
- L'écharde
- L'écharde
- L'Echarde
- Eglise St Germain
- Eglise St Germain
- Carrefour d'Elblag
- Etats-Unis
- Etats-Unis
- Gambetta
- Gambetta
- Gambetta
- Gare-Jeanne d'Arc
- Ecole St Germain
- Ecole St Germain
- Glacière
- Glacière
- Docteur Guerin
- Docteur Guerin
- Harlay
- Hippolyte Bottier
- Hippolyte Bottier
- Landshut
- Landshut
- Linières
- Marronniers
- Marronniers
- Hôpital
- Hôpital
- Royaumont
- Sergenteret
- Victor Hugo
- Jean l'Huillier
- Jean l'Huillier
- Les Jardins
- Les Jardins
- Justice
- Justice
- Ferdinand de Lesseps
- Ferdinand de Lesseps
- Libération
- Libération
- Les Jardins Familiaux
- Les Musiciens
- Les Musiciens
- Centre
- Mousquetaires
- Ouïnels
- Ouïnels
- Port à Carreaux
- La Planchette
- La Planchette
- Magenta
- Maison de l'Europe
- André Malraux
- André Malraux
- Mercières
- Mercières
- Mercières
- Jacques Monod
- Jacques Monod
- Lotissement du Moulin
- Carrefour Napoléon
- Les Nymphes
- Les Nymphes
- Palais
- Parc de Loisirs
- Parc de Loisirs
- Rue de Paris
- Rue de Paris
- Picardie
- Picardie
- Piscine
- Piscine
- Place Woimant
- Place Woimant
- Pommerelles
- Pommerelles
- Port à Bateaux
- Port à Bateaux
- Parc Songeons
- Rue de Clermont
- Rue de Clermont
- Centre de recherches
- Centre de recherches
- Réservoirs
- Réservoirs
- René Firmin
- René Firmin
- Résidence intergénérationnelle
- non desservi 2ème RI
- Robida
- Robida
- Rond Royal
- Rond Royal
- Edmond Rostand
- Edmond Rostand
- Royallieu
- Camp des Sablons
- Square Bonnault
- Square Bonnault
- Sports Nautiques
- Sports Nautiques
- Soissons
- Soissons
- Solférino
- Solférino
- Salle des sports
- Sous-Préfecture
- Sous-Préfecture
- Stade du Clos des Roses
- Stade du Clos des Roses
- Stalingrad
- Saint Corneille
- Saint Fiacre
- Saint Fiacre
- St Jacques - Abribus
- Place St Jacques
- St Joseph
- Saint Joseph
- Saint Joseph
- Saint Joseph
- Saint-Lazare
- Saint-Lazare
- Résidence Universitaire
- Résidence Universitaire
- Veneurs
- Verdun
- Verdun
- Vermandois
- Victoire
- Victoire
- La Vènerie
- La Vènerie
- La Vènerie
- Général Weygand
- Général Weygand
- Weygand
- Ziquodrome
- Multiplexe
- LA CROIX Lycée Ch. de Gaulle
- Jean Monnet
- Mercure
- Barthou
- Barthou
- MARGNY - Collège Debussy
- MARGNY - Collège Debussy
- Margny de Gaulle
- Margny de Gaulle
- Stade Roland Dubois
- Stade Roland Dubois
- Emile Dewoitine
- Gymnase
- Gymnase
- Hauts de Margny
- Jeanne d'Arc
- Jeanne d'Arc
- Laboratoire
- Laboratoire
- La Poste
- La Poste
- Mairie de Margny
- Mairie de Margny
- Paramé
- Paramé
- Foyer Edith Piaf
- Foyer Edith Piaf
- Poincaré - C. Commercial
- Poincaré - C. Commercial
- Prairie
- Prairie
- République
- République
- Bois de Plaisance 2
- Bois de Plaisance 2
- Bois de Plaisance 4
- Bois de Plaisance 4
- Bois de Plaisance
- Bois de Plaisance
- and 16 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 5 checks — unchanged since 2026-09-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 54.8 | first check |
| 2026-08-07 | 54.8 | no change |
| 2026-08-10 | 54.8 | no change |
| 2026-09-01 | 55.7 | up 0.9 |
| 2026-09-02 | 55.7 | 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-09-01.
Same feed file as 2026-09-01; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
Everything we checked
11 findings, ordered by severity.
Show every finding
- Error47 instances
Trip distance exceeds shape distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1214 instances
1214 of 1214 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)
- Warning616 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.)
Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning288 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)
- Warning266 instances
266 of 266 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)
- Warning12 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)
- 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
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
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)
- 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 0% 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 70 days.
- 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 70 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 47 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 52 / 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 37 / 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/tic-compiegne/2026-09-02.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-02. 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.