Hafren Dyfrdwy Event Duration Monitoring 2025

The overall objective of this use case is to pro-actively publish data that is regularly requested via Environmental Information Regulation Requests (EIRRs). By supplying historic data about the activity of event duration monitors situated at storm overflows, we believe that we can reduce requests for localised storm overflow performance data. The data will detail a lower level of granularity and higher update frequency than the Environment Agency (EA) Annual returns. Schema: Field Name DESCRIPTION DATA TYPE EXAMPLE DATA SiteId * Unique Identity of the Storm Overflow String ABC123 SiteName The name given to the Storm Overflow String Paris Road SO ReceivingWatercourse The name of the watercourse into which a discharge is directed String River Trent PermitReference The reference for the permit used String abc123 OutfallLatitude * Latitude of the outfall Float 52.21691 OutfallLongitude * Longitude of the outfall Float 0.14449 IsBathingWater An indication of whether the outfall meets a designated bathing water Boolean True BathingWaterName The name of the bathing water into which the outfall discharges String Spring Lake EventId The unique identifier assigned to this event String abc123 EventStart * Date and Time that the monitor indicated a discharge had started DateTime YYYY-MM-DDTHH:mm:ss EventEnd * Date and Time that the monitor indicated a discharge had ended DateTime YYYY-MM-DDTHH:mm:ss Duration The length of time between the event’s start and stop time Duration P3Y6M4DT12H30M5S EventVerified An indication of whether this event is verified at the time of it being published Boolean False *Mandatory **Requires a standard value