Search
  1. Home
  2. Zimbabwe Feeds
  3. harare-city-shuttle
  4. Source Data Validation Report

harare-city-shuttle — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-17T18:02:01Z,
for the dataset file:///shared/harare-city-shuttle_0cb5792f.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
WhereIsMyTransport
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2017-09-20
Feed End Date:
2020-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. fare_attributes.txt
  4. fare_rules.txt
  5. feed_info.txt
  6. frequencies.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 5
  • Shapes: 5
  • Stops: 16
  • Trips: 10

Specification Compliance report

15 notices reported (5 errors, 10 warnings, 0 infos)

Notice Code Severity Total
invalid_integer ERROR 5

invalid_integer

A field cannot be parsed as an integer.

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.
"fare_attributes.txt" 2 "transfers" "4294967295"
"fare_attributes.txt" 3 "transfers" "4294967295"
"fare_attributes.txt" 4 "transfers" "4294967295"
"fare_attributes.txt" 5 "transfers" "4294967295"
"fare_attributes.txt" 6 "transfers" "4294967295"
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 "service_0001"
3 "service_0002"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260417" "20201231" "20260424"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
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" "20180604" "20190703"
unexpected_enum_value WARNING 5

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. fieldName (?) The name of the field where the error occurred. fieldValue (?) Faulty value.
"routes.txt" 2 "route_type" 1501
"routes.txt" 3 "route_type" 1501
"routes.txt" 4 "route_type" 1501
"routes.txt" 5 "route_type" 1501
"routes.txt" 6 "route_type" 1501