GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2025-05-02T03:35:16+03:00,
for the dataset https://www.visimarsrutai.lt/gtfs/SiauliuR.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: 40
  • Shapes: 85
  • Stops: 347
  • Trips: 383

Specification Compliance report

4834 notices reported (0 errors, 4818 warnings, 16 infos)

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 23

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`.
"22712" 45493 14396.1 344 45492 14396.1 343
"16675" 10638 14396.1 344 10637 14396.1 343
"16675" 10653 14578.4 359 10652 14578.4 358
"22672" 38123 14396.1 344 38122 14396.1 343
"22672" 38138 14578.4 359 38137 14578.4 358
"22674" 39106 16490.1 440 39105 16490.1 439
"22674" 39121 16672.4 455 39120 16672.4 454
"22675" 40288 19188.3 597 40287 19188.3 596
"22675" 40303 19354.6 612 40302 19354.6 611
"16676" 11597 28853.2 482 11596 28853.2 481
"16676" 11612 29019.5 497 11611 29019.5 496
"22682" 43072 7798.1 157 43071 7798.1 156
"22682" 43087 7964.4 172 43086 7964.4 171
"16568" 7575 14396.1 344 7574 14396.1 343
"16570" 8454 16490.1 440 8453 16490.1 439
"16570" 8469 16672.4 455 8468 16672.4 454
"16612" 9640 19188.3 597 9639 19188.3 596
"16612" 9655 19354.6 612 9654 19354.6 611
"22783" 46463 24083.9 493 46462 24083.9 492
"16949" 15504 7798.1 157 15503 7798.1 156
"16949" 15519 7964.4 172 15518 7964.4 171
"16948" 15193 16490.1 440 15192 16490.1 439
"16948" 15208 16672.4 455 15207 16672.4 454
expired_calendar WARNING 3

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.
52 "32800"
24 "32798"
28 "32795"
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 4776

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 4776 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 "2211661" 1
3 "2211661" 2
4 "2211661" 3
5 "2211661" 4
6 "2211661" 5
7 "2211661" 6
8 "2211661" 7
9 "2211661" 8
10 "2211661" 9
11 "2211661" 10
12 "2211661" 11
13 "2211661" 12
14 "2211661" 13
15 "2211661" 14
16 "2211661" 15
17 "2211661" 16
18 "2211661" 17
19 "2211661" 18
20 "2211661" 19
21 "2211665" 1
22 "2211665" 2
23 "2211665" 3
24 "2211665" 4
25 "2211665" 5
26 "2211665" 6
27 "2211665" 7
28 "2211665" 8
29 "2211665" 9
30 "2211665" 10
31 "2211665" 11
32 "2211665" 12
33 "2211665" 13
34 "2211665" 14
35 "2211665" 15
36 "2211665" 16
37 "2211665" 17
38 "2211665" 18
39 "2211665" 19
40 "2211779" 1
41 "2211779" 2
42 "2211779" 3
43 "2211779" 5
44 "2211779" 6
45 "2211779" 7
46 "2211779" 8
47 "2211779" 9
48 "2211780" 1
49 "2211780" 2
50 "2211780" 3
51 "2211780" 4
mixed_case_recommended_field WARNING 11

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" "140 km" 336
"stops.txt" "stop_name" "140 km" 337
"trips.txt" "trip_short_name" "N73.-DD-MM-7.10" 5
"trips.txt" "trip_short_name" "N56.-MM-DD-7.50" 11
"trips.txt" "trip_short_name" "N63.-DD-MM-15.10" 50
"trips.txt" "trip_short_name" "N63,-DD-MM-14.45" 84
"trips.txt" "trip_short_name" "N59.-DD-Š-MMM-14:00" 88
"trips.txt" "trip_short_name" "N56.-MM-DD-13.30" 283
"trips.txt" "trip_short_name" "N55.-MM-DD-14.25" 285
"trips.txt" "trip_short_name" "N72.-DD-MM-7.25" 345
"trips.txt" "trip_short_name" "N63.-DD-MM-7,00" 376
stop_too_far_from_shape WARNING 3

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
16 "22910" "4973791" 4634 "24190" "Maldeniai" [56.08905,23.080025999999993] 114.55535215311666
123 "18184" "2933102" 2231 "24190" "Maldeniai" [56.08905,23.080025999999993] 114.55535215311666
49 "18185" "2933105" 2245 "24190" "Maldeniai" [56.08905,23.080025999999993] 114.55535215311666
stops_match_shape_out_of_order WARNING 1

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.
12 "22910" "4981065" 4706 "44981" "Apušėliai" [56.058900282912056,23.196604001375526] 4705 "23941" "Žiogai" [56.04871914929978,23.214028627477276]
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