Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Week of 5/22/2023 #851

Open
9 tasks done
glenncampagna opened this issue May 22, 2023 · 3 comments
Open
9 tasks done

Week of 5/22/2023 #851

glenncampagna opened this issue May 22, 2023 · 3 comments
Assignees

Comments

@glenncampagna
Copy link
Collaborator

glenncampagna commented May 22, 2023

Continued onboarding:

  • can Ella ssh into DEQ2? ssh -p 312 [username]@deq1.bse.vt.edu
    Yes, but she is not part of the allmodelers or harpmodelers groups yet
  • cover CBP vars and cbp-helper script Week of 5/15/2023: Onboarding for Summer 2023 #817 (comment)
  • quick explanation of northern vs. southern rivers in VA
  • Application Design: All data resources must be acccessible via http request.
    • Therefore, for model data, we must pass needed info, like:
      • model version,
      • model PARAMETERS set
      • model sub-version (like vadeq and p532c_sova)
      • model scenario
  • Add and test f-table params in args -- retrieve from online sources linked in Week of 5/15/2023: Onboarding for Summer 2023 #817 (comment)
  • Look over 2023 work plan
  • Explore the regional plan data in VAHydro
  • Use adminid search page to view available bundle types (and use this page to get IDs for the next bullet)
  • Try pulling in localities or systems via REST, using admincode or adminreg feature IDs of the system/locality
@glenncampagna
Copy link
Collaborator Author

Pulling systems/facilities via REST

To fetch a single registration using admin feature IDs we used getAdminregFeature()

bburgGolfCourse <- getAdminregFeature(inputs = list(
  adminid = '68732',
  bundle = 'registration'), base_url = site)

or to pull a list of facilities by specifying the ftype (capped at 100 it looks like):

facilities <- getAdminregFeature(inputs = list(
  ftype = 'vdeq_vwuds',
  bundle = 'registration'), base_url = site)

@EllaF21
Copy link
Contributor

EllaF21 commented May 26, 2023

Brainstorms of flagging specific reaches for potential issues:

  • Map that shows areas in region that are above/below certain percentile that represents potential drought in future
  • F tables that show amount of water that will be withdrawn from an area vs the available volume of water in the area
  • Comparison of water use projections bar graph vs general streamflow
  • Flag specific areas for drastic population growth predictions
  • When viewing each region's specific drought plan we discovered certain metrics that each region and locality uses to determine drought watch, warning or emergency. These metrics are different per locality and region but we could try to generalize them.
    - % of normal precipitation per month
    - Groundwater well levels
    - Reservoir levels
    - Specific gauges measured for specific percentiles
    - Specific river flows equal to or greater then values during winter/spring and summer/fall

(We plan to add any other ideas here in the future)

@megpritch
Copy link
Collaborator

Progress on Pulling Facilities & Localities Using REST

Facilities_REST_Test.docx

So far we are able to pull features for multiple types of coverages, but as far as actual data goes, we can only associate a few values with facilities. These values include:

  • wd_current_mgy
  • consumption
  • wsp2020_2040_mgy
  • wsp2020_2020_mgy
  • gw_frac
  • sw_frac
  • gw_current_mgy
  • sw_current_mgy

Our various REST methods and previews of the outputs can be seen in the word doc above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants