wouldnt it be great

I need to communicate with USGS to get a live connection of the gages layer indexed to the NLDI. This will allow for the tool to visualize upstream/downstream queries for gages and basins.

See here for contribution process:
https://github.com/ACWI-SSWD/nldi-crawler#contributing

This will require a geojson endpoint from which the entire layer can be fetched without iteration. Feature Server has max return of 1000. I will explore a pygeoapi service that can republish.

@pattersonla provided a pretty cool example for visualizing gage period of record from NCSCO. Based on more detailed POR, would require pulling all available data from CDEC and USGS where available

NLDI integration (#5 ) requires persistent identifiers. Need to come up with CA-wide identifier scheme. Can use https://geoconnex.us as resolver

CA Gage Workflow.pptx

• Groundwater-Dependent Ecosystems

1. I've uploaded a giant powerpoint (not really a presentation, but includes many slides from our recent TAC presentation). This can serve as the discussion point and framework for our next steps.
2. we should chat about this soon.
3. good news! we have a bit more breathing room, so I can pay attention more fully. I'm still probably the bottleneck with data, but maybe we have have parallel efforts running.

@vlzimmer , your side of the house needs to decide what gage prioritization framework to use.

If we have enough lead time, we can implement as an R Plumber API that you could pass a geojson file of a proposed gage network to and return the resulting prioritization.

don't we all!
@ksonda please fix the things

It appears that CDEC has changed its station metadata url pattern from

http://cdec.water.ca.gov/cgi-progs/staMeta?station_id=ARD

to

http://cdec.water.ca.gov/dynamicapp/staMeta?station_id=ARD

@vlzimmer whoever the custodian of https://gispublic.waterboards.ca.gov/portalserver/rest/services/Hosted/StreamGages_20210114/FeatureServer/0 is should change that

A great use case for persistent identifiers :P