haackwell's People
haackwell's Issues
New issue
This is issue text, describe what should be done.
Run geopandas_advanced.ipynb tutorial for well data to play with rasterstats
I think it's useful to make a copy of @EMayorga 's tutorial, but for well data, and see if we can get it to run. Then push it back to the tutorial materials.
-
Get the notebook running with well points and a grid (grace or chirps)
-
Explore some more rasterstats at the end of the notebook
-
Clean up the notebook to be useful and clear to our data patron/ well data stakeholders
-
Push back to the tutorial Github repository
Map pattern of polluted, damaged, stolen, etc.
This will be for the "human-caused" issues. Will need another one for hydrologic-caused issues.
Extract CHIRPS (or other precip raster) to study region
Similar to #8, clip our precipitation raster to the same bounding region for potential further hydrologic analysis.
Create a list of keywords for STATUS messages to better organize well data
In addition to the well functional binary (YES/NO), we also have status messages, e.g.,
Status:Not functional|Quantity:Dry|Quality:Soft
Low yield|Normally operational
Dry pan|No operation in the dry season
No- broken down. Well polluted
No- broken down. WATER TABLE HAS DROPED
So we need to figure out some of these keywords in order to make better categories of well failure conditions.
Set up environment for running project notebooks
Options
- Create YAML file, to be sourced from the terminal before starting Jupyter notebooks, or
- Create list of dependencies to be installed through conda.
Tasks:
- List dependencies.
- Create YAML file.
- Test environment.yaml
- Document guide for both methods of setting up environment.
Extract breakdown year for a subset of the non-functional wells
There are ~1500 wells that have "Breakdown year:[YEAR]" in the STATUS
message, e.g.,
WELL_ID | LAT_DD | LONG_DD | FUNC | STATUS | COD_FCN | COD_QTY | COD_RESRCE | ADM1 | ADM2 | ACTIVITY | COUNTRY | WATERSRC | WATERTECH | INSTALLED | MGMT | PAY | SOURCE | RPT_DATE |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
268998 | -10.71619084 | 36.02310299 | No | Status:Not functional|Breakdown Year:1999|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Communal standpipe | 1992 | Pay per bucket | Plan | 18/10/2009 | ||
282411 | -10.71532037 | 36.02752107 | No | Status:Not functional|Breakdown Year:2003|Quantity:Insufficient|Quality:Soft | 0 | 1 | 0 | Morogoro | Morogoro Rural | TZ | Dam | Gravity Communal standpipe | 2000 | Never pay | WA | 11/6/08 | ||
269003 | -10.71391058 | 35.9747595 | No | Status:Not functional|Breakdown Year:2004|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Dam | 1990 | Pay per bucket | Plan | 18/10/2009 | ||
269001 | -10.71294497 | 35.96916631 | No | Status:Not functional|Breakdown Year:2004|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Dam | 1970 | Pay per bucket | Plan | 18/10/2009 | ||
268081 | -10.71233895 | 36.031057 | No | Status:Not functional|Breakdown Year:2005|Reason Not Functioning:Also dam broken|Quantity:Dry|Quality:Soft | 0 | 1 | 0 | Arusha | Monduli | TZ | Dam | Gravity Communal standpipe | 1993 | Never pay | WA | 15/06/2008 | ||
269067 | -10.71037391 | 35.9691566 | No | Status:Not functional|Breakdown Year:2005|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Communal standpipe | 1970 | Never pay | Plan | 18/10/2009 | ||
269070 | -10.71022388 | 35.97219087 | No | Status:Not functional|Breakdown Year:2005|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Communal standpipe | 1970 | Never pay | Plan | 18/10/2009 | ||
269014 | -10.7097919 | 36.03288676 | No | Status:Not functional|Breakdown Year:2005|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Hand pump | 1970 | Pay per bucket | Plan | 18/10/2009 | ||
269069 | -10.70841953 | 35.97085284 | No | Status:Not functional|Breakdown Year:2005|Reason Not Functioning:Dam has dried up|Quantity:Dry|Quality:Soft | 0 | 0 | 1 | Coast Region | Kisarawe | TZ | Dam | Gravity Communal standpipe | 1970 | Never pay | Plan | 18/10/2009 |
This is useful information because it tells us the actual year where the well became nonfunctional, and we could use this date instead of the report date, which is often years later, for trying to pinpoint potential hydrologic causes.
Or, we could use the report date like we do with the rest of the data if we want to be consistent with the rest of the available data. Thoughts?
Extract GRACE data for the region of interest
Take the global GRACE dataset, clip to Tanzania/Uganda bounding box, potentially do some zonal stats based on hydrological units
Remove gravity-fed wells from the well dataset
Right now, we have "wells" that are actually gravity fed, like a spring or a rainwater harvesting operation, e.g.,
WELL_ID | LAT_DD | LONG_DD | FUNC | STATUS | COD_FCN | COD_QTY | COD_RESRCE | ADM1 | ADM2 | ACTIVITY | COUNTRY | WATERSRC | WATERTECH | INSTALLED | MGMT | PAY | SOURCE | RPT_DATE |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
486554 | -0.12982 | 34.456458 | Yes | Functional ( in use) | 1 | 1 | 0 | ksm372 | KE | Rainwater (harvesting) | Gravity | 2005 | Institutional Management | None | Virtual Kenya | 6/6/12 | ||
485707 | -0.109488 | 34.438404 | Yes | Functional ( in use) | 1 | 1 | 0 | ksm367 | KE | Rainwater (harvesting) | Gravity | 2005 | Institutional Management | None | Virtual Kenya | 5/6/12 | ||
486748 | -0.123888 | 34.548462 | Yes | Functional ( in use) | 1 | 1 | 0 | ksm296 | KE | Rainwater (harvesting) | Gravity | 2008 | Institutional Management | 2 KES/20L Jerrican | Virtual Kenya | 25/04/2012 | ||
486747 | -0.123888 | 34.548462 | Yes | Functional ( in use) | 1 | 1 | 0 | ksm296 | KE | Rainwater (harvesting) | Gravity | 2008 | Institutional Management | 2 KES/20L Jerrican | Virtual Kenya | 25/04/2012 |
These have no relation to GRACE data (since GRACE is groundwater), and therefore should be removed.
Drought Indexes
I am using GEE to calculate drought indexes (probably NDDI) from Landsat. I can plot changes in the drought indexes over time in the area of the well.
Clip well data CSV to study area
Should clip it so we only include in the eastern part of Africa.
GRACE location update
Can we delineate precipitation into a wet and dry season for the study area?
Tasks:
- Aggregate precipitation product to monthly precipitation [mm/month].
- Calculate mean monthly precipitation for study time. Can use this to get a general idea of the wet and dry season.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.