Search
  1. Home
  2. Poland Feeds
  3. sochaczew
  4. Source Data Validation Report

sochaczew — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T06:43:05Z,
for the dataset file:///shared/sochaczew_8d5de924.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • ZAKŁAD KOMUNIKACJI MIEJSKIEJ w Sochaczewie

Feed Info

Publisher Name:
unofficial Sochaczew gtfs, generated from T4B by lz
Feed Email:
N/A
Feed Language:
Polish
Feed Start Date:
2026-05-01
Feed End Date:
2026-05-14

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: 10
  • Shapes: 121
  • Stops: 143
  • Trips: 2112

Specification Compliance report

10 notices reported (3 errors, 5 warnings, 2 infos)

Notice Code Severity Total
duplicate_key ERROR 3

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file oldCsvRowNumber (?) The row of the first occurrence. newCsvRowNumber (?) The row of the other occurrence. fieldName1 (?) Composite key's first field name. fieldValue1 (?) Composite key's first value.
"routes.txt" 10 11 "route_id" "E"
"routes.txt" 10 12 "route_id" "E"
"routes.txt" 10 13 "route_id" "E"
duplicate_route_name WARNING 3

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
10 "E" 11 "E" "E" "" 3 "1"
10 "E" 12 "E" "E" "" 3 "1"
10 "E" 13 "E" "E" "" 3 "1"
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 "20260505" "20260514" "20260604"
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
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