Search
  1. Home
  2. United States Feeds
  3. great-lakes-community-action-partnership
  4. Source Data Validation Report

great-lakes-community-action-partnership — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T11:13:05Z,
for the dataset file:///shared/great-lakes-community-action-partnership_c5c7edaa.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

Feed Info

Publisher Name:
Great Lakes Community Action Partnership
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2023-01-01
Feed End Date:
2025-12-01

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 2
  • Routes: 2
  • Shapes: 19
  • Stops: 22
  • Trips: 20

Specification Compliance report

260 notices reported (0 errors, 245 warnings, 15 infos)

Notice Code Severity Total
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260509" "20251201" "20260516"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 2

missing_recommended_field

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

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
missing_timepoint_value WARNING 220

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "Green1" 1
3 "Green1" 2
4 "Green1" 3
5 "Green1" 4
6 "Green1" 5
7 "Green1" 6
8 "Green1" 7
9 "Green1" 8
10 "Green1" 9
11 "Green1" 10
12 "Green2" 1
13 "Green2" 2
14 "Green2" 3
15 "Green2" 4
16 "Green2" 5
17 "Green2" 6
18 "Green2" 7
19 "Green2" 8
20 "Green2" 9
21 "Green2" 10
22 "Green3" 1
23 "Green3" 2
24 "Green3" 3
25 "Green3" 4
26 "Green3" 5
27 "Green3" 6
28 "Green3" 7
29 "Green3" 8
30 "Green3" 9
31 "Green3" 10
32 "Green4" 1
33 "Green4" 2
34 "Green4" 3
35 "Green4" 4
36 "Green4" 5
37 "Green4" 6
38 "Green4" 7
39 "Green4" 8
40 "Green4" 9
41 "Green4" 10
42 "Green5" 1
43 "Green5" 2
44 "Green5" 3
45 "Green5" 4
46 "Green5" 5
47 "Green5" 6
48 "Green5" 7
49 "Green5" 8
50 "Green5" 9
51 "Green5" 10
route_long_name_contains_short_name WARNING 2

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`.
"Green" 2 "Green" "Green Line"
"Orange" 3 "Orange" "Orange Line"
unused_shape WARNING 19

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"Orange Seniors to DJFS" 2
"DJFS to Wal-Mart" 5
"Wal-Mart to North Park Ave-State St" 19
"North Park Ave-State St to Birchard Library" 25
"Birchard Library to Janel Terrace" 29
"Janel Terrace to GLCAP" 34
"GLCAP to Commons at Little Bark" 37
"Commons at Little Bark to Advance Auto Parts" 48
"Advance Auto Parts to Liberty Center" 54
"Liberty Center to Big Lots" 56
"Big Lots to Senior Center" 59
"North Park Ave-State St to Wal-Mart" 67
"Wal-Mart to Fremont Ross High School" 73
"Fremont Ross High School to Ross Apartments" 79
"Ross Apartments to Potter Village" 81
"Potter Village to Firelands Counseling" 87
"Firelands Counseling to Community Health Services" 94
"Community Health Services to Promedica Memorial Hospital" 98
"Promedica Memorial Hopsital to North Park Ave-State St" 102
transfer_distance_above_2_km INFO 15

transfer_distance_above_2_km

The transfer distance from stop to stop in transfers.txt is larger than 2 km.

You can see more about this notice here.

csvRowNumber (?) The row number from `transfers.txt` for the faulty entry. fromStopId (?) The ID of the stop in `from_stop_id`. toStopId (?) The ID of the stop in `to_stop_id`. distanceKm (?) The distance between the two stops in km.
4 "G1" "O3" 2.9356794770493835
9 "G6" "O3" 2.3903404649073288
10 "G7" "O3" 4.897867413522147
11 "G8" "O3" 4.311119437707115
12 "G9" "O3" 4.174479614600285
13 "O1" "G2" 3.356326307690058
14 "O2" "G2" 3.885976939268687
16 "O4" "G2" 2.9356794770493835
17 "O5" "G2" 3.2378499326207595
18 "O6" "G2" 3.568796469646326
19 "O7" "G2" 3.346546784279701
20 "O8" "G2" 4.7310705442182055
21 "O9" "G2" 3.662486175361167
22 "O10" "G2" 4.312297969034938
23 "O11" "G2" 4.737208411959765