GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2024-12-19T03:10:13+02:00,
for the dataset https://www.visimarsrutai.lt/gtfs/PanevezioM.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

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

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 21
  • Shapes: 129
  • Stops: 249
  • Trips: 1712

Specification Compliance report

29604 notices reported (0 errors, 29602 warnings, 2 infos)

Notice Code Severity Total
expired_calendar WARNING 29

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.
15 "42604"
7 "42605"
4 "49172"
21 "49171"
17 "49170"
26 "49192"
14 "49191"
19 "49190"
23 "49179"
11 "49178"
10 "49177"
22 "49176"
9 "49175"
29 "49174"
28 "49173"
27 "44037"
2 "38552"
20 "44035"
6 "49183"
5 "49182"
24 "49181"
8 "49180"
3 "49169"
13 "49189"
25 "49188"
30 "49187"
12 "49186"
16 "49185"
18 "49184"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
missing_timepoint_value WARNING 29567

missing_timepoint_value

stop_times.timepoint value is missing for a record.

Even though the column timepoint is optional in stop_times.txt according to the specification, stop_times.timepoint should not be empty when provided.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "7202065" 1
3 "7202065" 2
4 "7202065" 3
5 "7202065" 4
6 "7202065" 5
7 "7202065" 6
8 "7202065" 7
9 "7202065" 8
10 "7202065" 9
11 "7202065" 10
12 "7202065" 11
13 "7202065" 12
14 "7202065" 13
15 "7202065" 14
16 "7202065" 15
17 "7202065" 16
18 "7202065" 17
19 "7202096" 1
20 "7202096" 2
21 "7202096" 3
22 "7202096" 4
23 "7202096" 5
24 "7202096" 6
25 "7202096" 7
26 "7202096" 8
27 "7202096" 9
28 "7202096" 10
29 "7202096" 11
30 "7202096" 12
31 "7202096" 13
32 "7202096" 14
33 "7202096" 15
34 "7202096" 16
35 "7202096" 17
36 "7202096" 18
37 "7202104" 1
38 "7202104" 2
39 "7202104" 3
40 "7202104" 4
41 "7202104" 5
42 "7202104" 6
43 "7202104" 7
44 "7202104" 8
45 "7202104" 9
46 "7202104" 10
47 "7202104" 11
48 "7202104" 12
49 "7202104" 13
50 "7202104" 14
51 "7202104" 15
mixed_case_recommended_field WARNING 4

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" "5-oji gimnazija" 166
"stops.txt" "stop_name" "HARJU ELEKTER" 189
"trips.txt" "trip_headsign" "HARJU ELEKTER" 190
"trips.txt" "trip_headsign" "HARJU ELEKTER" 1423
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.
"20241219" "20230731" "20240701"
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.
"routes.txt" "bikes_allowed" 9
"stops.txt" "vehicle_type" 13