Search
  1. Home
  2. Belgium Feeds
  3. dewaterbus-gtfs
  4. Source Data Validation Report

dewaterbus-gtfs — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T19:09:54Z,
for the dataset file:///shared/dewaterbus-gtfs_4b59639b.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
AddTransit
Publisher URL:
https://addtransit.com
Feed Email:
N/A
Feed Language:
Dutch
Feed Start Date:
2019-01-02
Feed End Date:
2026-01-01

Files included

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

Counts

  • Agencies: 1
  • Blocks: 6
  • Routes: 2
  • Shapes: 4
  • Stops: 13
  • Trips: 223

Specification Compliance report

151 notices reported (123 errors, 26 warnings, 2 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 123

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

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

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
222 "1" "1" 76 "318" "3" "1" "20250721"
222 "1" "1" 2 "109" "1" "1" "20220801"
76 "318" "3" 2 "109" "1" "1" "20250721"
2 "109" "1" 186 "429" "3" "1" "20250721"
186 "429" "3" 113 "355" "1" "1" "20250721"
113 "355" "1" 77 "319" "3" "1" "20250721"
77 "319" "3" 3 "110" "1" "1" "20250721"
3 "110" "1" 187 "430" "3" "1" "20250721"
187 "430" "3" 114 "356" "1" "1" "20250721"
114 "356" "1" 78 "320" "3" "1" "20250721"
78 "320" "3" 4 "111" "1" "1" "20250721"
4 "111" "1" 188 "431" "3" "1" "20250721"
188 "431" "3" 115 "357" "1" "1" "20250721"
115 "357" "1" 79 "321" "3" "1" "20250721"
79 "321" "3" 5 "112" "1" "1" "20250721"
5 "112" "1" 189 "432" "3" "1" "20250721"
189 "432" "3" 116 "358" "1" "1" "20250721"
116 "358" "1" 80 "322" "3" "1" "20250721"
80 "322" "3" 6 "113" "1" "1" "20250721"
6 "113" "1" 190 "433" "3" "1" "20250721"
190 "433" "3" 117 "359" "1" "1" "20250721"
117 "359" "1" 81 "323" "3" "1" "20250721"
119 "361" "1" 191 "434" "3" "2" "20250721"
82 "324" "3" 9 "116" "1" "2" "20250721"
9 "116" "1" 192 "435" "3" "2" "20250721"
192 "435" "3" 120 "362" "1" "2" "20250721"
120 "362" "1" 83 "325" "3" "2" "20250721"
83 "325" "3" 10 "117" "1" "2" "20250721"
10 "117" "1" 193 "436" "3" "2" "20250721"
193 "436" "3" 121 "363" "1" "2" "20250721"
121 "363" "1" 84 "326" "3" "2" "20250721"
84 "326" "3" 11 "118" "1" "2" "20250721"
11 "118" "1" 194 "437" "3" "2" "20250721"
194 "437" "3" 223 "2" "1" "2" "20250721"
223 "2" "1" 85 "327" "3" "2" "20250721"
85 "327" "3" 224 "3" "1" "2" "20250721"
195 "438" "3" 12 "119" "1" "2" "20250721"
195 "438" "3" 122 "365" "1" "2" "20250721"
122 "365" "1" 86 "328" "3" "2" "20250721"
86 "328" "3" 13 "120" "1" "2" "20250721"
13 "120" "1" 196 "439" "3" "2" "20250721"
196 "439" "3" 123 "366" "1" "2" "20250721"
123 "366" "1" 87 "329" "3" "2" "20250721"
125 "368" "1" 197 "440" "3" "3" "20250721"
88 "330" "3" 16 "123" "1" "3" "20250721"
16 "123" "1" 198 "441" "3" "3" "20250721"
198 "441" "3" 126 "369" "1" "3" "20250721"
126 "369" "1" 89 "331" "3" "3" "20250721"
89 "331" "3" 17 "124" "1" "3" "20250721"
17 "124" "1" 199 "442" "3" "3" "20250721"
expired_calendar WARNING 9

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 "7"
3 "8"
4 "9"
5 "10"
6 "11"
7 "12"
8 "1"
9 "2"
10 "3"
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 "20260323" "20260101" "20260330"
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
missing_recommended_field WARNING 7

missing_recommended_field

A recommended field is missing.

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

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.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
"fare_attributes.txt" 5 "agency_id"
"fare_attributes.txt" 6 "agency_id"
"fare_attributes.txt" 7 "agency_id"
"fare_attributes.txt" 8 "agency_id"
stop_without_stop_time WARNING 5

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.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
3 "10" "Hoogmolendijk"
4 "11" "Brug Houtlaan Wijnegem"
12 "7" "Havenhuis"
13 "8" "Fietsbrug IJzerlaan"
14 "9" "Brug Azijn"
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.
"20260323" "20220703" "20260101"
unused_shape WARNING 2

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"2" 2
"37" 50
transfer_distance_above_2_km INFO 2

transfer_distance_above_2_km

The transfer distance from stop to stop in transfers.txt is larger than 2 km.

You can see more about this notice here.

csvRowNumber (?) The row number from `transfers.txt` for the faulty entry. fromStopId (?) The ID of the stop in `from_stop_id`. toStopId (?) The ID of the stop in `to_stop_id`. distanceKm (?) The distance between the two stops in km.
2 "3" "2" 3.6578686090365986
3 "3" "1" 9.93194158873623