Home
Ghana Feeds
smartertravel
Source Data Validation Report

smartertravel — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-03T17:40:06Z,
for the dataset file:///shared/smartertravel_9191f71c.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

bus
- website: https://www.smartertravel.com/transportation-kumasi-taxi-train-bus-airport-tips/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2019-01-01 to 2019-12-31 (?) 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
frequencies.txt
routes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 27
Shapes: 0
Stops: 401
Trips: 48

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

Frequencies

Specification Compliance report

1226 notices reported (0 errors, 1226 warnings, 0 infos)

Notice Code Severity Total

expired_calendar WARNING 1

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	"allweek"

fast_travel_between_consecutive_stops WARNING 11

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.
23	"20_Outbound"	"20"	313.80402088481566	5.230067014746927	355	1	"409"	"stop_409"	"00:00:17"	356	2	"368"	"stop_368"	"00:00:17"
7	"13_Inbound"	"13"	182.7028402301314	3.0450473371688567	53	2	"37"	"stop_37"	"00:27:12"	54	3	"83"	"stop_83"	"00:27:12"
5	"12_Inbound"	"12"	108.59066691412576	5.308877049135037	39	1	"127"	"stop_127"	"00:00:17"	40	3	"185"	"stop_185"	"00:03:13"
27	"22_Outbound"	"22"	144.11220515175992	2.401870085862665	390	1	"54"	"stop_54"	"00:00:17"	391	2	"61"	"stop_61"	"00:00:17"
27	"22_Outbound"	"22"	266.83968347696634	0.3706106714957866	392	3	"62"	"stop_62"	"00:10:59"	393	4	"63"	"stop_63"	"00:11:04"
19	"19_Outbound"	"19"	123.25403351747113	1.3694892613052347	234	6	"417"	"stop_417"	"00:10:52"	235	7	"418"	"stop_418"	"00:11:32"
19	"19_Outbound"	"19"	227.7549825880098	5.061221835289107	239	11	"422"	"stop_422"	"00:25:47"	240	12	"409"	"stop_409"	"00:27:07"
21	"2_Outbound"	"2"	192.1701334423105	5.6049622254007225	310	15	"16"	"stop_16"	"00:54:13"	311	16	"18"	"stop_18"	"00:55:58"
39	"29_Outbound"	"29"	251.64023403226747	1.7475016252240796	569	1	"26"	"stop_26"	"00:00:17"	570	2	"54"	"stop_54"	"00:00:42"
41	"30_Outbound"	"30"	145.5363604240662	2.42560600706777	602	1	"383"	"stop_383"	"00:00:17"	603	2	"344"	"stop_344"	"00:00:17"
20	"2_Inbound"	"2"	102.73104854230267	5.136552427115134	280	25	"18"	"stop_18"	"01:47:57"	281	26	"17"	"stop_17"	"01:50:57"

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 753

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

Only the first 50 of 753 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	"1_Inbound"	1
3	"1_Inbound"	2
4	"1_Inbound"	3
5	"1_Inbound"	4
6	"1_Inbound"	5
7	"1_Inbound"	6
8	"1_Inbound"	7
9	"1_Inbound"	8
10	"10_Inbound"	1
11	"10_Inbound"	2
12	"10_Inbound"	3
13	"10_Inbound"	4
14	"10_Inbound"	5
15	"10_Inbound"	6
16	"10_Inbound"	7
17	"10_Inbound"	8
18	"10_Inbound"	9
19	"10_Inbound"	10
20	"10_Inbound"	11
21	"10_Inbound"	12
22	"10_Inbound"	13
23	"10_Inbound"	14
24	"10_Inbound"	15
25	"10_Outbound"	1
26	"10_Outbound"	2
27	"10_Outbound"	3
28	"10_Outbound"	4
29	"10_Outbound"	5
30	"10_Outbound"	6
31	"10_Outbound"	7
32	"10_Outbound"	8
33	"10_Outbound"	9
34	"10_Outbound"	10
35	"10_Outbound"	11
36	"10_Outbound"	12
37	"10_Outbound"	13
38	"10_Outbound"	14
39	"12_Inbound"	1
40	"12_Inbound"	3
41	"12_Inbound"	4
42	"12_Inbound"	6
43	"12_Inbound"	7
44	"12_Inbound"	8
45	"12_Inbound"	9
46	"12_Outbound"	1
47	"12_Outbound"	2
48	"12_Outbound"	3
49	"12_Outbound"	4
50	"12_Outbound"	11
51	"12_Outbound"	12

