si-nap-gtfs — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-31T13:48:35Z,
for the dataset file:///shared/si-nap-gtfs_67ae0a41.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


  • Javno podjetje Ljubljanski potniški promet d.o.o.
  • Nomago d.o.o.
  • Avtobusni promet Murska Sobota d.d.
  • Arriva d.o.o.
  • SŽ - Potniški promet, d.o.o.
  • Prevozi na klic – Nova Gorica
  • Prevozi na klic študent – Maribor
  • Prevozi na klic študent – Ljubljana
  • Prevozi na klic - Celje

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: 9
  • Blocks: 0
  • Routes: 2381
  • Shapes: 3436
  • Stops: 9753
  • Trips: 18325

Specification Compliance report

18449 notices reported (0 errors, 100 warnings, 18349 infos)

Notice Code Severity Total
expired_calendar WARNING 10

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.
16 "2362"
17 "2363"
25 "2340"
28 "2327"
40 "2360"
49 "2365"
61 "2326"
71 "2366"
75 "2345"
78 "2344"
fast_travel_between_consecutive_stops WARNING 6

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
13047 "465221" "65420" 181.1853753394908 1.50987812782909 260004 7 "1150228" "Koseze/Stare" "08:16:00" 210456 8 "1150812" "Koseze/Vodicah" "08:16:30"
13046 "465220" "65420" 181.1853753394908 1.50987812782909 103523 7 "1150228" "Koseze/Stare" "07:11:00" 183831 8 "1150812" "Koseze/Vodicah" "07:11:30"
13044 "465218" "65420" 181.1853753394908 1.50987812782909 32925 7 "1150228" "Koseze/Stare" "07:49:00" 308883 8 "1150812" "Koseze/Vodicah" "07:49:30"
1054 "404110" "59380" 190.52255625685586 1.5876879688071321 68520 14 "1132176" "Želimlje Nučič" "05:55:00" 192747 15 "1132175" "Želimlje" "05:55:30"
7228 "452519" "63552" 265.00946098247607 2.2084121748539673 168102 30 "1167289" "Vižmarje" "05:19:00" 169639 31 "1167164" "Stanežiče" "05:19:30"
13018 "465178" "65420" 206.99818600171483 1.7249848833476236 67290 1 "1131671" "Vojsko/Vodicah" "08:46:00" 21443 2 "1128685" "Vesca/Vodicah" "08:46:30"
leading_or_trailing_whitespaces WARNING 5

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 6497 "stop_name" "Središka "
"stops.txt" 6907 "stop_name" "Središka "
"stops.txt" 7991 "stop_name" "Praproče/P.Krasu "
"stops.txt" 9632 "stop_name" "OŠ Domžale "
"stops.txt" 9633 "stop_name" "OŠ Domžale "
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"
mixed_case_recommended_field WARNING 1

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" "CIVIDALE D.FRIULI C.INTERM.(I)" 6958
service_has_no_active_day_of_the_week WARNING 68

service_has_no_active_day_of_the_week

A service is not valid for any day of the week.

You can see more about this notice here.

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

csvRowNumber (?) The row number in calendar.txt where the error occurs. serviceId (?) The service_id field value.
3 "2320"
4 "2354"
5 "2248"
6 "2303"
7 "2358"
8 "2341"
10 "119"
12 "2278"
14 "1378"
15 "1786"
16 "2362"
17 "2363"
18 "2308"
19 "2321"
21 "1391"
22 "1433"
23 "1683"
24 "2307"
25 "2340"
26 "2351"
28 "2327"
29 "2343"
30 "2348"
31 "2364"
32 "1398"
33 "1377"
35 "1405"
36 "1916"
38 "2319"
39 "1638"
40 "2360"
41 "2138"
42 "2179"
43 "2262"
45 "2353"
46 "2355"
47 "1753"
48 "1639"
49 "2365"
51 "2153"
52 "2305"
53 "2309"
55 "1787"
56 "2356"
58 "2279"
61 "2326"
62 "1923"
63 "2185"
64 "2310"
66 "1381"
stop_has_too_many_matches_for_shape WARNING 6

