United Utilities Event Duration Monitoring 2024

The overall objective of this use case is to proactively publish data that is regularly requested via Environmental Information Requests (EIRs). 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. United Utilities' storm overflow map and the National Storm Overflow Hub for England facilitate the near-real time reporting of storm overflow data that has undergone initial automated validation; this should be viewed as indicative rather than fully verified. This file contains start/stop spill data for 2024, and is a further validated version of the near-real time data from the storm overflow map. The locations shown in the data may differ slightly from the storm overflow map as this represents the location the UU discharge leaves our network. For example, the data location may show the location of discharge to an underground culverted watercourse, whilst the storm overflow map may show the location of the culvert discharge to a watercourse. This location may be remote from the pumping station or treatment works. Watercourses often receive inputs from sources other than storm overflows such as highway drainage, surface water, run off from agricultural land and culverted watercourses. Please be aware that the SiteId field has been updated for 2024. While the underlying sites themselves are unchanged, their identifier values have been revised from the 2023 format. Historically, storm overflow identifiers were not standardised across the industry. Following a request from DEFRA, water and sewerage companies are now adopting a consistent, national format. This standardisation enhances data quality, streamlines reporting, and improves the reliability of cross‑system integrations. The provided lookup table maps the previous identifiers to the new ones, enabling you to migrate any historical data you may hold. If you are not capturing historical data, it is unlikely this change will affect you. Schema (where fields are not mandatory, columns will be present in the dataset to reflect the schema but may not contain data): 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本用例的总体目标是主动发布那些通过环境信息申请（Environmental Information Requests, EIRs）频繁被申请获取的数据。通过提供部署于风暴溢流现场的时长监测设备的运行历史数据，我们认为可有效减少针对局部风暴溢流性能数据的申请需求。 联合公用事业（United Utilities）的风暴溢流地图及英格兰国家风暴溢流枢纽，可对经过初步自动化验证的风暴溢流数据进行近乎实时上报；此类数据仅作参考性数据，而非经完全核验的最终结果。 本文件包含2024年的溢流启停数据，是对风暴溢流地图中近乎实时数据的进一步验证版本。数据中展示的点位可能与风暴溢流地图存在细微差异，因为此处标注的是联合公用事业公司排污口脱离其管网的位置。例如，本数据的点位可能显示排污口通往地下涵管河道的位置，而风暴溢流地图则可能标注该涵管向河道排污的点位。该点位可能远离泵站或污水处理厂。 河道通常还会接收来自风暴溢流以外的其他水源补给，例如公路排水、地表水、农田径流以及涵管河道来水。 请注意，2024年已对SiteId字段进行更新。尽管相关站点本身未发生变化，但其标识符值已从2023年的格式完成修订。长期以来，行业内的风暴溢流标识符并未实现统一标准化。应英国环境、食品与农村事务部（DEFRA）的要求，各水务与污水处理企业目前正采用统一的全国性标识符格式。此项标准化工作可提升数据质量、简化报告流程，并提高跨系统集成的可靠性。 本次提供的对照表可将旧版标识符映射至新版标识符，方便您迁移所持有的任何历史数据。若您未留存历史数据，则此变更不太可能对您造成影响。 数据架构说明（若字段非必填，数据集中仍会包含该列以符合架构要求，但可能不含实际数据）： | 字段名 | 描述 | 数据类型 | 示例数据 | | --- | --- | --- | --- | | SiteId * | 风暴溢流的唯一标识 | 字符串 | ABC123 | | SiteName | 风暴溢流的命名 | 字符串 | 巴黎路溢流点 | | ReceivingWatercourse | 排污所指向的河道名称 | 字符串 | 特伦特河 | | PermitReference | 所用许可证的编号 | 字符串 | abc123 | | OutfallLatitude * | 排污口纬度 | 浮点数 | 52.21691 | | OutfallLongitude * | 排污口经度 | 浮点数 | 0.14449 | | IsBathingWater | 标识排污口是否属于指定沐浴水域 | 布尔值 | True | | BathingWaterName | 排污口排污所进入的沐浴水域名称 | 字符串 | 春湖 | | EventId | 分配给本次事件的唯一标识符 | 字符串 | abc123 | | EventStart * | 监测设备显示排污开始的日期与时间 | 日期时间 | YYYY-MM-DDTHH:mm:ss | | EventEnd * | 监测设备显示排污结束的日期与时间 | 日期时间 | YYYY-MM-DDTHH:mm:ss | | Duration | 事件起止时间的间隔时长 | 时长类型 | P3Y6M4DT12H30M5S | | EventVerified | 发布时该事件是否已完成核验的标识 | 布尔值 | False | * 必填项 ** 需采用标准值