GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-23T07:27:08Z,
for the dataset file:///shared/ciechanow.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • ZAKŁAD KOMUNIKACJI MIEJSKIEJ W CIECHANOWIE SP. Z O.O.

Feed Info

Publisher Name:
unofficial Ciechanow gtfs, generated from T4B by lz
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2025-12-13
Feed End Date:
2025-12-26

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 15
  • Shapes: 123
  • Stops: 338
  • Trips: 3564

Specification Compliance report

23 notices reported (14 errors, 7 warnings, 2 infos)

Notice Code Severity Total
decreasing_or_equal_stop_time_distance ERROR 14

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

tripId (?) The id of the faulty trip. stopId (?) The id of the faulty stop. csvRowNumber (?) The row number from `stop_times.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. stopSequence (?) The faulty record's `stop_times.stop_sequence`. prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time. prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"70392820" "213" 19216 12.195 25 19215 12.195 24
"70391570" "213" 15989 12.195 25 15988 12.195 24
"70392755" "213" 18635 12.195 25 18634 12.195 24
"70393450" "213" 20742 12.195 25 20741 12.195 24
"70391635" "213" 16570 12.195 25 16569 12.195 24
"70393385" "213" 20161 12.195 25 20160 12.195 24
"70392030" "213" 17452 12.195 25 17451 12.195 24
"70391965" "213" 16871 12.195 25 16870 12.195 24
"70393780" "213" 21043 12.195 25 21042 12.195 24
"70392425" "213" 18334 12.195 25 18333 12.195 24
"70392360" "213" 17753 12.195 25 17752 12.195 24
"70391240" "213" 15688 12.195 25 15687 12.195 24
"70393845" "213" 21624 12.195 25 21623 12.195 24
"70391175" "213" 15107 12.195 25 15106 12.195 24
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 "20251223" "20251226" "20251230"
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
mixed_case_recommended_field WARNING 2

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.

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" "PEC - pętla" 280
"agency.txt" "agency_name" "ZAKŁAD KOMUNIKACJI MIEJSKIEJ W CIECHANOWIE SP. Z O.O." 2
stop_too_far_from_shape_using_user_distance WARNING 1

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
3453 "13_0_u5wopZjtoVPKvL5or0D0zw==" "70391339" 74935 "114" "Pęchcin" [52.85474,20.540949999999995] 1356.72507737961
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
732 "2_4_5YZPPrgKIwLfHIESDy1q2A==" "70391175" 15107 "213" "Rzeczki, pętla" [52.84141006352933,20.690431953215615] 15106 "212" "Rzeczki, pętla" [52.84141010100243,20.690433105329586]
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.
"20251223" "20251215" "20251223"
unknown_column INFO 2

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.
"trips.txt" "brigade" 6
"feed_info.txt" "feed_timezone" 3