mixed_case_recommended_field WARNING 405

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.

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

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"agency.txt"	"agency_name"	"bus"	2
"routes.txt"	"route_long_name"	"12AL"	9
"routes.txt"	"route_long_name"	"14AL"	12
"routes.txt"	"route_long_name"	"16AL"	15
"stops.txt"	"stop_name"	"stop_1"	2
"stops.txt"	"stop_name"	"stop_2"	3
"stops.txt"	"stop_name"	"stop_3"	4
"stops.txt"	"stop_name"	"stop_4"	5
"stops.txt"	"stop_name"	"stop_5"	6
"stops.txt"	"stop_name"	"stop_6"	7
"stops.txt"	"stop_name"	"stop_7"	8
"stops.txt"	"stop_name"	"stop_8"	9
"stops.txt"	"stop_name"	"stop_9"	10
"stops.txt"	"stop_name"	"stop_10"	11
"stops.txt"	"stop_name"	"stop_11"	12
"stops.txt"	"stop_name"	"stop_12"	13
"stops.txt"	"stop_name"	"stop_13"	14
"stops.txt"	"stop_name"	"stop_14"	15
"stops.txt"	"stop_name"	"stop_15"	16
"stops.txt"	"stop_name"	"stop_16"	17
"stops.txt"	"stop_name"	"stop_17"	18
"stops.txt"	"stop_name"	"stop_18"	19
"stops.txt"	"stop_name"	"stop_19"	20
"stops.txt"	"stop_name"	"stop_20"	21
"stops.txt"	"stop_name"	"stop_21"	22
"stops.txt"	"stop_name"	"stop_22"	23
"stops.txt"	"stop_name"	"stop_23"	24
"stops.txt"	"stop_name"	"stop_24"	25
"stops.txt"	"stop_name"	"stop_25"	26
"stops.txt"	"stop_name"	"stop_26"	27
"stops.txt"	"stop_name"	"stop_27"	28
"stops.txt"	"stop_name"	"stop_28"	29
"stops.txt"	"stop_name"	"stop_29"	30
"stops.txt"	"stop_name"	"stop_30"	31
"stops.txt"	"stop_name"	"stop_31"	32
"stops.txt"	"stop_name"	"stop_32"	33
"stops.txt"	"stop_name"	"stop_33"	34
"stops.txt"	"stop_name"	"stop_34"	35
"stops.txt"	"stop_name"	"stop_35"	36
"stops.txt"	"stop_name"	"stop_36"	37
"stops.txt"	"stop_name"	"stop_37"	38
"stops.txt"	"stop_name"	"stop_38"	39
"stops.txt"	"stop_name"	"stop_39"	40
"stops.txt"	"stop_name"	"stop_40"	41
"stops.txt"	"stop_name"	"stop_41"	42
"stops.txt"	"stop_name"	"stop_42"	43
"stops.txt"	"stop_name"	"stop_43"	44
"stops.txt"	"stop_name"	"stop_44"	45
"stops.txt"	"stop_name"	"stop_45"	46
"stops.txt"	"stop_name"	"stop_46"	47

stop_without_stop_time WARNING 54

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
2	"1"	"stop_1"
22	"21"	"stop_21"
23	"22"	"stop_22"
32	"31"	"stop_31"
33	"32"	"stop_32"
34	"33"	"stop_33"
35	"34"	"stop_34"
36	"35"	"stop_35"
37	"36"	"stop_36"
43	"42"	"stop_42"
44	"43"	"stop_43"
46	"45"	"stop_45"
52	"51"	"stop_51"
53	"52"	"stop_52"
80	"79"	"stop_79"
94	"99"	"stop_99"
96	"101"	"stop_101"
97	"102"	"stop_102"
98	"103"	"stop_103"
99	"104"	"stop_104"
104	"109"	"stop_109"
105	"110"	"stop_110"
114	"125"	"stop_125"
118	"129"	"stop_129"
122	"133"	"stop_133"
158	"169"	"stop_169"
160	"171"	"stop_171"
161	"172"	"stop_172"
162	"173"	"stop_173"
163	"174"	"stop_174"
164	"175"	"stop_175"
165	"176"	"stop_176"
168	"179"	"stop_179"
175	"188"	"stop_188"
197	"212"	"stop_212"
198	"213"	"stop_213"
199	"214"	"stop_214"
200	"215"	"stop_215"
201	"216"	"stop_216"
202	"217"	"stop_217"
223	"238"	"stop_238"
249	"264"	"stop_264"
279	"294"	"stop_294"
295	"310"	"stop_310"
296	"311"	"stop_311"
299	"314"	"stop_314"
311	"326"	"stop_326"
381	"400"	"stop_400"
382	"401"	"stop_401"
383	"402"	"stop_402"

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.
"20260403"	"20190101"	"20191231"