← All agencies

Feed status · checked 2026-10-16

Réseau urbain Colibri (Miribel)

Based on the official feed source on file

Service mode Bus

FDCBA

68.0 / 100

unchanged since 2026-10-15

Cataloged in Auvergne-Rhône-Alpes, France.

Covers 259 daysAccessibility gaps

Source feed: https://www.data.gouv.fr/api/1/datasets/r/dbd0bd0e-933a-4a21-8772-efdf41778e64

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.4, validator 8.0.1.

Checked for changes 39 minutes ago; last changed 45 days ago.

Measured 4 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: high.

All four score categories were measured this run.
Realtime was sampled in one bounded window of 3 snapshots.
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.

About this feed

Réseau urbain Colibri (Miribel)’s published feed lists 1 bus route, 64 scheduled trips and 67 stops. Its service dates run from 2026-07-04 through 2027-07-02. It publishes realtime trip updates; when we checked, it answered. The published file has not changed since our first check on 2026-09-01.

Top things to fix

Fix 01

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ Usually an export-tool fix, not hand editing.worth about +18 points in its category

Fix 02

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

67 of 67 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.

Fixing this covers all 67 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 03

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

64 of 64 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

Fixing this covers all 64 trips in the feed.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Riders and need behind these fixes

Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
The served-area need overlays cover the United States and Canada, so none of them applies to this feed.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding: Fix 01 in Top things to fix: its feed evidence and the requested change.
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

Agency: Réseau urbain Colibri (Miribel)
Finding: decreasing_or_equal_stop_time_distance
Feed evidence: Some trips have stop times whose distances along the route go backwards.
Why it matters: Apps can show buses jumping backwards or mis-order stops.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/fr-pan-79810/?finding=decreasing_or_equal_stop_time_distance#finding-handoff

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.

Fix 01
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 03 · Read the fix guide for scorecard_wheelchair_accessible_unknown
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 259 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: Live-arrival data covered 100% of scheduled trips in the sampled window.

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.

Hi,

Our GTFS feed (Réseau urbain Colibri (Miribel)) scored D (68.0 out of 100) on the GTFS Scorecard. Could you review these in our export settings:

1. Re-generate shape distances in your export; flag to your vendor if it persists.
   What: Some trips have stop times whose distances along the route go backwards.
   Finding code: decreasing_or_equal_stop_time_distance

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
   What: 67 of 67 stops don't say whether a wheelchair user can board there.
   Finding code: scorecard_wheelchair_boarding_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_boarding_unknown/

3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
   What: 64 of 64 trips don't say whether the vehicle is wheelchair accessible.
   Finding code: scorecard_wheelchair_accessible_unknown
   Guide: https://gtfsscorecard.org/fix/scorecard_wheelchair_accessible_unknown/

Full scorecard: https://gtfsscorecard.org/agency/fr-pan-79810/

Score by category

Correctness64.0 / 100

