GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2025-12-10T01:45:15+02:00,
for the dataset https://www.visimarsrutai.lt/gtfs/KretingosR_20251210014500.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.

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: 45
  • Shapes: 77
  • Stops: 279
  • Trips: 254

Specification Compliance report

3870 notices reported (5 errors, 3833 warnings, 32 infos)

Notice Code Severity Total
foreign_key_violation ERROR 5

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.
"stop_times.txt" "stop_id" "stops.txt" "stop_id" "91324" 3681
"stop_times.txt" "stop_id" "stops.txt" "stop_id" "96497" 3682
"stop_times.txt" "stop_id" "stops.txt" "stop_id" "100644" 3693
"stop_times.txt" "stop_id" "stops.txt" "stop_id" "21255" 3699
"stop_times.txt" "stop_id" "stops.txt" "stop_id" "21255" 3713
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 10

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

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 small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"34101" 29059 3241.6 163 29058 3241.6 162 0.0623586881758763
"34067" 25666 49177.4 805 25665 49177.4 804 0.0623586881758763
"34096" 28263 3241.6 163 28262 3241.6 162 0.0623586881758763
"36319" 33622 31015.9 528 33621 31015.9 527 0.0623586881758763
"36317" 32418 38911.6 654 32417 38911.6 653 0.0623586881758763
"34086" 27519 3793.2 180 27518 3793.2 179 0.0623586881758763
"34086" 28065 17842.1 726 28064 17842.1 725 0.06236154185211733
"34084" 26770 3793.2 180 26769 3793.2 179 0.0623586881758763
"33950" 11682 42609.2 716 11681 42609.2 715 0.0623586881758763
"34079" 26355 10297.4 210 26354 10297.4 209 0.06236154185211733
equal_shape_distance_same_coordinates WARNING 90

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.

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

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`.
"41235" 38369 144.7 9 38368 144.7 8
"41235" 38391 1229.5 31 38390 1229.5 30
"41235" 38408 1769.7 48 38407 1769.7 47
"41235" 38456 2925.4 96 38455 2925.4 95
"41235" 38466 3374.1 106 38465 3374.1 105
"41235" 38495 4099.1 135 38494 4099.1 134
"41235" 38527 4969.4 167 38526 4969.4 166
"41235" 38537 5575.5 177 38536 5575.5 176
"41235" 38553 6110.2 193 38552 6110.2 192
"41235" 38566 6612.1 206 38565 6612.1 205
"41235" 38663 9214.8 303 38662 9214.8 302
"41235" 38698 10496.6 338 38697 10496.6 337
"41235" 38787 12857.4 427 38786 12857.4 426
"41235" 38824 14404.3 464 38823 14404.3 463
"41235" 38847 15954.9 487 38846 15954.9 486
"41235" 38924 17558.2 564 38923 17558.2 563
"41234" 37468 945.2 71 37467 945.2 70
"41234" 37796 8498.9 399 37795 8498.9 398
"41234" 37869 9990.3 472 37868 9990.3 471
"41234" 37898 11754.0 501 37897 11754.0 500
"41234" 37936 13276.0 539 37935 13276.0 538
"41234" 38018 15421.2 621 38017 15421.2 620
"41234" 38057 16862.8 660 38056 16862.8 659
"41234" 38143 19312.1 746 38142 19312.1 745
"41234" 38173 19980.3 776 38172 19980.3 775
"41234" 38187 20508.9 790 38186 20508.9 789
"41234" 38200 21223.4 803 38199 21223.4 802
"41234" 38238 21911.0 841 38237 21911.0 840
"41234" 38254 22536.1 857 38253 22536.1 856
"41234" 38262 22919.0 865 38261 22919.0 864
"41234" 38315 24071.8 918 38314 24071.8 917
"41234" 38329 24551.4 932 38328 24551.4 931
"41234" 38349 25511.3 952 38348 25511.3 951
"33971" 14809 26845.6 695 14808 26845.6 694
"34101" 29693 17790.7 797 29692 17790.7 796
"34096" 28886 17507.2 786 28885 17507.2 785
"46070" 39674 8150.6 373 39673 8150.6 372
"46070" 39747 9642.6 446 39746 9642.6 445
"46070" 39776 11406.4 475 39775 11406.4 474
"46070" 39814 12928.4 513 39813 12928.4 512
"46070" 39896 15073.6 595 39895 15073.6 594
"46070" 39935 16515.2 634 39934 16515.2 633
"46070" 40021 18964.5 720 40020 18964.5 719
"46070" 40051 19632.6 750 40050 19632.6 749
"46070" 40065 20161.3 764 40064 20161.3 763
"46070" 40078 20875.8 777 40077 20875.8 776
"46070" 40116 21563.3 815 40115 21563.3 814
"46070" 40148 22497.0 847 40147 22497.0 846
"46070" 40173 23234.5 872 40172 23234.5 871
"46070" 40224 24425.5 923 40223 24425.5 922
expired_calendar WARNING 1

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.
19 "48594"
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 3722

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 3722 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 "7558076" 1
3 "7558076" 3
4 "7558076" 4
5 "7558076" 5
6 "7558079" 1
7 "7558079" 2
8 "7558079" 3
9 "7558079" 4
10 "7558079" 5
11 "7558079" 6
12 "7558079" 7
13 "7558079" 8
14 "7558079" 9
15 "7558079" 10
16 "7558079" 11
17 "7558079" 12
18 "7558081" 1
19 "7558081" 2
20 "7558081" 3
21 "7558081" 4
22 "7558081" 5
23 "7558081" 6
24 "7558081" 7
25 "7558081" 8
26 "7558081" 9
27 "7558081" 10
28 "7558081" 11
29 "7558081" 12
30 "7558081" 13
31 "7558081" 14
32 "7558081" 15
33 "7558081" 16
34 "7558081" 17
35 "7558085" 1
36 "7558085" 2
37 "7558085" 3
38 "7558085" 4
39 "7558085" 5
40 "7558085" 6
41 "7558085" 7
42 "7558085" 8
43 "7558085" 9
44 "7558085" 10
45 "7558085" 11
46 "7558085" 12
47 "7558085" 13
48 "7558085" 14
49 "7558085" 15
50 "7558085" 16
51 "7558086" 1
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_short_name" "50AB" 39
"trips.txt" "trip_short_name" "50AB" 237
stop_too_far_from_shape WARNING 5

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.
237 "46070" "8155052" 3681 "91324" "" [55.721029,21.125873000000002] 6483442.286104919
237 "46070" "8155052" 3682 "96497" "" [55.721029,21.125873000000002] 6483442.286104919
237 "46070" "8155052" 3693 "100644" "" [55.721029,21.125873000000002] 6483442.286104919
124 "46075" "8155064" 3713 "21255" "" [55.881766,21.263633000000002] 6503280.007336191
45 "46072" "8155057" 3699 "21255" "" [55.793309,21.376443000000002] 6497388.908106137
stop_without_stop_time WARNING 2

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
270 "73549" "Budriai"
271 "73550" "Mišučiai"
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