Search
  1. Home
  2. Poland Feeds
  3. ztm-rzesz-mdc
  4. Source Data Validation Report

ztm-rzesz-mdc — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-24T03:22:15Z,
for the dataset file:///shared/ztm-rzesz-mdc_6b98d497.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Zarząd Transportu Miejskiego w Rzeszowie
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2023-01-02
Feed End Date:
2023-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: 500
  • Routes: 229
  • Shapes: 229
  • Stops: 888
  • Trips: 7179

Specification Compliance report

7217 notices reported (6 errors, 7202 warnings, 9 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates ERROR 6

equal_shape_distance_diff_coordinates

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 the 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 different coordinates indicate an error.

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.
"118" 56827 6.7135 136 56826 6.7135 135 5.227250872782178
"32" 14745 6.7135 136 14744 6.7135 135 5.227250872782178
"45" 21802 12.6773 252 21801 12.6773 251 5.227250872782178
"57" 28152 6.7135 136 28151 6.7135 135 5.227250872782178
"74" 36405 6.7135 136 36404 6.7135 135 5.227250872782178
"84" 42152 29.6863 639 42151 29.6863 638 5.227250872782178
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 19

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.
"110" 53424 1.5664 29 53423 1.5664 28 0.028498186466892637
"12" 5041 6.2907 111 5040 6.2907 110 0.02344205655304519
"19" 8205 1.5664 29 8204 1.5664 28 0.028498186466892637
"125" 60365 9.4194 203 60364 9.4194 202 0.028498186466892637
"125" 60376 9.5451 214 60375 9.5451 213 0.02344205655304519
"9" 3771 6.0063 155 3770 6.0063 154 0.028498186466892637
"9" 3782 6.132 166 3781 6.132 165 0.02344205655304519
"130" 63008 2.1639 30 63007 2.1639 29 0.028498186466892637
"130" 63019 2.2775 41 63018 2.2775 40 0.02344205655304519
"38" 17869 10.5259 184 17868 10.5259 183 0.02344205655304519
"140" 67804 2.3543 41 67803 2.3543 40 0.02344205655304519
"144" 69236 4.3432 120 69235 4.3432 119 0.02344205655304519
"50" 23942 1.5664 29 23941 1.5664 28 0.028498186466892637
"53" 25639 1.5664 29 25638 1.5664 28 0.028498186466892637
"170" 80478 6.2907 111 80477 6.2907 110 0.02344205655304519
"81" 40286 10.5259 184 40285 10.5259 183 0.02344205655304519
"82" 40390 2.1639 30 40389 2.1639 29 0.028498186466892637
"82" 40401 2.2775 41 40400 2.2775 40 0.02344205655304519
"84" 41542 1.5017 29 41541 1.5017 28 0.028498186466892637
expired_calendar WARNING 7179

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.

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

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
2 "1"
3 "2"
4 "3"
5 "4"
6 "5"
7 "6"
8 "7"
9 "8"
10 "9"
11 "10"
12 "11"
13 "12"
14 "13"
15 "14"
16 "15"
17 "16"
18 "17"
19 "18"
20 "19"
21 "20"
22 "21"
23 "22"
24 "23"
25 "24"
26 "25"
27 "26"
28 "27"
29 "28"
30 "29"
31 "30"
32 "31"
33 "32"
34 "33"
35 "34"
36 "35"
37 "36"
38 "37"
39 "38"
40 "39"
41 "40"
42 "41"
43 "42"
44 "43"
45 "44"
46 "45"
47 "46"
48 "47"
49 "48"
50 "49"
51 "50"
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 "20260324" "20231231" "20260331"
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 1

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.
"feed_info.txt" 2 "feed_version"
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.
"20260324" "20230102" "20231229"
transfer_distance_above_2_km INFO 9

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.
896 "506" "507" 2.0418911970863736
897 "507" "370" 2.0788457173391044
1061 "424" "425" 2.15998305622911
1100 "468" "628" 3.729384795760127
1103 "1069" "1070" 2.169756300275572
1117 "1066" "1067" 2.3703508439654564
1123 "206" "468" 2.804416823062615
1133 "1057" "750" 3.909976855262014
1136 "750" "1058" 3.8906649663184436