GTFS Scorecard
← All agencies

Feed status · checked 2026-07-19

Hilagobus (Saint-Gilles-Croix-de-Vie)

Based on the feed this agency publishes

Service mode Bus

69.4 / 100

First scorecard for this agency

Catalogued in Pays-de-la-Loire, France.

Covers 346 daysAccessibility 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.2, validator 8.0.1.

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

Fix 01

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

116 of 116 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 02

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.

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

Fix 03

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.

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

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

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

Correctness91.2 / 100

The MobilityData validator flagged 3 kinds of issue across 13 instances (0 error, 6 warning, 7 informational).

Freshness85.0 / 100

Service data covers the next 346 days.

Rider experience26.2 / 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

  • 6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Ligne A, Ligne B, TALP C, TALP S, Ligne A, 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.

  • 1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cyprès/Petit Pavillon").

    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

This feed has no route shapes, so the map shows its stops only.

Skip to route and stop data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.

Routes in Hilagobus (Saint-Gilles-Croix-de-Vie)'s feed
RouteTypeLine color
Ligne C Hilagobus Ligne CBusgreen (no shape in feed)
Ligne A Gillobus Ligne ABusteal (no shape in feed)
Ligne B Gillobus Ligne BBusred (no shape in feed)
TALP N Tous à la plage NordBusbrown (no shape in feed)
TALP C Tous à la plage CentreBusteal (no shape in feed)
TALP S Tous à la plage SudBusred (no shape in feed)
Ligne A Gillobus Ligne A 26Busteal (no shape in feed)
Ligne B Gillobus Ligne B 26Busred (no shape in feed)

This feed has 116 stops.

List every stop
  • Alain Gerbault
  • Calvaire
  • Vergers d'Eole
  • Vergers d'Eole
  • Villa Notre Dame
  • Gare SNCF
  • Grollier
  • Grollier
  • Le Roc
  • Le Roc
  • L'Ormeau
  • L'Ormeau
  • Calvaire
  • 34 rue Georges Clemenceau
  • Rd-pt des Mimosas
  • Rd-pt des Mimosas
  • 63 rue de Bel Air
  • 63 rue de Bel Air
  • 2 Rue des Quarante Sillons
  • Les Sables
  • Calvaire
  • Centre
  • Centre
  • Route des Sables
  • Route des Sables
  • Cour Rouge
  • Docteur Potel
  • Docteur Potel
  • Alain Gerbault
  • Ecole publique
  • Embarcadère Ile d'Yeu
  • Embarcadère Ile d'Yeu
  • Espace Commercial
  • Espace Commercial
  • Europe
  • Europe
  • Rue de l'Océan
  • Gare SNCF
  • Gare SNCF
  • Ambroise Paré
  • Gendarmerie
  • Gendarmerie
  • Hôpital
  • Hôpital
  • Jean Moulin
  • Jean Moulin
  • Fradinière
  • Pelle à Porteau
  • Pelle à Porteau
  • Poste
  • Ambroise Paré
  • Rousselotière
  • Rousselotière
  • Bahamas Beach
  • Disque
  • Disque
  • Port de pêche
  • Grande Plage
  • Cyprès/Petit Pavillon
  • Les Sables
  • Salines
  • Bellevue
  • Liberté
  • Liberté
  • Ecole l'Oiseau Bleu
  • Louis Cristau
  • Louis Cristau
  • Mairie
  • Mairie
  • Mairie
  • Mairie
  • Moulins
  • Bellevue
  • Moulins
  • Multiplexe aquatique
  • Océanides
  • Pasteur
  • Petite Gare
  • Petite Gare
  • Pinède
  • Pinède
  • Pissot
  • Place Brechoteau
  • Bilbao
  • Place Clémenceau
  • Place de la Ménarderie
  • Place de la Ménarderie
  • Place des anciens combattants
  • Plage des Dunes 1
  • Pompidou 1
  • Pompidou 1
  • Pompidou 2
  • Pompidou 2
  • Port Fidèle
  • Bilbao
  • Port Fidèle
  • Quai Gorin
  • Quai Gorin
  • Quai Rivière
  • Quarteron
  • Quarteron
  • Rond Point Océan
  • Rond Point Océan
  • Rochebonne Grande plage
  • Rond Point de l'Europe
  • 15 rue de Lattre de Tassigny
  • Rue Piétonne
  • Rue Piétonne
  • Rue Piétonne
  • Rue Piétonne
  • Sablais
  • Sion l'Océan
  • Tassigny
  • Tassigny
  • Terres Franches
  • Terres Franches

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
  • Warning116 instances

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

  • 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.)

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning48 instances

    48 of 64 trips have no headsign.

    Riders at the stop can't tell which direction a bus is going.

    Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

    Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

  • Warning4 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning2 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.)

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

  • 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

  • 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

  • Info7 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

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

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 4 of 116 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 346 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 91 / 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 26 / 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.

Hilagobus (Saint-Gilles-Croix-de-Vie) GTFS data quality grade: D

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/hilagobus-saint-gilles/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.