GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2025-10-19T00:25:15+03:00,
for the dataset https://www.visimarsrutai.lt/gtfs/BirzuR.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. fare_attributes.txt
  5. fare_rules.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 24
  • Shapes: 47
  • Stops: 346
  • Trips: 63

Specification Compliance report

1141 notices reported (0 errors, 1109 warnings, 32 infos)

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 17

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`.
"41064" 34106 416.0 10 34105 416.0 9
"41064" 34117 833.9 21 34116 833.9 20
"41064" 34126 1241.8 30 34125 1241.8 29
"41064" 34181 3380.8 85 34180 3380.8 84
"41064" 34225 5416.3 129 34224 5416.3 128
"41064" 34255 6534.2 159 34254 6534.2 158
"41064" 34266 6926.2 170 34265 6926.2 169
"41064" 34272 7137.9 176 34271 7137.9 175
"41064" 34279 7443.8 183 34278 7443.8 182
"41064" 34289 7917.1 193 34288 7917.1 192
"41064" 34300 8335.0 204 34299 8335.0 203
"40928" 33944 124.2 5 33943 124.2 4
"40928" 33951 423.7 12 33950 423.7 11
"40928" 33955 550.6 16 33954 550.6 15
"40928" 33968 1051.9 29 33967 1051.9 28
"40928" 33991 1960.6 52 33990 1960.6 51
"40928" 34042 4160.8 103 34041 4160.8 102
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 1087

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 1087 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 "59839" 1
3 "59839" 2
4 "59839" 3
5 "59839" 4
6 "59839" 5
7 "59839" 6
8 "59839" 7
9 "59839" 8
10 "59839" 9
11 "59839" 10
12 "59839" 11
13 "59839" 12
14 "59839" 13
15 "59839" 14
16 "59839" 15
17 "59839" 16
18 "59839" 17
19 "59839" 18
20 "59839" 19
21 "59839" 20
22 "59839" 21
23 "59839" 22
24 "59839" 23
25 "59839" 24
26 "59839" 25
27 "59839" 26
28 "59839" 27
29 "59839" 28
30 "59839" 29
31 "59839" 30
32 "59839" 31
33 "1627951" 1
34 "1627951" 2
35 "1627951" 3
36 "1627951" 4
37 "1627951" 5
38 "1627951" 6
39 "1627951" 7
40 "1627951" 8
41 "1627951" 9
42 "1627951" 10
43 "1627951" 11
44 "1627951" 12
45 "1627951" 13
46 "1627951" 14
47 "1627951" 15
48 "1627951" 16
49 "1627951" 17
50 "1627951" 18
51 "1627951" 19
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.
"stops.txt" "stop_name" "PALIŪNIŠKIS II" 187
"stops.txt" "stop_name" "IKI prekybos centras" 319
stops_match_shape_out_of_order WARNING 2

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
31 "28435" "7339430" 730 "64819" "Suostas" [56.32837413018391,24.713657886432735] 729 "16112" "Svydžiai" [56.352930797976754,24.686322368913352]
30 "28434" "7339429" 706 "10057" "Svydžiai" [56.35334128457164,24.685572701413516] 705 "64820" "Suostas" [56.32837775901334,24.713656830174433]
unknown_column INFO 32

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.
"fare_attributes.txt" "journey_duration" 8
"routes.txt" "eligibility_restricted" 11
"routes.txt" "bikes_allowed" 12
"routes.txt" "regional_fare_card" 14
"stops.txt" "stop_direction" 12
"stops.txt" "vehicle_type" 14
"stops.txt" "mta_stop_id" 17
"stops.txt" "regional_fare_card" 18
"stop_times.txt" "start_service_area_id" 1
"stop_times.txt" "end_service_area_id" 2
"stop_times.txt" "note_id" 5
"stop_times.txt" "to_stop_sequence" 16
"stop_times.txt" "route_short_name" 18
"stop_times.txt" "start_service_area_radius" 24
"stop_times.txt" "end_service_area_radius" 25
"stop_times.txt" "fare_period_id" 26
"stop_times.txt" "departure_buffer" 27
"stop_times.txt" "track" 28
"stop_times.txt" "mean_duration_factor" 29
"stop_times.txt" "mean_duration_offset" 30
"stop_times.txt" "safe_duration_factor" 31
"stop_times.txt" "safe_duration_offset" 32
"stop_times.txt" "free_running_flag" 33
"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