GTFS Scorecard
← All agencies

Feed status · checked 2026-07-18

Marinéo (Boulogne-sur-Mer)

Based on the feed this agency publishes

Service mode Bus

57.5 / 100

First scorecard for this agency

Catalogued in Hauts-de-France, France.

Covers 350 daysRealtime 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

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 +12 points in its category

Fix 02

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.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Fix 03

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

242 of 664 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 +9 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. 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. Self-check a feed before you publish.

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

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 350 days.
Published accessibility data
Accessibility information is stated for 63.6% of stops and 100% 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

Correctness25.5 / 100

The MobilityData validator flagged 15 kinds of issue across 5188 instances (5 error, 4473 warning, 710 informational).

Freshness100.0 / 100

Service data covers the next 350 days.

Rider experience68.4 / 100

64% of stops state wheelchair accessibility (52% marked accessible, 12% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility77.2 / 100

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

2 accessibility depth signals

  • 37 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (A, C, D, E, G, 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.

  • 15 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("St Patrick", "St Patrick", "Val St Martin", 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.

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.

Skip to route and stop data

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

  • 100 (teal)
  • 101 (green)
  • 123 (teal)
  • 128 (teal)
  • 143 (teal)
  • 153 (teal)
  • 154 (teal)
  • 16 (teal)
  • 173 (teal)
  • 176 (teal)
  • 18 (teal)
  • 183 (teal)
  • 188 (teal)
  • 193 (teal)
  • 194 (teal)
  • 206 (teal)
  • 207 (teal)
  • 210 (teal)
  • 34 (teal)
  • 53 (teal)
  • 54 (teal)
  • 73 (teal)
  • 78 (teal)
  • 83 (teal)
  • 94 (teal)
  • A (yellow)
  • B1 (teal)
  • B2 (teal)
  • C (teal)
  • D (purple)
  • E (teal)
  • F (red)
  • G (yellow)
  • H (orange)
  • I (gray)
  • K1 (white)
  • K2 (white)
  • L (orange)
  • M1 (pink)
  • M2 (pink)
  • N (pink)
  • NAV1 (black)
  • NAV2 (black)
  • NEMO (black)
  • O (green)
  • P (brown)
  • SAD2 (gray)
  • SAD3 (gray)
  • TH02 (purple)
Routes in Marinéo (Boulogne-sur-Mer)'s feed
RouteTypeLine color
100 100 : Baincthun <> EchinghenBusteal
101 101 : Outreau <> Boulogne-sur-MerBusgreen
123 123 : Le Portel <> Mariette- Haffreingue- St Joseph- NazarethBusteal
128 128 : Le Portel<> Giraux SannierBusteal
143 143 : Neufchâtel-Hardelot <> Mariette- Haffreingue- St Joseph- NazarethBusteal
153 153 : Outreau <> Mariette- Haffreingue- St Joseph- NazarethBusteal
154 154 : Outreau <> Collège Paul EluardBusteal
16 16 : Baincthun <> Collège Roger SalengroBusteal
173 173 : Pittefaux <> Mariette- Haffreingue- St Joseph- NazarethBusteal
176 176 : Pittefaux <> Collège Roger SalengroBusteal
18 18 : Baincthun <> Giraux SannierBusteal
183 183 <> St Etienne au Mont <> Mariette- Haffreingue- St Joseph- NazarethBusteal
188 188 <> St Etienne au Mont <> Giraux SannierBusteal
193 193 <> St Léonard <> Mariette- Haffreingue- St Joseph- NazarethBusteal
194 194 <> St Léonard <> Collège Paul EluardBusteal
206 206 : St Martin Boulogne <> Collège Roger SalengroBusteal
207 207 : St Martin Boulogne <> Collège St Joseph NavarinBusteal
210 210 : Wimereux <> Boulogne-sur-MerBusteal
34 34 : Condette <> Collège Paul EluardBusteal
53 53 : Dannes <> Mariette- Haffreingue- St Joseph- NazarethBusteal
54 54 : Dannes <> Collège Paul EluardBusteal
73 73 : Equihen-Plage <> Mariette- Haffreingue- St Joseph- NazarethBusteal
78 78 : Equihen-Plage <> Giraux SannierBusteal
83 83 : Hesdigneul <> Mariette- Haffreingue- St Joseph- NazarethBusteal
94 94 : Hesdin l'Abbé <> Collège Paul EluardBusteal
A A : Equihen-Plage <> WimereuxBusyellow
B1 B1 : Boulogne-sur-Mer <> Station Liane par MédiathèqueBusteal
B2 B2 : Boulogne-sur-Mer <> Station Liane par Dernier SouBusteal
C C : Outreau <> St Martin BoulogneBusteal
D D : Boulogne-sur-Mer <> St Martin BoulogneBuspurple
E E : St Martin Boulogne <> St Etienne au MontBusteal
F F : Outreau <> WimereuxBusred
G G : Boulogne-sur-Mer <> St Léonard <> Isques <> Hesdin l'AbbéBusyellow
H H : Boulogne-sur-Mer <> Le PortelBusorange
I I : Boulogne-sur-Mer <> St Etienne au MontBusgray
K1 K1 : Boulogne-sur-Mer -BeaurepaireBuswhite
K2 K2 Boulogne-sur-Mer -BrecquerecqueBuswhite
L L : Boulogne-sur-Mer <> La CapelleBusorange
M1 M1 : Boulogne-sur-Mer <> St Léonard <> Pont de BriquesBuspink
M2 M2 : St Léonard <> Boulogne-sur-MerBuspink
N Navette Centre ville Boulogne-sur-MerBuspink
NAV1 Navette Equihen-PlageBusblack
NAV2 Navette WimereuxBusblack
NEMO Ligne NémoBusblack
O O : Boulogne-sur-Mer <> OutreauBusgreen
P P : Boulogne-Sur-Mer <> Le PortelBusbrown
SAD2 Service à la Demande Hôpital : Boulogne-sur-Mer <> Saint-Martin-BoulogneBusgray
SAD3 Service à la Demande Henriville : Le Portel <> Boulogne-sur-MerBusgray
TH02 Navette Marché : Haute Ville Boulogne-sur-MerBuspurple

This feed has 664 stops.

List every stop
  • Fort Mahon Auberge
  • Fort Mahon Auberge
  • Berthenlaire
  • Boudoir
  • Boudoir
  • Fort Mahon Castors
  • Fort Mahon Castors
  • Allée des Hêtres
  • Allée des Hêtres
  • Macquinghen
  • Macquinghen
  • La Pâturelle
  • La Pâturelle
  • Questinghen
  • Questinghen
  • Bouverie
  • Bouverie
  • Rue d'Ambleteuse
  • Rue d'Ambleteuse
  • Ampère
  • Place d'Argentine
  • Place d'Argentine
  • Auguste Comte
  • Auguste Comte
  • Baron Bucaille
  • Beaurepaire
  • Belle Isle
  • Sainte-Beuve
  • Sainte-Beuve
  • Léon Blum
  • Léon Blum
  • Bouclet
  • Branly
  • Branly
  • Ansart Rault
  • Station Liane - Quai 14
  • Station Liane - Quai 15
  • Station Liane - Quai 16
  • Station Liane - Quai 17
  • Nausicaa
  • Rte de Calais
  • Rte de Calais
  • Calmette
  • Capécure
  • Caserne des Pompiers
  • Station Liane - Quai 10
  • Station Liane - Quai 11
  • Station Liane - Quai 1
  • Station Liane - Quai 10
  • Station Liane - Quai 11
  • Station Liane - Quai 13
  • Station Liane
  • Station Liane - Quai 2
  • Station Liane - Quai 3
  • Station Liane - Quai 3
  • Station Liane - Quai 4
  • Station Liane - Quai 4
  • Station Liane - Quai 5
  • Station Liane - Quai 6
  • Station Liane
  • Station Liane - Quai 7
  • Station Liane - Quai 7
  • Station Liane - Quai 8
  • Station Liane - Quai 8
  • Station Liane - Quai 9
  • Station Liane - Quai 9
  • Chambre de Commerce
  • Chambre de Commerce
  • Camille Enlart
  • Cimetière Nord
  • Cimetière Nord
  • Colonel Espérance
  • Coquelin
  • Place Dalton
  • Damrémont
  • Damrémont
  • Passage Daunou
  • Passage Daunou
  • Descente à la Mer
  • Descente à la Mer
  • Daudet
  • Docquois
  • Dressage
  • Dressage
  • l'Aiglon
  • Tivoli
  • Tivoli
  • Louis Duflos
  • Dugand Bucaille
  • Porte des Dunes
  • Dutertre
  • Ecole de Musique
  • Ecole d'Infirmières
  • Ecole d'Infirmières
  • Edouard Jenner
  • Entente Cordiale
  • Eperon
  • Cimetière Est
  • Résidence Eurvin
  • Résidence Eurvin
  • Ferdinand Buisson
  • Femeland
  • Flotille
  • Gambetta
  • Habitat du Littoral
  • Habitat du Littoral
  • Brequerecque
  • Henneguelle
  • Henneguelle
  • Henri Fabre
  • Hôpital - Duchenne
  • Hôpital - Centre de Rééducation
  • Henriville 2
  • Henriville 1
  • Henriville 1
  • Percier et Fontaine
  • Percier et Fontaine
  • Montesquieu
  • Montesquieu
  • Chaptal
  • Chaptal
  • Jules Verne
  • Légion d'Honneur
  • Légion d'Honneur
  • Lemaitre
  • Michelet
  • Michelet
  • Place de Lorraine
  • Louis David
  • Louis David
  • Lumière
  • Lumière
  • Gayole
  • Gayole
  • La Madeleine
  • La Madeleine
  • Maquétra
  • Marcourt
  • Maryse Bastié
  • Médiathèque
  • Médiathèque
  • Moka
  • Moka
  • Mont d'Ostrohove
  • Nausicaa
  • Nausicaa
  • Navarin ULCO
  • Navarin ULCO
  • Porte Neuve
  • Saint Nicolas
  • Normandie
  • Prince Albert
  • Prince Albert
  • Panetié
  • St Patrick
  • St Patrick
  • Pôle Capécure
  • Pôle Capécure
  • Pôle Capécure
  • François Mitterrand
  • Eglise Saint-Pierre
  • Eglise Saint-Pierre
  • Impasse Quéhen
  • Résidence
  • Résidence
  • Route de l'hôpital
  • Route de l'hôpital
  • Rosny
  • Rosny
  • Sécurité Sociale
  • Sécurité Sociale
  • Séliane
  • Séliane
  • Société Générale
  • Mont Plaisir
  • Mont Plaisir
  • Gare SNCF
  • Gare SNCF
  • Dernier Sou
  • Dernier Sou
  • Libération
  • Libération
  • Saint Michel
  • Saint Michel
  • Surcouf
  • Surcouf
  • Thiers
  • Tintelleries
  • Mariette
  • Val St Martin
  • Vieil Atre
  • Rue de Verdun
  • Victoires
  • Vieux Mont
  • Vieux Mont
  • Pont d'Aix
  • Béthune
  • Béthune
  • Av. Champagne
  • Av. Champagne
  • Ecames
  • Ecames
  • Mairie de Condette
  • Mairie de Condette
  • Pasteur
  • Pasteur
  • Le Pavé
  • Le Pavé
  • Yser
  • Yser
  • Conteville Croquet
  • Conteville Forêt
  • Conteville Croix
  • Conteville Village
  • Tunnels
  • Tunnels
  • Mairie de Dannes
  • Cimenterie
  • Petit Robinson
  • Echinghen
  • Echinghen
  • Esprée
  • Esprée
  • Menneville
  • Menneville
  • Tournes 1A
  • Tournes 1A
  • Tournes 2
  • Tournes 2
  • Tournes 1B
  • Tournes 1B
  • La Planquette
  • La Planquette
  • La Plage
  • Le Becquet
  • Le Becquet
  • Château d'eau
  • Cimetière d'Equihen Plage
  • Cimetière d'Equihen Plage
  • Les Dunes
  • Les Estombelles
  • Les Falaises
  • Camping
  • Services des Mines
  • Palézieux
  • Palézieux
  • La Plage
  • La Plage
  • La Pompe
  • La Pompe
  • and 414 more (see the full list on the map or in the GeoJSON)

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

18 findings, ordered by severity.

Show every finding
  • Error5 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.)

    Validator rule: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Warning2782 instances

    Equal shape distance same coordinates (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning1382 instances

    Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning242 instances

    242 of 664 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

  • Warning133 instances

    Some service calendars have no days of the week switched on.

    Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

    Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

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

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

    Validator rule: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules

  • Warning42 instances

    Route long name contains short name (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules

  • Warning20 instances

    Stop too far from shape using user distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

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

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

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

  • Warning1 instance

    Missing feed contact email and url (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: missing_feed_contact_email_and_url · 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

  • Info393 instances

    Big gap in service (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Info113 instances

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: unsorted_stop_times · See MobilityData GTFS Validator rules

  • Info106 instances

    Trip headsign matches intermediate stop (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Validator rule: trip_headsign_matches_intermediate_stop · See MobilityData GTFS Validator rules

  • Info97 instances

    Service window outside feed period (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Info1 instance

    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. 1 validator error to resolve. States wheelchair access on 64% of stops and 100% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 350 days.
Accessible Not yet
States wheelchair access on 64% of stops and 100% 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 350 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 5 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 26 / 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 68 / 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.

Marinéo (Boulogne-sur-Mer) 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/marineo-boulogne/2026-07-18.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-18. 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.