The MobilityData validator flagged 4 kinds of issue across 104 instances (41 error, 63 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 259 days.

Rider experience22.5 / 100

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.

Accessibility0 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime quality100.0 / 100

Sampled 3 times: 1 of 1 configured feed healthy; 100.0% of scheduled trips had live predictions; predictions ran a median of 275s behind schedule.

Routes and stops

Each route is drawn once, using the longest shape its trips follow; stops are the dots.

This feed has 67 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.

LC (orange)

Routes in Réseau urbain Colibri (Miribel)'s feed
Route	Type	Line color
LC Rillieux - Thil	Bus	orange

List every stop

PRE CAILLAT
ZONE COMMERCIALE DES BATERSES
PRE CAILLAT
ZONE COMMERCIALE DES BATERSES
ACTINOVE BMX
BARRONIERES
ACTINOVE BMX
BARRONIERES
LA SEREINE
POMMIERES
MAS BROCHET
LA SEREINE
LA CONCHE
LA CONCHE
POMMIERES
MAS BROCHET
GARE
GARE DE BEYNOST
PETITES COMBES
PRE MAYEUX
GARE DE BEYNOST
PETITES COMBES
MAS RILLIER CENTRE
LA MADONE
PLACE REPUBLIQUE
SAINT-MARTIN-CCMP
ANNE FRANK
TREVE
CENTRE
MAS RILLIER CENTRE
LA MADONE
PLACE REPUBLIQUE
SAINT-MARTIN-CCMP
ANNE FRANK
TREVE
CENTRE
LA POSTE
LA POSTE
LA CHANAL
ROMANS FERRARI - COMPLEXE SPORTIF
LA CHANAL
ROMANS FERRARI - COMPLEXE SPORTIF
ST MAURICE DE BEYNOST MAIRIE
PILON
ST MAURICE DE BEYNOST MAIRIE
GARE DE ST MAURICE DE BEYNOST
PILON
FORUM DES SPORTS - LILÔ
GARE DE ST MAURICE DE BEYNOST
LES COMBES
FORUM DES SPORTS - LILÔ
LES COMBES
ARMENIE
ARMENIE
CHAMPS DU PERRON
LA VERCHERE
LE VERGER
CHAMPS DU PERRON
LA VERCHERE
LE VERGER
CIMETIERE
RILLIEUX SEMAILLES
RILLIEUX SEMAILLES
OSTERODE
ZI SERMENAZ
OSTERODE
ZI SERMENAZ

Over time

Overall score across the last 15 checks — unchanged since 2026-10-15.

Show the numbers

Overall score by check, with the change from the previous check
Check	Score	Change
2026-10-02	68.0	first check
2026-10-03	68.0	no change
2026-10-04	68.0	no change
2026-10-05	68.0	no change
2026-10-06	68.0	no change
2026-10-07	68.0	no change
2026-10-08	68.0	no change
2026-10-09	68.0	no change
2026-10-10	68.0	no change
2026-10-11	68.0	no change
2026-10-12	68.0	no change
2026-10-13	68.0	no change
2026-10-14	68.0	no change
2026-10-15	68.0	no change
2026-10-16	68.0	no change

What changed since your last check

Correctness no change
Freshness no change
Rider experience no change
Realtime quality no change

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
Checked	Published file	Service dates through	Grade at the time
2026-10-02 to 2026-10-16 (15 checks)	`4e07ae22735c`	2027-07-02	Current rubric: see the trend above
2026-09-01 to 2026-10-01 (27 checks)	`4e07ae22735c`	2027-07-02	D, 68 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade

What changed in this feed

Overall grade and score held steady since 2026-10-15.

Same feed file as 2026-10-15; 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

9 findings, ordered by severity.

Show every finding

Error41 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)
Warning67 instances
67 of 67 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning64 instances
64 of 64 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
Warning51 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Warning11 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 for trip_distance_exceeds_shape_distance_below_threshold · 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 for missing_feed_contact_email_and_url · 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 for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Info67 instances
About 67 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 for scorecard_stop_names_all_caps · 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 for scorecard_no_feed_contact · 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 259 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.

Realtime reliability

The realtime feed responded on 100.0% of 200 checks in the 25 days to 2026-10-16, with 0s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment. The window ends at the newest observation, which is not always today: if the monitor stops, this window stops with it.

Live predictions vs schedule

Arrival predictions ran a median 275s late versus the schedule, and stayed within 767s nine times in ten. They were on time (about a minute early to five late) 52.1% of the time.

From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.

Clears the Google and Apple Maps four-week coverage bar. This feed has 259 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 41 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 64 / 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 100 / 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 22 / 100: GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 100 / 100: GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Part of the France portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Auvergne-Rhône-Alpes

Other scorecards in Auvergne-Rhône-Alpes, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Badge HTML

<a href="https://gtfsscorecard.org/agency/fr-pan-79810/"><img src="https://gtfsscorecard.org/agency/fr-pan-79810/badge.svg" width="320" height="58" alt="Réseau urbain Colibri (Miribel): current GTFS data quality score from GTFS Scorecard"></a>

Badge Markdown

[![Réseau urbain Colibri (Miribel): current GTFS data quality score from GTFS Scorecard](https://gtfsscorecard.org/agency/fr-pan-79810/badge.svg)](https://gtfsscorecard.org/agency/fr-pan-79810/)

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-79810/2026-10-16.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-10-16. 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.

GTFS Scorecard. (2026). Réseau urbain Colibri (Miribel) GTFS feed-quality record, dated 2026-10-16 (grade D (68.0/100), rubric v1.4, gtfs-validator 8.0.1, reader archive profile raw-v1, feed sha256 4e07ae22735c…). https://gtfsscorecard.org/data/artifacts/fr-pan-79810/2026-10-16.json

@misc{gtfsscorecard-fr-pan-79810-2026-10-16,
  title        = {Réseau urbain Colibri (Miribel) GTFS feed-quality record},
  author       = {GTFS Scorecard},
  year         = {2026},
  howpublished = {\url{https://gtfsscorecard.org/data/artifacts/fr-pan-79810/2026-10-16.json}},
  note         = {Checked 2026-10-16; rubric v1.4; gtfs-validator 8.0.1; reader archive profile raw-v1; grade D (68.0/100)}
}

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.