Home
Canada Feeds
transit
Source Data Validation Report

transit — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-11T21:15:27Z,
for the dataset file:///shared/transit_47231f83.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Quinte Access
- website: https://quintetransit.ca/
- phone number: 613-392-9640
- email: info@quintetransit.ca

Feed Info

Publisher Name:
Quinte Access: Publisher URL:
https://quintetransit.ca/: Feed Email:
info@quintetransit.ca: Feed Language:
English: Feed Start Date:
2026-08-12: Feed End Date:
2027-06-01: Service Window:
2026-08-12 to 2027-06-01 (?) 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
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 40
Routes: 12
Shapes: 21
Stops: 132
Trips: 430

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesFeed InformationRoute ColorsHeadsignsStops Wheelchair AccessibilityLocation Types

Specification Compliance report

2 notices reported (0 errors, 2 warnings, 0 infos)

Notice Code Severity Total

equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 1

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.	actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"eb5c6a0a-a7f1-4988-baf3-7b9d12410cd5"	497	11716.98	52	465	11716.98	51	0.04015101983562554

mixed_case_recommended_field WARNING 1

mixed_case_recommended_field

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

Good examples:
`Field Text`	`Dataset`
"Schwerin, Hauptbahnhof"	Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin"	NYC Ferry
"Campo Grande Norte"	Carris

Bad examples:
`Field Text`
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"routes.txt"	"route_short_name"	"CT-LN"	9