GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T19:59:28Z,
for the dataset file:///shared/pks-nova_3cc1d6c5.zip. No country code was provided.

Summary

Agencies included

PKS Nova
- website: https://www.pksnova.pl/pl/kontakt
- phone number:
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Email:
alex@busmaps.com: Feed Language:
Polish: Feed Start Date:
2026-06-13: Feed End Date:
2026-06-26: Service Window:
2026-06-13 to 2026-06-26 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
feed_info.txt
routes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 269
Shapes: 0
Stops: 3982
Trips: 1071

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Feed Information Route Colors Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types

Specification Compliance report

4 notices reported (0 errors, 3 warnings, 1 infos)

Notice Code

Severity

Total

feed_expiration_date30_days

WARNING

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	"20260619"	"20260626"	"20260719"

mixed_case_recommended_field

WARNING

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"	"GAĆ , DG/105715b/01/02"	821
"stops.txt"	"stop_name"	"GAĆ , DG/105715b/01/02"	822

trip_headsign_matches_intermediate_stop

INFO

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`.	tripId (?) The id of the trip with the problematic headsign.	tripHeadsign (?) The headsign value that matches an intermediate stop name.	stopId1 (?) The id of the intermediate stop whose name matches the headsign.	stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign.	stopId2 (?) The id of the actual last stop of the trip.
7	"105837-44912992"	"Siemiatycze Ul.Kościuszki"	"105837-1872780:1939936"	0	"105837-1872780:1939937"