Search
  1. Home
  2. United States Feeds
  3. north-carolina-state-university-1
  4. Source Data Validation Report

north-carolina-state-university-1 — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-27T19:38:50Z,
for the dataset file:///shared/north-carolina-state-university-1_8d79c498.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Passio Technologies
Publisher URL:
https://passiotech.com
Feed Email:
support@passiotech.com
Feed Language:
English
Feed Start Date:
2026-03-25
Feed End Date:
2026-04-25

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 41
  • Routes: 15
  • Shapes: 10
  • Stops: 117
  • Trips: 1094

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 24

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

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 the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"47773" 1970 116.32 20 1969 116.32 19
"70572" 1261 1647.36 127 1260 1647.36 126
"70572" 1284 1947.49 150 1283 1947.49 149
"70572" 1285 1947.49 151 1284 1947.49 150
"70572" 1286 1947.49 152 1285 1947.49 151
"70572" 1287 1947.49 153 1286 1947.49 152
"70572" 1288 1947.49 154 1287 1947.49 153
"70572" 1289 1947.49 155 1288 1947.49 154
"70572" 1290 1947.49 156 1289 1947.49 155
"70572" 1291 1947.49 157 1290 1947.49 156
"70572" 1292 1947.49 158 1291 1947.49 157
"70572" 1293 1947.49 159 1292 1947.49 158
"70572" 1294 1947.49 160 1293 1947.49 159
"70572" 1295 1947.49 161 1294 1947.49 160
"70572" 1296 1947.49 162 1295 1947.49 161
"70572" 1297 1947.49 163 1296 1947.49 162
"70572" 1298 1947.49 164 1297 1947.49 163
"70572" 1299 1947.49 165 1298 1947.49 164
"70572" 1300 1947.49 166 1299 1947.49 165
"70572" 1301 1947.49 167 1300 1947.49 166
"70572" 1302 1947.49 168 1301 1947.49 167
"70572" 1303 1947.49 169 1302 1947.49 168
"70572" 1304 1947.49 170 1303 1947.49 169
"70572" 1305 1947.49 171 1304 1947.49 170
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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 "20260327" "20260425" "20260426"
route_long_name_contains_short_name WARNING 1

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`.
"5640" 16 "RS" "RS Lot Shuttle"
stop_without_stop_time WARNING 15

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.
11 "150199" "Avent Ferry Rd at Trailwood Dr (EB)"
19 "179279" "Blue Ridge Rd at Trinity Rd (NB)"
20 "181320" "Carter Finley Park & Ride (State Fair)"
23 "154816" "Cates Ave at Witherspoon Student Center"
34 "159134" "Dan Allen Dr at Cates Ave"
47 "150208" "Events Lot"
48 "181322" "Faircloth St at Brookwood Dr (NB)"
49 "181321" "Faircloth St at Meredith College (SB)"
63 "154817" "Greek Tailgate"
83 "154837" "Lenovo Center"
89 "154394" "Morrill Dr at Cates Ave (NB)"
92 "201458" "Oglethorpe at Westchase"
101 "154815" "Trinity Rd (Red Terror)"
105 "150207" "Varsity Dr at Greek Village Dr"
116 "194060" "Western Blvd at Morrill Dr (WB)"