https://github.com/alexlipp/sewage-map
Realtime mapping the downstream impact of Combined Sewage Overflow discharge events in non-tidal rivers across England and Wales
Science Score: 26.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
○CITATION.cff file
-
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Academic email domains
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (10.1%) to scientific vocabulary
Keywords
Repository
Realtime mapping the downstream impact of Combined Sewage Overflow discharge events in non-tidal rivers across England and Wales
Basic Info
Statistics
- Stars: 16
- Watchers: 5
- Forks: 1
- Open Issues: 6
- Releases: 0
Topics
Metadata Files
README.md
Mapping Sewage Discharges into rivers across England <!--and Wales-->
Realtime mapping the downstream impact of Combined Sewage Overflow discharge events in non-tidal rivers across England <!--and Wales-->. This repository provides the back-end for www.sewagemap.co.uk. The repository for the front-end is available at github.com/JonnyDawe/UK-Sewage-Map/.
This was developed by Alex Lipp, Jonny Dawe and Sudhir Balaji. Please feel free to raise an issue above or contact us directly.
Installation
This script relies on the POOPy package which I (Alex) have created to allow easy interaction with Water Company Event Duration Monitoring (EDM) APIs, and analysis of the data. This is freely available at: github.com/AlexLipp/POOPy.
Usage
The core script is update_all.py which is called automatically every 15 minutes. This function, using POOPy functions, calculates a geoJSON file which contains the downstream impact of all active or recently active CSO spills for which EDM data is available. These are automatically uploaded to the Amazon Web Services bucket which hosts them. The data is then fronted using the CloudFront delivery service. The files are read by the www.sewagemap.co.uk front-end which visualises them.
The script update.py is included for legacy purposes, and updates only Thames Water data (but is needed for the historical data provided only by Thames).
Output data
The live downstream impact of Combined Sewage Overflow (CSO) discharge events is freely available under a CC-BY-SA license. The links in the table below give access to the data as .geoJSON files. The data are updated automatically every ~20 minutes (but the URL remains the same). These can be incorporated into your own projects, web-apps, or GIS projects but please attribute the source as www.sewagemap.co.uk. It'd be wonderful to hear about any projects you use this data in, so please do reach out to me to let me know, or if I can be of any assistance.
The Downstream impacted reaches is a LineString feature-collection simply showing the sections of a river which are downstream of current discharges, and optionally those in the last 48 hrs. These are the brown lines on www.sewagemap.co.uk.
The Downstream Impact Information is a Point feature-collection which details at each pixel in a drainage network 1) the number of discharges upstream, 2) the number of discharges per unit of upstream area, and 3) A list of the names (or permit numbers) of discharging CSOs upstream.
Water Company Data Table
Disclaimer: whilst we make every effort to ensure the accuracy of this data, we cannot guarantee it and it should not be used for any critical purposes.
Water Company | Downstream Impacted Reaches | Downstream Impact Information | Last Updated --- | --- | --- | --- Thames Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp Anglian Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp United Utilities | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp Southern Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp Northumbrian Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp Severn Trent Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp Wessex Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp Yorkshire Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp SouthWest Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp <!--Welsh Water | Current spills; Spills within last 48hrs | Current spills; Spills within last 48hrs | Timestamp-->
Thames Water historical data
We process the Thames Water historical spill API which records stop/start event histories and store it as a table of discharge events with attributes suc as StartTime and Duration. You can get this data (in .json format) for discharge events here and for offline periods here.
Source data
The live EDM data which we use to map downstream sectons is sourced, in England, from the Stream Storm Overflow Data Hub which is provided under a CC-BY license. Each individual water company maintain's an individual API which you can access from the given link. <!-- For Wales, we use data presented on the WelshWater Storm Overflow map.-->
Owner
- Name: Alex Lipp
- Login: AlexLipp
- Kind: user
- Location: Oxford, UK
- Company: Merton College, Oxford
- Website: https://alexlipp.github.io/
- Twitter: alexglipp
- Repositories: 4
- Profile: https://github.com/AlexLipp
Earth & Environmental Scientist at the University of Oxford
GitHub Events
Total
- Issues event: 3
- Watch event: 4
- Issue comment event: 4
- Push event: 6
- Pull request event: 4
- Fork event: 1
- Create event: 2
Last Year
- Issues event: 3
- Watch event: 4
- Issue comment event: 4
- Push event: 6
- Pull request event: 4
- Fork event: 1
- Create event: 2
Issues and Pull Requests
Last synced: 6 months ago
All Time
- Total issues: 2
- Total pull requests: 2
- Average time to close issues: about 19 hours
- Average time to close pull requests: less than a minute
- Total issue authors: 2
- Total pull request authors: 1
- Average comments per issue: 1.5
- Average comments per pull request: 0.0
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 2
- Pull requests: 2
- Average time to close issues: about 19 hours
- Average time to close pull requests: less than a minute
- Issue authors: 2
- Pull request authors: 1
- Average comments per issue: 1.5
- Average comments per pull request: 0.0
- Merged pull requests: 2
- Bot issues: 0
- Bot pull requests: 0
Top Authors
Issue Authors
- jpsingleton (1)
- alanedney-lgtm (1)
Pull Request Authors
- AlexLipp (2)
Top Labels
Issue Labels
Pull Request Labels
Dependencies
- adaptivekde ==1.1.1
- cfgv ==3.3.1
- distlib ==0.3.6
- filelock ==3.8.0
- future ==0.18.2
- identify ==2.5.6
- joblib ==1.2.0
- nodeenv ==1.7.0
- pre-commit ==2.20.0
- pygem ==2.0.0
- scikit-learn ==1.2.2
- toml ==0.10.2
- virtualenv ==20.16.5
- geojson *
- landlab *
- matplotlib *
- numpy *
- osgeo *
- pandas *
- requests *
