Home
United States Feeds
gtfs-rpt-cadavl-com-rochester-public-transit-1
Source Data Validation Report

gtfs-rpt-cadavl-com-rochester-public-transit-1 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-29T19:21:05Z,
for the dataset file:///shared/gtfs-rpt-cadavl-com-rochester-public-transit-1_49a24bcf.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Rochester
- website: https://www.rochestermn.gov/departments/rochester-public-transit
- phone number:
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2026-05-28 to 2026-05-30 (?) 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
transfers.txt
trips.txt

Counts

Agencies: 1
Blocks: 41
Routes: 28
Shapes: 44
Stops: 1499
Trips: 638

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

ShapesRoute ColorsLocation Types

Specification Compliance report

1444 notices reported (0 errors, 1443 warnings, 1 infos)

Notice Code Severity Total

equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 6

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.
"411_4099_4363"	3493	22043.0	901	3492	22043.0	900	0.08895608115225495
"413_4342_4363"	4792	10027.0	476	4791	10027.0	475	0.08895608115225495
"413_4342_4363_1"	14470	10027.0	476	14469	10027.0	475	0.08895608115225495
"419_4365_4363"	2591	30461.0	1197	2590	30461.0	1196	0.08895608115225495
"307_3171_4363"	558	10496.0	556	557	10496.0	555	0.08895608115225495
"410_4384_4363"	28224	15913.0	855	28223	15913.0	854	0.08895608115225495

missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"

mixed_case_recommended_field WARNING 1405

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.

Only the first 50 of 1405 affected records are displayed below.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"stops.txt"	"stop_name"	"ROSE DR SE AND HBR DR SE"	2
"stops.txt"	"stop_name"	"11 AVE SE AND 16 ST SE"	3
"stops.txt"	"stop_name"	"10 AVE SE AND 17 ST SE"	4
"stops.txt"	"stop_name"	"19 ST SE AND 9 1/2 AVE SE"	5
"stops.txt"	"stop_name"	"9 1/2 AVE SE AND 20 ST SE"	6
"stops.txt"	"stop_name"	"PINEWD RD SE AND 18 AVE SE"	7
"stops.txt"	"stop_name"	"BDWY AVE N AND 10 ST NE"	8
"stops.txt"	"stop_name"	"BDWY N AND W SILVER LK DR NE"	9
"stops.txt"	"stop_name"	"BDWY AVE N AND 9 ST NW"	10
"stops.txt"	"stop_name"	"E RIV RD NE AND ALLIANCE PL NE"	11
"stops.txt"	"stop_name"	"E RIV RD NE AND SVC CT NE"	12
"stops.txt"	"stop_name"	"NO HLS DR NE AT NO HLS APTS"	13
"stops.txt"	"stop_name"	"NO HLS DR NE AND NO HLS CT NE"	14
"stops.txt"	"stop_name"	"FAIRGROUNDS PK AND RIDE"	15
"stops.txt"	"stop_name"	"W FR RD AT WALMART NORTH"	16
"stops.txt"	"stop_name"	"CENTRAL PARK STAND 2"	17
"stops.txt"	"stop_name"	"16 AVE SW AND 1 ST SW"	18
"stops.txt"	"stop_name"	"16 AVE SW AND 1 ST SW"	19
"stops.txt"	"stop_name"	"BDWY AVE N AND NO HLS DR NE"	20
"stops.txt"	"stop_name"	"BDWY AVE N AND ROCKY CRK DR NE"	21
"stops.txt"	"stop_name"	"NORTH BDWY PK AND RIDE"	22
"stops.txt"	"stop_name"	"BDWY AVE N AND 13 ST NW"	23
"stops.txt"	"stop_name"	"9 ST NE AND 17 AVE NE EB"	24
"stops.txt"	"stop_name"	"21 AVE NW AND 17 1/2 ST NW"	25
"stops.txt"	"stop_name"	"15 1/2 AVE NW AND 14 ST NW"	26
"stops.txt"	"stop_name"	"21 AVE NW AND 17 1/2 ST NW"	27
"stops.txt"	"stop_name"	"11 AVE NE AND 5TH ST NE"	30
"stops.txt"	"stop_name"	"W FR RD AT WALMART NORTH"	33
"stops.txt"	"stop_name"	"NO HTS DR NE AND 7 AVE NE"	34
"stops.txt"	"stop_name"	"5 ST NE AND 11 AVE NE"	35
"stops.txt"	"stop_name"	"CTR ST E AND 9 AVE NE"	36
"stops.txt"	"stop_name"	"CTR ST E AND W OF 7 AVE NE"	37
"stops.txt"	"stop_name"	"CIV CTR DR AT ROCH CIV THTRE"	38
"stops.txt"	"stop_name"	"CTR ST E AND MAYO PK DR SE"	39
"stops.txt"	"stop_name"	"CTR ST E AND 7 AVE SE"	40
"stops.txt"	"stop_name"	"CTR ST E AND 9 AVE SE"	41
"stops.txt"	"stop_name"	"CTR ST E AND 11 AVE SE"	42
"stops.txt"	"stop_name"	"11 AVE NE AND 5 ST NE"	43
"stops.txt"	"stop_name"	"HBR DR AND S OF ROSE HTS DR SE"	44
"stops.txt"	"stop_name"	"15 AVE SE AND 10 ST SE"	45
"stops.txt"	"stop_name"	"BDWY AVE S AND S OF 16 ST SE"	46
"stops.txt"	"stop_name"	"3 AVE SW AND NORTH OF 14 ST SW"	47
"stops.txt"	"stop_name"	"ROCKY CRK DR AND WELLNER DR NE"	48
"stops.txt"	"stop_name"	"ROCKY CRK DR AND NO VLY DR NE"	49
"stops.txt"	"stop_name"	"ROCKY CRK DR AND NO VLY DR NE"	50
"stops.txt"	"stop_name"	"NO VLY DR AND NO SLOPES LN NE"	51
"stops.txt"	"stop_name"	"EASTWOOD RD AND FELTY AVE SE"	52
"stops.txt"	"stop_name"	"FELTY AVE AND TWN C PKWY SE"	53
"stops.txt"	"stop_name"	"4 ST SE AND 11 AVE SE"	54
"stops.txt"	"stop_name"	"4 ST SE AND 9 AVE SE"	55

route_long_name_contains_short_name WARNING 28

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"206"	2	"206"	"206"
"22"	3	"22"	"22"
"306"	4	"306"	"306"
"26"	5	"26"	"26"
"411"	6	"411"	"411"
"203"	7	"203"	"203"
"101"	8	"101"	"101"
"23"	9	"23"	"23"
"307"	10	"307"	"307"
"412"	11	"412"	"412"
"205"	12	"205"	"205"
"409"	13	"409"	"409"
"419"	14	"419"	"419"
"505"	15	"505"	"505"
"418"	16	"418"	"418"
"116"	17	"116"	"116"
"24"	18	"24"	"24"
"204"	19	"204"	"204"
"314"	20	"314"	"314"
"21"	21	"21"	"21"
"102"	22	"102"	"102"
"25"	23	"25"	"25"
"413"	24	"413"	"413"
"408"	25	"408"	"408"
"550"	26	"550"	"550"
"150"	27	"150"	"150"
"120"	28	"120"	"120"
"410"	29	"410"	"410"

stop_without_stop_time WARNING 2

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
503	"0:4357"	"PWTOC DEPOT"
771	"0:1165"	"31 St NE @ Sq31"

trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20260529"	"20260528"	"20260529"

unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the unknown column.	index (?) The index of the faulty column.
"stops.txt"	"vehicle_type"	10