stop_has_too_many_matches_for_shape

Stop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in shapes.txt.

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. matchCount (?) The number of matches for the stop that is referred to.
9628 "75618" "457770" 68733 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9628 "75618" "457770" 285981 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9648 "75620" "457790" 334470 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9648 "75620" "457790" 261991 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9647 "75619" "457789" 144791 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9647 "75619" "457789" 158051 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
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.
13557 "76736" "465938" 277509 "1123033" "Solkan" [45.96869305305878,13.631059685402601] 1255.0714050313686
13558 "76737" "465939" 340972 "1123032" "Nova Gorica" [46.04615122984819,13.589833413056501] 10444.724447059758
13558 "76737" "465939" 255897 "1123033" "Solkan" [46.04615122984819,13.589833413056501] 9268.024919657073
big_gap_in_service INFO 24

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"2358" "2026-09-30" "2027-06-01" 243
"2342" "2026-08-27" "2026-09-28" 31
"119" "2026-08-31" "2027-07-01" 303
"2278" "2026-10-24" "2027-04-03" 160
"1378" "2026-08-30" "2027-07-03" 306
"1786" "2026-12-17" "2027-01-07" 20
"1433" "2026-12-24" "2027-01-08" 14
"1683" "2026-09-27" "2027-06-05" 250
"1377" "2026-12-19" "2027-01-09" 20
"1916" "2026-08-31" "2026-12-28" 118
"1916" "2026-12-31" "2027-04-26" 115
"1916" "2027-04-30" "2027-06-28" 58
"1638" "2026-08-30" "2027-06-25" 298
"2138" "2026-10-31" "2027-04-03" 153
"2262" "2026-12-19" "2027-01-09" 20
"2335" "2026-10-04" "2026-12-13" 69
"1753" "2026-09-30" "2027-06-01" 243
"1639" "2026-10-31" "2027-04-03" 153
"2153" "2026-10-30" "2027-04-01" 152
"1787" "2026-08-31" "2027-06-25" 297
"2279" "2026-11-01" "2027-04-04" 153
"2330" "2026-08-31" "2026-10-26" 55
"2332" "2026-08-27" "2026-09-28" 31
"1389" "2026-12-18" "2027-01-08" 20
unsorted_stop_times INFO 18325

unsorted_stop_times

Stop times are not sorted by trip_id and stop_sequence.

'stop_times.txt' entries for a given trip are not sorted by stop_sequence, or are not contiguous in the file.

You can see more about this notice here.

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

tripId (?) The faulty record's trip_id. startCsvRowNumber (?) CSV row number of the first stop_times entry for this trip. endCsvRowNumber (?) CSV row number of the last stop_times entry for this trip.
"465598" 11987 332021
"464267" 39577 309989
"464266" 13289 335620
"465597" 31874 350007
"465599" 2911 332922
"464278" 811 349839
"464277" 172 334118
"453598" 1965 345586
"452267" 38352 308647
"453599" 41406 320904
"452268" 95866 326549
"453596" 44767 309217
"452265" 71734 293061
"453597" 5618 318746
"452266" 27832 307564
"464249" 24252 345644
"464248" 170 331819
"465579" 28027 345868
"464245" 7329 333241
"465576" 48881 331345
"464244" 731 341326
"465575" 28427 266970
"464247" 4904 343218
"465578" 15233 303828
"464246" 3444 330680
"465577" 30194 344947
"465583" 2908 338695
"464252" 13071 345837
"465582" 180 343231
"464251" 4905 340050
"464254" 23074 338674
"465585" 45810 329542
"464253" 8195 335205
"465584" 17178 332250
"465581" 9482 333799
"464250" 11043 348675
"465580" 35304 303368
"464259" 10893 336588
"465587" 195 343190
"464256" 34740 342394
"465586" 7629 324755
"464255" 10079 345645
"464258" 4515 306563
"465589" 9595 350006
"465588" 3649 349121
"464257" 5126 349838
"464263" 6007 337553
"465594" 48006 344798
"465593" 9643 316912
"464262" 19737 336790