si-nap-gtfs — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-03T15:32:38Z,
for the dataset file:///shared/si-nap-gtfs_d6c46357.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: 2380
  • Shapes: 3431
  • Stops: 9753
  • Trips: 18257

Specification Compliance report

18379 notices reported (0 errors, 94 warnings, 18285 infos)

Notice Code Severity Total
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.
13483 "465221" "65420" 181.1853753394908 1.50987812782909 276878 7 "1150228" "Koseze/Stare" "08:16:00" 208913 8 "1150812" "Koseze/Vodicah" "08:16:30"
13482 "465220" "65420" 181.1853753394908 1.50987812782909 105827 7 "1150228" "Koseze/Stare" "07:11:00" 185548 8 "1150812" "Koseze/Vodicah" "07:11:30"
13480 "465218" "65420" 181.1853753394908 1.50987812782909 35663 7 "1150228" "Koseze/Stare" "07:49:00" 317149 8 "1150812" "Koseze/Vodicah" "07:49:30"
1091 "404110" "59380" 190.52255625685586 1.5876879688071321 73884 14 "1132176" "Želimlje Nučič" "05:55:00" 193153 15 "1132175" "Želimlje" "05:55:30"
7514 "452519" "63552" 265.00946098247607 2.2084121748539673 172468 30 "1167289" "Vižmarje" "05:19:00" 171292 31 "1167164" "Stanežiče" "05:19:30"
13454 "465178" "65420" 206.99818600171483 1.7249848833476236 67859 1 "1131671" "Vojsko/Vodicah" "08:46:00" 27366 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" 8374 "stop_name" "Praproče/P.Krasu "
"stops.txt" 8385 "stop_name" "OŠ Domžale "
"stops.txt" 8395 "stop_name" "OŠ Domžale "
"stops.txt" 8805 "stop_name" "Središka "
"stops.txt" 8840 "stop_name" "Središka "
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)" 8948
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 "2278"
5 "2358"
6 "2341"
8 "119"
9 "2308"
10 "2362"
11 "2363"
12 "1378"
13 "1786"
15 "2353"
16 "2355"
17 "1753"
19 "2326"
20 "1923"
21 "2185"
22 "2310"
23 "2325"
24 "2339"
25 "2324"
27 "2366"
30 "2186"
31 "1381"
32 "2322"
35 "2352"
36 "1033"
37 "2301"
38 "2318"
40 "1389"
42 "2365"
43 "2153"
44 "2305"
45 "2309"
47 "1639"
48 "2356"
50 "2279"
52 "1787"
53 "1916"
55 "2319"
57 "1405"
58 "2306"
59 "2347"
60 "2330"
61 "2344"
62 "2361"
63 "2331"
64 "2345"
65 "2138"
66 "2179"
67 "2262"
68 "2360"
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.
9920 "75618" "457770" 70791 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9920 "75618" "457770" 282411 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9940 "75620" "457790" 329281 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9940 "75620" "457790" 258334 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9939 "75619" "457789" 138582 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
9939 "75619" "457789" 159706 "1123395" "Bled" [46.371272193958,14.106962078526998] 23
stop_too_far_from_shape WARNING 7

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.
18241 "63145" "471877" 263900 "1168798" "Veščica Novak/Ljut." [46.51494706186308,16.242406774940576] 105.53087339808728
13994 "76736" "465938" 277774 "1123033" "Solkan" [45.96869305305878,13.631059685402601] 1255.0714050313686
13995 "76737" "465939" 341541 "1123032" "Nova Gorica" [46.04615122984819,13.589833413056501] 10444.724447059758
13995 "76737" "465939" 253043 "1123033" "Solkan" [46.04615122984819,13.589833413056501] 9268.024919657073
18255 "77550" "471892" 156511 "1168798" "Veščica Novak/Ljut." [46.51494706186308,16.242406774940576] 105.53087339808728
18239 "71437" "471875" 15081 "1168798" "Veščica Novak/Ljut." [46.51494706186308,16.242406774940576] 105.53087339808728
18227 "71439" "471863" 153787 "1168798" "Veščica Novak/Ljut." [46.51494706186308,16.242406774940576] 105.53087339808728
big_gap_in_service INFO 28

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.
"2278" "2026-10-24" "2027-04-03" 160
"2358" "2026-09-30" "2027-06-01" 243
"2342" "2026-06-30" "2026-09-28" 89
"1786" "2026-12-17" "2027-01-01" 14
"2335" "2026-10-04" "2026-12-13" 69
"1753" "2026-09-30" "2027-06-01" 243
"2339" "2026-09-26" "2026-11-07" 41
"2324" "2026-08-15" "2026-10-03" 48
"1917" "2026-06-30" "2026-09-01" 62
"2332" "2026-06-30" "2026-09-28" 89
"2336" "2026-06-30" "2026-09-01" 62
"2298" "2026-06-30" "2026-09-01" 62
"1389" "2026-12-18" "2027-01-08" 20
"2153" "2026-10-30" "2027-04-01" 152
"2311" "2026-06-30" "2026-09-01" 62
"1639" "2026-10-31" "2027-04-03" 153
"2323" "2026-06-30" "2026-08-31" 61
"2279" "2026-11-01" "2027-04-04" 153
"1787" "2026-08-31" "2027-06-25" 297
"1916" "2026-08-31" "2026-12-28" 118
"1916" "2026-12-31" "2027-06-28" 178
"2367" "2026-09-27" "2026-12-13" 76
"2330" "2026-08-31" "2026-10-26" 55
"2138" "2026-10-31" "2027-04-03" 153
"2262" "2026-12-19" "2027-01-09" 20
"1638" "2026-08-30" "2027-06-25" 298
"1683" "2026-09-27" "2027-06-05" 250
"1377" "2026-12-19" "2027-01-09" 20
unsorted_stop_times INFO 18257

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 18257 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" 12726 329795
"464267" 40148 312073
"464266" 13082 330301
"465597" 30608 348677
"465599" 2115 331304
"464278" 676 348962
"464277" 33 330903
"453598" 14356 344662
"452267" 45628 316926
"453599" 41878 326717
"452268" 98964 326392
"453596" 44652 314088
"452265" 72896 296794
"453597" 5770 319944
"452266" 27397 313173
"464249" 21812 342739
"464248" 103 329659
"465579" 31672 345179
"464245" 7067 338441
"465576" 54184 332667
"464244" 740 343749
"465575" 27853 265693
"464247" 3828 342383
"465578" 15682 298708
"464246" 3603 328598
"465577" 29204 342108
"464252" 15579 345133
"465583" 15883 338127
"465582" 65 342385
"464251" 3861 340495
"464254" 20449 338152
"465585" 46404 332332
"464253" 8538 336056
"465584" 20005 334509
"465581" 9984 338995
"464250" 12014 348274
"465580" 39033 296711
"464259" 9840 336382
"465587" 95 342772
"464256" 34897 341823
"465586" 196 326230
"464255" 10890 342700
"464258" 7484 308615
"465589" 10380 326193
"465588" 2887 348669
"464257" 5371 348977
"465594" 2988 344403
"464263" 5919 335408
"465593" 6532 317806
"464262" 17524 334486