ey-vizur-ftp — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T23:02:36Z,
for the dataset file:///shared/ey-vizur-ftp_5aa019c7.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:
TRENMO
Feed Email:
info.gtfs@trenmo.com
Feed Language:
Portuguese
Feed Start Date:
2026-04-17
Feed End Date:
2026-12-31

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. transfers.txt
  10. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 72
  • Shapes: 329
  • Stops: 2851
  • Trips: 1308

Specification Compliance report

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

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 15

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`.
"7mtj" 162609 4888.53 114 162607 4888.53 113
"92k2" 37351 5035.48 146 37350 5035.48 145
"7oyr" 159 6341.26 157 158 6341.26 156
"rl0w" 14912 3940.53 97 14911 3940.53 96
"tphj" 128451 21393.48 400 128447 21393.48 399
"vhc4" 150426 6434.8 63 150421 6434.8 62
"y57r" 83997 2519.49 93 83996 2519.49 92
"332d" 164101 13660.18 276 164100 13660.18 275
"vpwt" 84502 4262.79 68 84500 4262.79 67
"6w1z" 10112 3704.4 106 10110 3704.4 105
"catt" 160921 27417.23 454 160918 27417.23 453
"hjiz" 22822 36167.99 650 22819 36167.99 649
"3sxo" 22254 12313.92 290 22253 12313.92 289
"mpfg" 169924 2193.98 41 169923 2193.98 40
"bq7f" 107356 16468.15 345 107352 16468.15 344
expired_calendar WARNING 4

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "V3-U"
3 "V3-S"
4 "V3-DF"
34 "XV-U"