-
just moving this here
https://github.com/internetofwater/geoconnex.us/issues/113
First stab going here
https://github.com/internetofwater/gwtc2021-workshop
-
NLDI is now returning active and discontinued gages and we need to parse those for active only.
-
Here are some examples of function to retrieve NDLI data:
- **nldi.get_basin()** - returns a geodataframe with a polygon geometry
- **nldi.get_flowlines()** - returns a geodataframe with a polyli…
-
Query/pull characteristics from NLDI (not sure how that will be formatted in NLDI yet, under progress)
-
Users would like to retrieve WQP data and OPTIONALLY any additional USGS continuous data that in the specific area of interest and possible also nearby data (within additional buffer zone) or upstream…
-
Define a common `Feature` model for use across the project (crawler client, server, other tools).
Can be a 'vanilla' `dataclass`, a pydantic model, or an ORM model. All sides of the workflow shou…
-
Other NHD functions work for this comid. This fails, and so this site is not mapped to salt use.
```
comids_ut
-
I found two USGS stations where the area of the NLDI's delineated basin geometry is way off compared to the total drainage area provided by NHD. The IDs are:
- USGS-01446000: NLDI area is 307 sqkm …
-
It appears that a significant portion of the functions in the Liquibase configuration are deprecated. @dblodgett-usgs @gzt5142 (cc: @EthanGrahn) I would be interested to know if we can prune what is n…
-
For Frank the Farmer, Tony once mentioned this point and I love it. I'm not sure how hard it would be to code. Suppose the NLDI API returns 200 WaDE POD sites. Each site has its priority date from its…