GTFS Scorecard
← All agencies

Feed status · checked 2026-09-01

Navettes du Giffre

Based on the official feed source on file

Service mode Bus

45.8 / 100

First scorecard for this agency

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

Review service end dateAccessibility gapsRealtime not yet published

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.

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

Fix 01

Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Duplicate key (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.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

75 of 75 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

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

940 of 940 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
Duplicate key (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'duplicate_key' 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
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.

  1. Review the rule documentation for 'duplicate_key' 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. Self-check a feed before you publish.

  2. 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.

  3. 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.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed states that service is published through 5202-04-30. This may be intentional or a placeholder; confirm current service with the transit operator.
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

Correctness40.0 / 100

The MobilityData validator flagged 10 kinds of issue across 12748 instances (13 error, 10865 warning, 1870 informational).

Freshness85.0 / 100

Service is published through 5202-04-30. It may be intentional, but confirm the end date before treating the feed as maintained.

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.

2 accessibility depth signals

  • 7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (L2 BLEUE, L3TURQUOISE, L6ROSE, L7ORANGE, L8ROUGE, 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 ("MORILLON - MAIRIE / ECOLE", "SIXT FER A CHEVAL - MAISON NEUVE / LES VAGNYS", "SIXT FER A CHEVAL - MAISON NEUVE / LES VAGNYS").

    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.

Realtime qualityNot yet measured

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 75 stops.

Skip to route and stop data

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.

  • L1JAUNE (yellow)
  • L2 BLEUE (teal)
  • L3TURQUOISE (teal)
  • L5BLANCHE (white)
  • L6ROSE (pink)
  • L7ORANGE (orange)
  • L8ROUGE (red)
  • L9VERTE (green)
  • L9.1VERTE (green)
  • L11MARRON (brown)
Routes in Navettes du Giffre's feed
RouteTypeLine color
L1JAUNEBusyellow
L2 BLEUE LIGNE 2 BLEUEBusteal
L3TURQUOISEBusteal
L5BLANCHE LIGNE 5 BLANCHEBuswhite
L6ROSEBuspink
L7ORANGEBusorange
L8ROUGEBusred
L9VERTEBusgreen
L9.1VERTEBusgreen
L11MARRONBusbrown
List every stop
  • LA RIVIERE ENVERSE - LA GROTTE
  • LA RIVIERE ENVERSE - LA GROTTE
  • VERCHAIX - CHEF LIEU
  • FLAINE - FORUM
  • MORILLON - MAIRIE / ECOLE
  • CHATILLON SUR CLUSES - MAIRIE
  • CHATILLON SUR CLUSES - MAIRIE
  • MORILLON - CCAS
  • MORILLON - CCAS
  • MORILLON - TÉLÉCABINE
  • MORILLON - TÉLÉCABINE
  • LA RIVIERE ENVERSE - CHEF LIEU
  • LA RIVIERE ENVERSE - CHEF LIEU
  • LA RIVIERE ENVERSE - LE PLAN
  • LA RIVIERE ENVERSE - LE PLAN
  • LA RIVIERE ENVERSE - PETIT MARVEL
  • LA RIVIERE ENVERSE - PETIT MARVEL
  • SAMOENS - LE BÉROUZE
  • SAMOENS - LES VALLONS D'EN BAS
  • SAMOENS - LES VALLONS D'EN HAUT
  • SAMOENS - PONT DE CLÉVIEUX
  • VERCHAIX - GARE (OT)
  • SAMOENS - GRAND MASSIF EXPRESS
  • LES CARROZ - OFFICE DU TOURISME
  • SIXT FER A CHEVAL - LE PERRET
  • SIXT FER A CHEVAL - LE PERRET
  • SAMOENS - FONTAINE DES VALLONS
  • MORILLON - BOIS CHAMPELLE
  • MORILLON - BOIS CHAMPELLE
  • MORILLON - OURSON BAS
  • MORILLON - OURSON BAS
  • MORILLON - VERNEY D'EN HAUT
  • SAMOENS - LAC AUX DAMES
  • SAMOENS - SOUS LE CRET
  • SAMOENS - SOUS LE CRET
  • SAMOENS - PLAMPRAZ
  • SAMOENS - PLAMPRAZ
  • SAMOENS - JOUX PLANE
  • MORILLON - LA PERRIÈRE
  • SAMOENS - LE QUART
  • SAMOENS - CLOS PARCHET
  • SAMOENS - CLOS PARCHET
  • SIXT FER A CHEVAL - SALVAGNY
  • SIXT FER A CHEVAL - SALVAGNY
  • SIXT FER A CHEVAL - MAISON NEUVE / LES VAGNYS
  • SIXT FER A CHEVAL - MAISON NEUVE / LES VAGNYS
  • SIXT FER A CHEVAL - MAISON DE LA MONTAGNE
  • SIXT FER A CHEVAL - MAISON DE LA MONTAGNE
  • SAMOENS - LE PETIT SAIX
  • SAMOENS - LE PETIT SAIX
  • SAMOENS - CINEMA
  • SAMOENS - AVENUE DES LOISIRS
  • SAMOENS - PLACE DES 7 MONTS
  • SAMOENS - SKIBUS LES BEULES
  • SIXT FER A CHEVAL - SALVAGNY CAISSE
  • SIXT FER A CHEVAL - SALVAGNY CAISSE
  • SAMOENS - VERCLAND
  • SAMOENS - CLOS MOCCANS BAS
  • SAMOENS - SKIBUS OFFICE DU TOURISME
  • SAMOENS - CLOS MOCCANS HAUT
  • SAMOENS - ANCIENNE FRUITIERE
  • SAMOENS - LES PERTUETS
  • VERCHAIX - HAMEAU DU GIFFRE
  • MORILLON - LE GRAND CHAMP
  • MORILLON - OURSON HAUT
  • SAMOENS - ETELLEY
  • SAMOENS - ETELLEY
  • LA RIVIERE ENVERSE - GRAND MARVEL
  • LA RIVIERE ENVERSE - GRAND MARVEL
  • SIXT FER A CHEVAL - SALVAGNY CAP FRANCE
  • VERCHAIX - SKIBUS OFFICE DU TOURISME
  • SIXT FER A CHEVAL - PISTE DES CASCADES
  • SAMOENS - LES FONTAINES
  • SAMOENS - FONTANYS
  • SAMOENS - LES MOULINS

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

16 findings, ordered by severity.

Show every finding
  • Error13 instances

    Duplicate key (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: duplicate_key · See MobilityData GTFS Validator rules

  • Warning9800 instances

    Some rows in stop_times.txt leave the timepoint column blank.

    That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.

    Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)

    Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1035 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

  • Warning940 instances

    940 of 940 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

  • Warning75 instances

    75 of 75 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

  • Warning13 instances

    Some files leave out fields that GTFS asks for but does not require.

    Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

    Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning8 instances

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • Warning4 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • 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 · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt is missing its start/end dates

    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

  • 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

  • Info936 instances

    Service extends far in the future (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: service_extends_far_in_the_future · See MobilityData GTFS Validator rules

  • Info934 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

  • Info75 instances

    About 75 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

  • 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

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
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
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 clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. The feed also carries 13 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 22 / 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.

Navettes du Giffre GTFS data quality grade: F

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-81549/2026-09-01.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-01. 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.