Home
South Africa Feeds
stellenbosch
Source Data Validation Report

stellenbosch — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-17T18:24:17Z,
for the dataset file:///shared/stellenbosch_6a1f0cff.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: Service Window:
2023-03-08 to 2023-07-08 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 0
Blocks: 0
Routes: 4
Shapes: 44
Stops: 226
Trips: 44

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Headsigns

Specification Compliance report

20 notices reported (1 errors, 19 warnings, 0 infos)

Notice Code Severity Total

missing_required_field ERROR 1

missing_required_field

A required field is missing.

The given field has no value in some input row, even though values are required.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"agency.txt"	2	"agency_url"

expired_calendar WARNING 2

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.
2	"weekdays"
3	"saturdays"

fast_travel_between_consecutive_stops WARNING 2

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.
7	"37987277"	"route2"	198.37630074217506	0.7714633917751252	221	4	"28117"	"2_Paradyskloof Rd"	"06:34:01"	222	5	"28112"	"5_Paradyskloof Rd"	"06:34:15"
7	"37987277"	"route2"	188.15923281185877	1.1498619782946924	227	10	"28110"	"16_Webersvallei Rd"	"06:41:11"	228	11	"28107"	"1_Pajaro Avenue"	"06:41:33"

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 4

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"	"route1"	2
"routes.txt"	"route_short_name"	"route2"	3
"routes.txt"	"route_short_name"	"route3"	4
"routes.txt"	"route_short_name"	"route4"	5

stops_match_shape_out_of_order WARNING 9

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.
18	"37873689"	"37873689"	56	"37852510"	"10_Long str"	[-33.90705100000001,18.851568000000004]	55	"28490"	"1_Stellenvista Estate"	[-33.907824,18.852437]
27	"37926835"	"37926835"	141	"28306"	"14_Torrey Str"	[-33.981187,18.853057]	140	"28110"	"16_Webersvallei Rd"	[-33.969159839967105,18.844144556025885]
41	"38018131"	"38018131"	267	"28345"	"37_Stellenbosch Square"	[-33.977242000000004,18.841509000000002]	266	"28050"	"2_La Clemence Retirement Village"	[-33.97144139722903,18.843252687981785]
23	"37910126"	"37910126"	110	"37890904"	"2_Bergzicht Rank"	[-33.93231,18.858733000000004]	109	"28566"	"29_Bergzicht Rank"	[-33.932124,18.860154]
2	"37896054"	"37896054"	92	"28428"	"2_VGK Church"	[-33.91624300000001,18.857831]	91	"28477"	"6_Lang Rd"	[-33.91535,18.857737]
17	"37872348"	"37872348"	43	"37890904"	"2_Bergzicht Rank"	[-33.93231,18.858733000000004]	42	"28531"	"2_Bergzicht Rank"	[-33.93201899999999,18.858613000000002]
3	"37852918"	"37852918"	7	"28494"	"1_North End"	[-33.912927999999994,18.854843999999996]	6	"28493"	"17_Lang str"	[-33.91240500000001,18.85658]
28	"37930508"	"37930508"	165	"28328"	"18_Torrey Str"	[-33.980887,18.853971000000005]	164	"37847432"	"24_Webersvallei Rd"	[-33.97898500000001,18.850461000000003]
7	"37987277"	"37987277"	221	"28117"	"2_Paradyskloof Rd"	[-33.959571,18.853539]	220	"37841704"	"4_Paradyskloof Rd"	[-33.963894,18.858425]

trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20260417"	"20230308"	"20230707"