Call-prep brief · checked 2026-10-15

Réseau de transport de Longueuil

Grade D · 62.9 / 100

Down 0.4 points since 2026-10-14 (D to D).

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.

What changed since the last check

Correctness no change
Freshness down 1.7
Rider experience no change

Top three things to fix

Re-export with a validity window that reaches at least 60 days out.
Service data runs out in 17 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
This one is about the feed as a whole, so there is no share of it to count.
Effort: One export setting.
Review the flagged fields and fill in the ones your riders would use.
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.
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.
Effort: A field at a time; not urgent.
Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Unexpected enum value (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.
Effort: 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.

Feed evidence: Service data runs out in 17 day(s).
Next action: Re-export with a validity window that reaches at least 60 days out.
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 de transport de Longueuil
Finding: scorecard_feed_expiring_soon
Feed evidence: Service data runs out in 17 day(s).
Why it matters: When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Requested change: Re-export with a validity window that reaches at least 60 days out.
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/rtl-longueuil/?finding=scorecard_feed_expiring_soon#finding-handoff

Ready to send to the agency

Hi Réseau de transport de Longueuil team, Service data runs out in 17 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice. The fix is usually one export setting: Re-export with a validity window that reaches at least 60 days out. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/rtl-longueuil/

Copy this note from the full scorecard.

Key facts

Feed URL: https://www.rtl-longueuil.qc.ca/transit/latestfeed/RTL.zip
Last checked: 2026-10-15
Service window: 17 days of service data remain. Last service date 2026-11-01.
Feed version: 202610091441
Location: Quebec, Canada

Part of the Canada portfolio: see where this agency sits among the other feeds in that group before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.