Canal closures

Independent. Built from Canal & River Trust's own published notices, with no affiliation to or endorsement by the Trust.

The archive / Data

Download the data

Regenerated nightly. Read the method page first โ€” several columns are deliberately blank where no honest figure exists.

FileWhat it contains
cadence.csvUpdates and the longest silence on each closure.
causes.csvClosure-days by cause.
closures.csvOne row per closure, with every field the archive holds.
denominators.csvWaterway lengths and asset counts, and their licence.
durations.csvHow many closures fall in each duration band.
mapping.csvOne row per notice and each waterway it names.
open_ended.csvClosures with no published reopening date, longest first.
pre-migration.csvNotices still open on migration day, one row per update.
regions.csvClosures and closure-days by CRT region.
waterways.csvClosures and median duration by waterway.

Reading the files

Cadence
How often CRT added an update to a notice in its lifetime. A notice carried over in the migration can show an artificially low cadence, because only its later updates survive.
Longest silence
The longest gap either between two updates, or between the last update and the reopening date. For a closure still shut it is measured to today. A long silence on an open closure is the finding, so it has its own column.
Defensible duration
The days between a closure's start and its reopening date, counted only where the dates allow it. A cancelled notice, or one whose reopening precedes its start, has none and is in no total.
Mapping
One row per notice and each waterway it names. A notice that names two canals is two rows; nothing is lost to a joined display string.

Column dictionary: closures.csv

ColumnMeaning
idCRT's notice identifier (UUIDv7, which carries its creation time).
titleThe notice's published title.
waterwayThe waterway string as CRT filed it; one notice can name two.
waterwaysThat string split on commas, separated by semicolons.
regionCRT's region field.
causeCause read from the notice prose, never from a CRT field.
assetThe asset the cause affected, read from the prose.
reasonCRT's own reason field, kept separate from the cause.
plannedTrue when CRT's programme id marks scheduled maintenance.
statusStill shut, Scheduled or Reopened, judged against the build day.
partialTrue for a restriction rather than a full navigation closure.
startStart date, ISO format.
endPublished reopening date, blank where none is published.
daysFull duration in days; blank where none is defensible.
days_archiveDays inside the archive window, from May 2025.
season_daysDays inside the 15 March to 31 October cruising season.
planned_daysAnnounced length of a closure that has not started.
extentThe locks or bridges the closure sat between, where recorded.

The pre-migration file

CRT migrated to its current notice system on 1 May 2025 and carried over only the notices still open; completed ones were not. CRT's own notices link to a spreadsheet as the pre-migration history, and that link is live while the file returns HTTP 404.

pre-migration.csv is a copy recovered from the Internet Archive. It is not a history of earlier closures: it holds the notices still open on migration day, one row per update. It is read separately and never added to a closure figure.

Licences

Closure notices are Canal & River Trust's own published notices, reproduced with attribution to the Trust. They remain the Trust's copyright.

Waterway lengths and asset counts in denominators.csv come from CRT's ArcGIS open data. Their licence is stated three incompatible ways โ€” data.gov.uk lists it as Other (Non-Commercial), the portal metadata says CC-BY-SA, and an Ordnance Survey End User Licence is referenced. They are published here under the strictest reading: non-commercial use, attribution to Canal & River Trust, and no warranty. Anything derived from them carries the same terms.

Method and limits ยท The network