wiener-linien-original — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T12:35:38Z,
for the dataset file:///shared/wiener-linien-original_70d9d5bc.zip. No country code was provided.

Use this report alongside our documentation.

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: 2
  • Blocks: 371
  • Routes: 704
  • Shapes: 4813
  • Stops: 4264
  • Trips: 310658

Specification Compliance report

1028 notices reported (7 errors, 676 warnings, 345 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates ERROR 7

equal_shape_distance_diff_coordinates

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 the 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 different coordinates indicate an error.

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.
"23-88B-j26-24.4.R" 784481 4862.98 109 784480 4862.98 108 4.623753243759582
"23-95B-j26-1.2.R" 806417 2038.36 67 806416 2038.36 66 124.81953277605766
"23-88B-j26-24.5.R" 784627 4862.98 109 784626 4862.98 108 4.623753243759582
"23-88B-j26-31.3.R" 784916 4862.98 109 784915 4862.98 108 4.623753243759582
"23-88B-j26-31.5.R" 785208 4862.98 109 785207 4862.98 108 4.623753243759582
"23-88B-j26-31.4.R" 785062 4862.98 109 785061 4862.98 108 4.623753243759582
"23-88B-j26-24.3.R" 784335 4862.98 109 784334 4862.98 108 4.623753243759582
duplicate_route_name WARNING 386

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.

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

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`.
5 "11-WLB-j26-1" 9 "11-WLB-j26-5" "BB" "Wien Oper - Aßmayergasse - Inzersdorf Lokalbahn - Wiener Neudorf - Baden Landesklinikum - Baden Josefsplatz" 0 "03"
15 "21-U1-j26-1" 16 "21-U1-j26-2" "U1" "Oberlaa - Leopoldau" 1 "04"
15 "21-U1-j26-1" 17 "21-U1-j26-24" "U1" "Oberlaa - Leopoldau" 1 "04"
15 "21-U1-j26-1" 19 "21-U1-j26-31" "U1" "Oberlaa - Leopoldau" 1 "04"
21 "21-U2-j26-1" 22 "21-U2-j26-2" "U2" "Seestadt - Schottentor" 1 "04"
21 "21-U2-j26-1" 23 "21-U2-j26-24" "U2" "Seestadt - Schottentor" 1 "04"
21 "21-U2-j26-1" 25 "21-U2-j26-31" "U2" "Seestadt - Schottentor" 1 "04"
21 "21-U2-j26-1" 27 "21-U2-j26-5" "U2" "Seestadt - Schottentor" 1 "04"
28 "21-U3-j26-1" 29 "21-U3-j26-2" "U3" "Ottakring - Simmering" 1 "04"
28 "21-U3-j26-1" 30 "21-U3-j26-24" "U3" "Ottakring - Simmering" 1 "04"
28 "21-U3-j26-1" 32 "21-U3-j26-31" "U3" "Ottakring - Simmering" 1 "04"
34 "21-U4-j26-1" 35 "21-U4-j26-2" "U4" "Hütteldorf - Heiligenstadt" 1 "04"
34 "21-U4-j26-1" 36 "21-U4-j26-24" "U4" "Hütteldorf - Heiligenstadt" 1 "04"
34 "21-U4-j26-1" 38 "21-U4-j26-31" "U4" "Hütteldorf - Heiligenstadt" 1 "04"
42 "21-U6-j26-2" 43 "21-U6-j26-24" "U6" "Siebenhirten - Floridsdorf" 1 "04"
42 "21-U6-j26-2" 44 "21-U6-j26-3" "U6" "Siebenhirten - Floridsdorf" 1 "04"
42 "21-U6-j26-2" 45 "21-U6-j26-31" "U6" "Siebenhirten - Floridsdorf" 1 "04"
42 "21-U6-j26-2" 46 "21-U6-j26-4" "U6" "Siebenhirten - Floridsdorf" 1 "04"
42 "21-U6-j26-2" 49 "21-U6-j26-7" "U6" "Siebenhirten - Floridsdorf" 1 "04"
41 "21-U6-j26-1" 50 "21-U6-j26-90" "U6" "Siebenhirten - Floridsdorf Baustellenfahrplan" 1 "04"
51 "22-10-j26-1" 52 "22-10-j26-2" "10" "Dornbach - Unter St. Veit, Hummelgasse" 0 "04"
51 "22-10-j26-1" 53 "22-10-j26-24" "10" "Dornbach - Unter St. Veit, Hummelgasse" 0 "04"
54 "22-11-j26-1" 55 "22-11-j26-2" "11" "Otto-Probst-Platz - Kaiserebersdorf, Zinnergasse" 0 "04"
56 "22-11-j26-24" 57 "22-11-j26-3" "11" "Otto-Probst-Platz - Geiereckstraße" 0 "04"
56 "22-11-j26-24" 58 "22-11-j26-31" "11" "Otto-Probst-Platz - Geiereckstraße" 0 "04"
56 "22-11-j26-24" 59 "22-11-j26-4" "11" "Otto-Probst-Platz - Geiereckstraße" 0 "04"
56 "22-11-j26-24" 60 "22-11-j26-5" "11" "Otto-Probst-Platz - Geiereckstraße" 0 "04"
61 "22-12-j26-1" 62 "22-12-j26-2" "12" "Hillerstraße - Josefstädter Straße" 0 "04"
61 "22-12-j26-1" 63 "22-12-j26-24" "12" "Hillerstraße - Josefstädter Straße" 0 "04"
61 "22-12-j26-1" 65 "22-12-j26-31" "12" "Hillerstraße - Josefstädter Straße" 0 "04"
68 "22-18-j26-24" 69 "22-18-j26-3" "18" "Westbahnhof - Schlachthausgasse" 0 "04"
68 "22-18-j26-24" 70 "22-18-j26-31" "18" "Westbahnhof - Schlachthausgasse" 0 "04"
73 "22-18-j26-7" 75 "22-18-j26-90" "18" "Burggasse-Stadthalle - Schlachthausgasse" 0 "04"
76 "22-1-j26-1" 80 "22-1-j26-2" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 81 "22-1-j26-24" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 82 "22-1-j26-3" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 83 "22-1-j26-31" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 84 "22-1-j26-4" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 87 "22-1-j26-7" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 88 "22-1-j26-8" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
76 "22-1-j26-1" 90 "22-1-j26-99" "1" "Prater, Hauptallee - Stefan-Fadinger-Platz" 0 "04"
91 "22-25-j26-1" 92 "22-25-j26-24" "25" "Aspern, Oberdorfstraße - Floridsdorf" 0 "04"
91 "22-25-j26-1" 93 "22-25-j26-31" "25" "Aspern, Oberdorfstraße - Floridsdorf" 0 "04"
94 "22-26-j26-1" 97 "22-26-j26-31" "26" "Hausfeldstraße - Strebersdorf" 0 "04"
98 "22-27-j26-1" 100 "22-27-j26-24" "27" "Aspern Nord - Strebersdorf,Edmund-Hawranek-Platz" 0 "04"
98 "22-27-j26-1" 101 "22-27-j26-31" "27" "Aspern Nord - Strebersdorf,Edmund-Hawranek-Platz" 0 "04"
102 "22-2-j26-1" 103 "22-2-j26-2" "2" "Dornbach - Friedrich-Engels-Platz" 0 "04"
102 "22-2-j26-1" 104 "22-2-j26-24" "2" "Dornbach - Friedrich-Engels-Platz" 0 "04"
102 "22-2-j26-1" 105 "22-2-j26-3" "2" "Dornbach - Friedrich-Engels-Platz" 0 "04"
102 "22-2-j26-1" 106 "22-2-j26-31" "2" "Dornbach - Friedrich-Engels-Platz" 0 "04"
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 4

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.
"23-38A-j26-31.15.R" 631785 1888.81 107 631784 1888.81 106 0.0011119511293433693
"22-D-j26-4.28.H" 510297 361.46 18 510296 361.46 17 0.0013361665531705282
"23-74A-j26-2.6.R" 743695 2155.76 46 743694 2155.76 45 0.001336283568112423
"22-D-j26-31.13.H" 504293 361.46 18 504292 361.46 17 0.0013361665531705282
equal_shape_distance_same_coordinates WARNING 6

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`.
"23-38A-j26-31.14.R" 631188 1523.74 67 631187 1523.74 66
"23-38A-j26-31.15.R" 631851 3412.55 173 631850 3412.55 172
"22-D-j26-31.30.R" 506406 5866.79 164 506405 5866.79 163
"22-D-j26-4.32.R" 511345 5866.79 163 511344 5866.79 162
"22-D-j26-4.34.R" 511602 2960.31 115 511601 2960.31 114
"22-D-j26-31.35.R" 507275 2960.31 116 507274 2960.31 115
expired_calendar WARNING 274

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.

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

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
3 "T0#1"
4 "T0#10"
6 "T0#12"
7 "T0#13"
10 "T0#16"
14 "T0#2"
17 "T0#22"
20 "T0#25"
21 "T0#26"
22 "T0#27"
25 "T0#3"
26 "T0#30"
27 "T0#31"
28 "T0#32"
29 "T0#33"
30 "T0#34"
32 "T0#36"
34 "T0#38"
35 "T0#39"
36 "T0#4"
38 "T0#41"
39 "T0#42"
45 "T0#48"
50 "T0#52"
54 "T0#56"
56 "T0#58"
58 "T0#6"
61 "T0#62"
64 "T0#7"
65 "T0#8"
66 "T0#9"
67 "T0+bb01"
68 "T0+bb01#1"
70 "T0+bb01#3"
71 "T0+bb01#4"
72 "T0+bb01#5"
75 "T0+bb02#1"
76 "T0+bb02#2"
77 "T0+bb02#3"
83 "T2#102"
88 "T2#107"
91 "T2#11"
98 "T2#116"
99 "T2#117"
103 "T2#120"
105 "T2#122"
107 "T2#124"
109 "T2#126"
110 "T2#127"
112 "T2#129"
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 3

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" "SEV BB" 2
"routes.txt" "route_short_name" "SEV BB" 3
"routes.txt" "route_short_name" "SEV BB" 4
route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"25-49B-j26-1" 684 "49B" "49B"
stop_too_far_from_shape_using_user_distance WARNING 1

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

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.
302151 "23-95B-j26-1.2.R" "41.T0.23-95B-j26-1.2.R" 5018729 "at:49:531:0:2" "Blumengärten Hirschstetten" [48.23604556,16.472681080000005] 125.02368715604132
big_gap_in_service INFO 345

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.

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

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.
"T0#11" "2026-03-04" "2026-05-04" 60
"T0#18" "2026-03-09" "2026-07-14" 126
"T0#20" "2026-04-17" "2026-08-11" 115
"T0#29" "2026-04-17" "2026-05-08" 20
"T0#29" "2026-07-03" "2026-09-07" 65
"T0#44" "2026-05-13" "2026-09-21" 130
"T0#45" "2026-06-12" "2026-08-31" 79
"T0#47" "2026-03-27" "2026-10-27" 213
"T0#61" "2026-03-27" "2026-09-07" 163
"T0+bb01#2" "2026-03-20" "2026-04-10" 20
"T0+bb01#2" "2026-04-17" "2026-05-08" 20
"T0+bb01#2" "2026-07-03" "2026-09-11" 69
"T0+bb02" "2026-04-16" "2026-05-11" 24
"T0+bb02" "2026-07-02" "2026-09-07" 66
"T2" "2026-05-02" "2026-06-27" 55
"T2#101" "2026-02-21" "2026-07-04" 132
"T2#104" "2026-05-09" "2026-09-26" 139
"T2#105" "2026-06-13" "2026-09-05" 83
"T2#106" "2026-03-21" "2026-10-31" 223
"T2#113" "2026-04-18" "2026-08-22" 125
"T2#115" "2026-01-10" "2026-03-07" 55
"T2#12" "2026-02-28" "2026-06-27" 118
"T2#13" "2026-03-14" "2026-04-11" 27
"T2#13" "2026-05-09" "2026-05-30" 20
"T2#132" "2026-03-21" "2026-09-05" 167
"T2#15" "2026-03-21" "2026-04-11" 20
"T2#23" "2026-04-18" "2026-08-01" 104
"T2#31" "2026-05-02" "2026-06-27" 55
"T2#33" "2026-04-18" "2026-08-01" 104
"T2#4" "2026-03-14" "2026-04-11" 27
"T2#4" "2026-04-11" "2026-05-02" 20
"T2#46" "2026-02-28" "2026-06-27" 118
"T2#54" "2026-06-27" "2026-08-08" 41
"T2#56" "2026-01-24" "2026-05-30" 125
"T2#56" "2026-05-30" "2026-09-12" 104
"T2#58" "2026-03-21" "2026-04-11" 20
"T2#60" "2026-02-28" "2026-05-02" 62
"T2#66" "2026-03-07" "2026-07-18" 132
"T2#68" "2026-04-18" "2026-08-22" 125
"T2#70" "2026-03-21" "2026-04-11" 20
"T2#73" "2026-03-21" "2026-04-11" 20
"T2#73" "2026-04-18" "2026-05-09" 20
"T2#73" "2026-06-27" "2026-09-12" 76
"T2#80" "2026-06-13" "2026-09-05" 83
"T2#85" "2026-03-21" "2026-04-11" 20
"T2#96" "2026-02-14" "2026-05-16" 90
"T2#99" "2026-01-24" "2026-08-29" 216
"T3" "2026-05-03" "2026-06-28" 55
"T3#106" "2026-04-19" "2026-08-15" 117
"T3#108" "2026-01-11" "2026-03-01" 48