GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2025-03-26T01:10:19+02:00,
for the dataset https://www.visimarsrutai.lt/gtfs/UkmergesR.zip. No country code was provided.

Use this report alongside our documentation.

⚠ This feed contains GTFS Flex features. Please note that GTFS Flex validation support is still in development. You can manually review all the validation rules for Flex data here.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

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: 18
  • Shapes: 78
  • Stops: 217
  • Trips: 298

Specification Compliance report

3669 notices reported (0 errors, 3653 warnings, 16 infos)

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 2

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"22929" 11995 10692.2 126 11994 10692.2 125
"22929" 12014 12831.4 145 12013 12831.4 144
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 3648

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 3648 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 "157256" 1
3 "157256" 2
4 "157256" 3
5 "157256" 4
6 "157256" 5
7 "157256" 6
8 "157256" 7
9 "157256" 8
10 "157256" 9
11 "157256" 10
12 "157256" 11
13 "157256" 12
14 "157256" 13
15 "157256" 14
16 "157256" 15
17 "157256" 16
18 "157256" 17
19 "157256" 18
20 "157256" 19
21 "157256" 20
22 "3845975" 1
23 "3845975" 2
24 "3845975" 3
25 "3845975" 4
26 "3845975" 5
27 "3845975" 6
28 "3845975" 7
29 "3845975" 8
30 "3845975" 9
31 "3845975" 10
32 "3845976" 1
33 "3845976" 2
34 "3845976" 3
35 "3845976" 4
36 "3845976" 5
37 "3845976" 6
38 "3845976" 7
39 "3845976" 8
40 "3845976" 9
41 "3845976" 10
42 "4935918" 1
43 "4935918" 2
44 "4935918" 3
45 "4935918" 4
46 "4935918" 5
47 "4935918" 6
48 "4935918" 7
49 "4935918" 8
50 "4935918" 9
51 "4935918" 10
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.
"routes.txt" "route_long_name" "UKMERGĖ- MIŠNIŪNAI PER LIAUŠIUS" 19
"stops.txt" "stop_name" "kulniškiai" 156
unknown_column INFO 16

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" "eligibility_restricted" 10
"routes.txt" "bikes_allowed" 11
"routes.txt" "regional_fare_card" 12
"stops.txt" "vehicle_type" 13
"stops.txt" "mta_stop_id" 16
"stops.txt" "regional_fare_card" 17
"stop_times.txt" "note_id" 3
"trips.txt" "note_id" 2
"trips.txt" "mean_duration_factor" 12
"trips.txt" "mean_duration_offset" 13
"trips.txt" "safe_duration_factor" 14
"trips.txt" "safe_duration_offset" 15
"trips.txt" "cars_allowed" 16
"trips.txt" "peak_offpeak" 17
"trips.txt" "mta_trip_id" 18
"trips.txt" "boarding_type" 19