GTFS Scorecard
← All agencies

Feed status · checked 2026-10-20

Société des traversiers du Québec (STQ)

Based on the official feed source on file

Service mode Ferry

91.0 / 100

unchanged since 2026-10-19

Cataloged in Quebec, Canada.

Review service end dateRealtime not yet published

Source feed: https://gtfs.traversiers.com/api/gtfs.zip

One export covering the provincial ferry crossings, counted as one feed record.

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 3 hours ago; last changed 3 hours ago.

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.

About this feed

Société des traversiers du Québec (STQ)’s published feed lists 10 ferry routes, 4,956 scheduled trips and 21 stops. Its service dates run from 2021-04-06 through 2099-12-31. The published file last changed on 2026-10-20.

Top things to fix

Fix 01

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.

This one is about the feed as a whole, so there is no share of it to count.

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

Fix 03

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.

Service extends far in the future (flagged by the MobilityData validator). See the linked rule for what this affects.

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.

⏱ Varies.

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.
  • No need reading for this feed was on hand when this was built, so transit need is not known.

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
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. Fix 01 · Read the fix guide for scorecard_no_fare_data

    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. Fix 02 · Read the fix guide for mixed_case_recommended_field

    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. Fix 03

    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 2099-12-31. This may be intentional or a placeholder; confirm current service with the transit operator.
Published accessibility data
Accessibility information is stated for 100% of terminals and 100% of trips. This measures published data, not whether terminals or vessels 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.

Ungraded capability read

Ferry data profile

A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labeled as whole-feed. Unknown values are not treated as no.

Ferry service
10 routes · 4,956 trips
Terminal structure
21 ferry boarding locations; no parent-station hierarchy is published.
Terminal access
Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
Published accessibility
100% of ferry boarding locations publish a value; 71.4% of all ferry boarding locations explicitly say allowed (15 of 21). Unstated values remain unknown. 100% of ferry trips publish a value; 91.7% of all ferry trips explicitly say allowed (4,546 of 4,956). Unstated values remain unknown. This reports published values, not verified physical usability.
Bicycles
100% of ferry trips publish a value; 92.2% of all ferry trips explicitly say allowed (4,570 of 4,956). Unstated values remain unknown.
Cars
100% of ferry trips publish a value; 92.2% of all ferry trips explicitly say allowed (4,570 of 4,956). Unstated values remain unknown.
Fares
Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
Realtime
Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.

Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.

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

Correctness90.2 / 100

The MobilityData validator flagged 4 kinds of issue across 244 instances (0 error, 227 warning, 17 informational).

Freshness100.0 / 100

Service is published through 2099-12-31. It may be intentional, but confirm the end date before treating the feed as maintained.

Rider experience85.0 / 100

