GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 6.0.0 at 2025-06-14T00:10:20+03:00,
for the dataset https://www.visimarsrutai.lt/gtfs/AlytausR.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: 67
  • Shapes: 239
  • Stops: 825
  • Trips: 1282

Specification Compliance report

27657 notices reported (0 errors, 27625 warnings, 32 infos)

Notice Code Severity Total
duplicate_route_name WARNING 2

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
9 "16021" 11 "6209" "M1" "Alytus - Geniai" 3 "48"
45 "16052" 49 "6212" "M23" "Alytus - Punia - Butrimonys - Eigirdonys" 3 "48"
equal_shape_distance_same_coordinates WARNING 1

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`.
"29098" 22553 21944.3 914 22552 21944.3 913
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 27608

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

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" "IKI parduotuvė" 531
"stops.txt" "stop_name" "IKI parduotuvė" 532
"trips.txt" "trip_short_name" "7 vasaros" 233
"trips.txt" "trip_short_name" "1 vasaros" 234
"trips.txt" "trip_short_name" "1 žiemos" 235
"trips.txt" "trip_short_name" "5 žiemos" 236
"trips.txt" "trip_short_name" "6 žiemos" 237
"trips.txt" "trip_short_name" "2 žiemos" 238
"trips.txt" "trip_short_name" "2 vasaros" 239
"trips.txt" "trip_short_name" "8 vasaros" 240
stop_too_far_from_shape WARNING 2

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.
382 "29093" "7413976" 584 "21366" "Vozbučiai" [54.262253,23.964486] 113.93775557849204
381 "29092" "7413975" 554 "21366" "Vozbučiai" [54.262253,23.964486] 113.93775557849204
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.
1218 "29102" "7413991" 678 "71231" "Žuvintai" [54.448579423202126,23.62330650767253] 677 "71255" "Litvanciškai" [54.41436513808293,23.67340583550103]
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