mrc-du-haut-saint-laurent-1 — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T19:30:13Z,
for the dataset file:///shared/mrc-du-haut-saint-laurent-1_2d5ba3d2.zip. No country code was provided.
Use this report alongside our documentation.
Summary
Feed Info
- Publisher Name:
- N/A
- Publisher URL:
- N/A
- Feed Email:
- N/A
- Feed Language:
- N/A
- Service Window:
- 2023-08-11 to 2100-12-31 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt
Files included
- agency.txt
- calendar.txt
- calendar_dates.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- trips.txt
Counts
- Agencies: 1
- Blocks: 3
- Routes: 3
- Shapes: 6
- Stops: 62
- Trips: 30
Specification Compliance report
9 notices reported (0 errors, 9 warnings, 0 infos)
| Notice Code | Severity | Total | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| leading_or_trailing_whitespaces | WARNING | 2 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
leading_or_trailing_whitespacesThe value in CSV file has leading or trailing whitespaces. This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser. The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces. You can see more about this notice here.
missing_recommended_field | WARNING | 3 | missing_recommended_fieldA recommended field is missing. The given field has no value in some input row, even though values are recommended. You can see more about this notice here.
missing_recommended_file | WARNING | 1 | missing_recommended_fileA recommended file is missing. You can see more about this notice here.
mixed_case_recommended_field | WARNING | 2 | mixed_case_recommended_fieldThis field has customer-facing text and should use Mixed Case (should contain upper and lower case letters). This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.
You can see more about this notice here.
stop_too_far_from_shape | WARNING | 1 | stop_too_far_from_shapeStop too far from trip shape. Per GTFS Best Practices, route alignments (in You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||