100% of terminals state wheelchair accessibility (71% marked accessible, 29% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is not published.

Accessibility100 / 100

100% of terminals state accessibility (71% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and terminals

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

This feed has 21 terminals.

Skip to route and terminal data

The route and terminal data is ready below. Load the map only when you want the geographic view. It uses additional data.

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

Routes in Société des traversiers du Québec (STQ)'s feed
RouteTypeLine color
HHC Harrington Harbour–CheveryFerryblack (no shape in feed)
IV l'île-VerteFerryblack (no shape in feed)
IE Île d'Entrée–Cap-aux-MeulesFerryblack (no shape in feed)
IAC L'Isle-aux-Coudres–Saint-Joseph-de-la-RiveFerryblack (no shape in feed)
IAG L'Isle-aux-Grues–MontmagnyFerryblack (no shape in feed)
MBCG Matane–Baie-Comeau–GodboutFerryblack (no shape in feed)
QL Québec-LévisFerryblack (no shape in feed)
RSA Rivière Saint-AugustinFerryblack (no shape in feed)
STSIL Sorel-Tracy–Saint-Ignace-de-LoyolaFerryblack (no shape in feed)
TBSC Tadoussac–Baie-Sainte-CatherineFerryblack (no shape in feed)
List every terminal
  • Sorel-Tracy
  • Saint-Ignace-de-Loyola
  • Québec
  • Lévis
  • Matane
  • Godbout
  • Baie-Comeau
  • Tadoussac
  • Baie-Sainte-Catherine
  • L'Isle-aux-Coudres
  • St-Joseph-de-la-Rive
  • Saint-Augustin
  • Harrington Harbour
  • Chevery
  • Montmagny
  • L'Isle-aux-Grues
  • Pakuashipi
  • Ile d'Entrée
  • Cap-aux-Meules
  • départ de l'île
  • départ du village

Over time

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

2026-10-02: 91.02026-10-03: 91.02026-10-04: 91.02026-10-05: 91.02026-10-06: 91.02026-10-07: 91.02026-10-08: 91.02026-10-09: 91.02026-10-10: 91.02026-10-11: 91.02026-10-12: 91.02026-10-13: 91.02026-10-14: 91.02026-10-15: 91.02026-10-16: 91.02026-10-17: 91.02026-10-18: 91.02026-10-19: 91.02026-10-20: 91.0
Show the numbers
CheckScoreChange
2026-10-0291.0 first check
2026-10-0391.0 no change
2026-10-0491.0 no change
2026-10-0591.0 no change
2026-10-0691.0 no change
2026-10-0791.0 no change
2026-10-0891.0 no change
2026-10-0991.0 no change
2026-10-1091.0 no change
2026-10-1191.0 no change
2026-10-1291.0 no change
2026-10-1391.0 no change
2026-10-1491.0 no change
2026-10-1591.0 no change
2026-10-1691.0 no change
2026-10-1791.0 no change
2026-10-1891.0 no change
2026-10-1991.0 no change
2026-10-2091.0 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience 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.

CheckedPublished fileService dates throughGrade at the time
2026-10-200b8342dc66032099-12-31Current rubric: see the trend above
2026-10-1978bf904bc3602099-12-31Current rubric: see the trend above
2026-10-18e80c664b10782099-12-31Current rubric: see the trend above
2026-10-17635d8dc8e2562099-12-31Current rubric: see the trend above
2026-10-163b17bfa7d3b72099-12-31Current rubric: see the trend above
2026-10-15e28b6d622cd12099-12-31Current rubric: see the trend above
2026-10-145c6c202cd3272099-12-31Current rubric: see the trend above
2026-10-13741b5c96f9c02099-12-31Current rubric: see the trend above
2026-10-12ff0a2f016d552099-12-31Current rubric: see the trend above
2026-10-11fc8ca2e0bead2099-12-31Current rubric: see the trend above
2026-10-102b589da165cf2099-12-31Current rubric: see the trend above
2026-10-09a4ca35e153732099-12-31Current rubric: see the trend above

Showing the 12 most recent of 42 periods.

What changed in this feed

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

The feed file was re-published since 2026-10-19 (-1 KB).

Changed counts

  • down Some rider-facing names are in ALL CAPS or all lowercase. (231 → 227) (mixed_case_recommended_field)

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

5 findings, ordered by severity.

Show every finding
  • Warning227 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

  • 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

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

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

  • Info1 instance

    Feed valid beyond total service window (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules

Conformance mark Awarded

This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every terminal and trip.

GTFS conformance mark for Société des traversiers du Québec (STQ)

Valid Met
Passes validation with no errors.
Current Met
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
Accessible Met
States wheelchair access on 100% of terminals and 100% of trips.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every terminal and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every terminal and trip. Accessibility here measures what the feed publishes, not whether a terminal 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. 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 90 / 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 85 / 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.

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

Similar feeds in Quebec

Other scorecards in Quebec, 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.

Société des traversiers du Québec (STQ): GTFS feed quality grade A, 91.0 of 100, checked 2026-10-20. GTFS 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/stq-traversiers/2026-10-20.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-20. 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.