Wessex Water Event Duration Monitoring 2024

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, but a more accurate picture of storm overflow operations than is currently available in the National Storm Overflow Hub (NSOH). The Coast and Rivers Watch web map and National Storm Overflow Hub feed facilitates the near-real time reporting of storm overflow start and stop data. The built-in quality assurance function automatically removes flatlines and data spikes and is calibrated on a site-by-site basis to achieve the best level of accuracy. Further in-depth assurance continues after publishing on the web map and the data set is updated and published on a monthly basis 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 Regulation Requests, EIRRs）定期申领的数据。通过提供部署于暴雨溢流口的事件时长监测设备的运行历史数据，我们认为可减少针对本地化暴雨溢流性能数据的申领需求。相较于环境署（Environment Agency, EA）的年度回报数据，本数据集的颗粒度更低但更新频率更高，且相比当前国家暴雨溢流枢纽（National Storm Overflow Hub, NSOH）中的公开数据，能更精准地呈现暴雨溢流的实际运行情况。 海岸与河流监控（Coast and Rivers Watch）网页地图及国家暴雨溢流枢纽数据源支持暴雨溢流启停数据的近实时上报。内置的质量保障功能可自动剔除恒定值数据与异常尖峰，并针对每个站点单独校准以达到最优精度水准。在网页地图发布数据后，仍会开展进一步的深度质量核查；本数据集将按月完成更新与发布。 ### 数据集架构 注：若字段为非必填项，数据集中仍会保留对应列以符合架构要求，但可能无实际数据： 1. SiteId*：暴雨溢流口的唯一标识，字符串类型，示例：ABC123 2. SiteName：暴雨溢流口的命名，字符串类型，示例：Paris Road SO 3. ReceivingWatercourse：溢流排放所指向的水道名称，字符串类型，示例：River Trent 4. PermitReference：所用许可证的编号，字符串类型，示例：abc123 5. OutfallLatitude*：溢流口的纬度，浮点型，示例：52.21691 6. OutfallLongitude*：溢流口的经度，浮点型，示例：0.14449 7. IsBathingWater：标识该溢流口是否排入指定游泳水域，布尔型，示例：True 8. BathingWaterName：该溢流口排放汇入的游泳水域名称，字符串类型，示例：Spring Lake 9. EventId：分配给本次事件的唯一标识符，字符串类型，示例：abc123 10. EventStart*：监测设备判定排放开始的日期与时间，日期时间类型，格式遵循YYYY-MM-DDTHH:mm:ss 11. EventEnd*：监测设备判定排放结束的日期与时间，日期时间类型，格式遵循YYYY-MM-DDTHH:mm:ss 12. Duration：事件启停之间的时长，时长类型，示例：P3Y6M4DT12H30M5S 13. EventVerified：标识该事件在发布时是否已完成核查，布尔型，示例：False * 为必填字段；** 需采用标准取值。