Feed status · checked 2026-07-19
Ametis (Amiens Métropole)
Based on the feed this agency publishes
Service mode Bus
down 0.5 since 2026-07-18
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
737 of 737 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
2301 of 2301 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
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.
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 42 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 4 kinds of issue across 79952 instances (0 error, 79951 warning, 1 informational).
Service data covers the next 42 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.
1 accessibility depth signal
2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Collège St Martin", "Collège St Martin").
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
This feed has no route shapes, so the map shows its stops only.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
| Route | Type | Line color |
|---|---|---|
| 10 LIGNE 10 | Bus | green (no shape in feed) |
| 11 LIGNE 11 | Bus | green (no shape in feed) |
| 12 LIGNE 12 | Bus | green (no shape in feed) |
| 13 LIGNE 13 | Bus | green (no shape in feed) |
| 14 LIGNE 14 | Bus | green (no shape in feed) |
| 15 LIGNE 15 | Bus | green (no shape in feed) |
| 16 LIGNE 16 | Bus | green (no shape in feed) |
| 5A LIGNE 5A | Bus | green (no shape in feed) |
| 5B LIGNE 5B | Bus | green (no shape in feed) |
| 6 LIGNE 6 | Bus | green (no shape in feed) |
| 7 LIGNE 7 | Bus | green (no shape in feed) |
| 8 LIGNE 8 | Bus | green (no shape in feed) |
| 9 LIGNE 9 | Bus | green (no shape in feed) |
| CDV Coeur de ville | Bus | green (no shape in feed) |
| L Lianes | Bus | green (no shape in feed) |
| N1 Nemo 1 Bleu | Bus | green (no shape in feed) |
| N2 Nemo 2 Rouge | Bus | green (no shape in feed) |
| N3 Nemo 3 Verte | Bus | green (no shape in feed) |
| N4 Nemo 4 Jaune | Bus | green (no shape in feed) |
| NAM1 Navette marche Ambonne | Bus | green (no shape in feed) |
| NAM2 Navette marche Duclos | Bus | green (no shape in feed) |
| NAVC Navette cimetiere | Bus | green (no shape in feed) |
This feed has 737 stops.
List every stop
- Abbé de l'Épée
- Camping
- Collège Rosa Parks
- Cité Providence
- Cité Providence
- Chardin
- Chardin
- Zoo d'Amiens
- Zoo d'Amiens
- Citadelle François 1er
- Citadelle Montrescu quai B
- Camping
- Citadelle Montrescu quai A
- Cirque Jules Verne quai D
- Cirque Jules Verne quai B
- Clémenceau
- Clémenceau
- Collège St Martin
- Collège St Martin
- Capitaine Nemo
- Capitaine Nemo
- Campus quai C
- Colvert
- Colvert
- Les coursives
- Les Coursives
- Croix de Fer
- Croix de Fer
- Centre Saint Victor
- Centre Saint Victor
- Delpech quai A
- Delpech quai B
- Eglise Saint Firmin
- Eglise Saint Firmin
- Eloi Morel
- Eloi Morel
- Etouvie quai A
- Faubourg de Hem
- Faubourg de Hem
- La Fontaine
- Campus quai B
- La Fontaine
- La Fourche
- La Fourche
- Gare du Nord quai A
- Gare du Nord quai B
- Gare du Nord quai D
- Georges Beauvais
- Georges Beauvais
- Campus quai A
- Grèce
- Grèce
- CHU A. Picardie quai A
- Hôtel de Ville
- Dusevel
- I.M.E
- I.M.E
- Jacobins
- Jean Jaurès
- Jean Jaurès
- Charassain
- Languedoc
- Languedoc
- Nautilus
- Nautilus
- Libération quai A
- Libération quai B
- Lycée de Luzarches
- Lycée de Luzarches
- Maison de la Culture
- Espagne
- Charassain
- Espagne
- Mairie de Longueau
- Mairie de Longueau
- Otages
- Otages
- La Paix
- La Paix
- Place du Don
- Place du Don
- Pont de l'Avre
- Pont de l'Avre
- Hortillonnages
- Hortillonnages
- Parc Saint Pierre
- Parc Saint Pierre
- Pinceau
- Pinceau
- Palais de Justice
- Place du Marché
- Pôle d'Echanges Nord quai B
- Carmel
- Pôle d'Echanges Nord quai A
- Poidevin
- Poidevin
- Pôle des cliniques
- Pôle des cliniques
- Vogel quai B
- Quatre Chênes
- Quatre Chênes
- Abbé Hénocque
- Carmel
- Quatre Lemaire
- Emile Zola
- René Goblet
- Romain Rolland
- Romain Rolland
- La Rose Rouge
- La Rose Rouge
- Résidence du Thil
- Résidence du Thil
- Espace Santé
- Sobo
- Sobo
- Martinique
- Martinique
- Stendhal
- Stendhal
- Sully
- Sully
- UPJV Saint Leu
- Cirque Jules Verne quai A
- Cirque Jules Verne quai C
- Colbert
- Colbert
- Waide
- Hélène Lockert
- Hélène Lockert
- Gare du Nord quai C
- Laënnec quai C
- Cateuse
- Cateuse
- Citadelle Montrescu quai C
- Clos de l'Avre
- Clos de l'Avre
- Cité du Château
- Abbé Hénocque
- Ambonne
- Cozette
- Le Tintoret
- Le Tintoret
- Longueville
- Maître Zacharius
- Maître Zacharius
- Taisnil
- Centre Commercial Nord quai
- 14 juillet
- De la Basse Selle
- Jean Catelas
- Promenade
- Promenade
- Centre Commercial Sud
- Eglise de Camon
- Gare du Nord quai C
- Robert Le Coq
- Robert Le Coq
- Simone Veil quai A
- Iream
- Iream
- Chambre d'Agriculture
- Chambre d'Agriculture
- Champ à Oisons
- Simone Veil quai B
- Simone Veil quai F
- Simone Veil quai E
- Laënnec quai C
- Château
- Château
- Alsace Lorraine
- La Chaussée
- Laënnec quai A
- Chevalier Labarre
- Chaussée de Paris
- IUT
- Laënnec quai B
- Chemin de la Vallée
- Chemin de la Vallée
- Alsace Lorraine
- Rollin
- Rollin
- Libération quai C
- Libération quai D
- Libération quai E
- Matifas
- Matifas
- Alain Colas
- Pôle Licorne
- Krüger
- Cimetière Saint Jean
- Cimetière Saint Jean
- Collège Jean Marc Laurent
- Collège Jean Marc Laurent
- Collège Joliot Curie
- Collège Joliot Curie
- Alain Colas
- Collège Jules Verne
- Collège Jules Verne
- Pôle d'Echanges Nord quai C
- Pôle d'Echanges Nord quai D
- Clos Saint Jean
- Clos Saint Jean
- Cimetière La Madeleine
- Cimetière La Madeleine
- Amiral Courbet
- Coisy
- Coisy
- 14 juillet
- Amiral Courbet
- Place de Cagny
- Conty
- CHU A. Picardie quai C
- Conty
- Corbie
- Berlioz
- Berlioz
- Calmette
- Calmette
- Saint Jacques
- Corbie
- Saint Jacques
- Chapitre
- Chapitre
- Maison de la Culture
- Maison de la Culture
- Cimetière de Rivery
- Eglise Saint Martin
- Moutiers
- Cimetière de Rivery
- Moutiers
- Croix de Pierre
- Croix de Pierre
- Afpa
- Vogel quai C
- Collège de la Salle
- Collège de la Salle
- Cité des Castors
- Cité des Castors
- Cité du Château
- Vogel quai E
- Charles Tellier
- Afpa
- Charles Tellier
- Cité Petit
- Cité Petit
- Centre de Tri
- Centre de Tri
- Vogel quai D
- Croix Rompue
- Anatole France
- and 487 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 2 checks — down 0.5 since 2026-07-18.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-18 | 60.7 | first check |
| 2026-07-19 | 60.2 | down 0.5 |
What changed since your last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
What changed in this feed
Overall score fell 0.5 points since 2026-07-18.
Same feed file as 2026-07-18; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning78487 instances
Missing timepoint value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2301 instances
2301 of 2301 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.)
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1463 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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning737 instances
737 of 737 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)
- 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
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)
- Info1 instance
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.)
Validator rule: 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).
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 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 42 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 42 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 80 / 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 55 / 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/ametis-amiens/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.