GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2024-12-19T01:10:11+02:00,
for the dataset https://www.visimarsrutai.lt/gtfs/SiauliuR.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. shapes.txt
  5. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 0
  • Shapes: 2
  • Stops: 20
  • Trips: 12

Specification Compliance report

150 notices reported (13 errors, 136 warnings, 1 infos)

Notice Code Severity Total
foreign_key_violation ERROR 12

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 2
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 3
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 4
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 5
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 6
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 7
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 8
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 9
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 10
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 11
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 12
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "3001" 13
missing_required_file ERROR 1

missing_required_file

A required file is missing.

If this notice is triggered for every core file, it might be a problem with the input. To create a zip file from the GTFS .txt files: select all the .txt files, right-click, and compress. Do not compress the folder containing the files.

You can see more about this notice here.

filename (?) The name of the faulty file.
"routes.txt"
expired_calendar WARNING 6

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.
51 "13006"
22 "13653"
20 "13137"
58 "16604"
10 "16603"
19 "13030"
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 129

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 129 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 "7490821" 1
3 "7490821" 3
4 "7490821" 4
5 "7490821" 5
6 "7490821" 6
7 "7490821" 7
8 "7490821" 8
9 "7490821" 9
10 "7490821" 10
11 "7490821" 11
12 "7490821" 12
13 "7490821" 13
14 "7490822" 1
15 "7490822" 3
16 "7490822" 4
17 "7490822" 5
18 "7490822" 7
19 "7490822" 8
20 "7490822" 9
21 "7490822" 10
22 "7490822" 11
23 "7490822" 12
24 "7490822" 13
25 "7490823" 1
26 "7490823" 2
27 "7490823" 4
28 "7490823" 5
29 "7490823" 7
30 "7490823" 8
31 "7490823" 9
32 "7490823" 10
33 "7490823" 11
34 "7490823" 12
35 "7490823" 13
36 "7490825" 1
37 "7490825" 3
38 "7490825" 4
39 "7490825" 5
40 "7490825" 7
41 "7490825" 8
42 "7490825" 9
43 "7490825" 10
44 "7490825" 11
45 "7490825" 12
46 "7490825" 13
47 "7490826" 1
48 "7490826" 2
49 "7490826" 4
50 "7490826" 5
51 "7490826" 6
unknown_column INFO 1

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.
"stops.txt" "vehicle_type" 13