You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How to handle when an MP or other feature is missing/delete/disappears from VAHydro? See email titled: How to handle missing MP on live? - Doswell WTP Facility & North Anna River Intake
We need to establish a workflow to follow for retrieving props/ts data from one feature on a VAHydro site and pushing it to another.
Long-term Solution:
option 1: rewrite dh_get_dh_propts_tree in r script
option 2: View and Rscript combo
- Make view that runs dh_get_dh_propts_tree dhmodule function and simply returns pid
- R script uses pid to pull all fields using REST get_props/ts function
- Reset all PID values so they don't override anything when pushed
- Pushes updates to VAHydro via rest
- Note: RB and JM are leaning towards this option as it leverages a dhmodule function that already exists
Test Node for dh_get_dh_propts_tree is at dh/node/65
We'll want this completed before the May 2020 QA Cycle when we set the 5 Year Average Property (wd_current_mgy).
The text was updated successfully, but these errors were encountered:
@jmineva -- did we essentially sort this out? If so, can you leave a link to the most up to date code you have for ding this and then close this? Thanks!
PROBLEM
How to handle when an MP or other feature is missing/delete/disappears from VAHydro? See email titled: How to handle missing MP on live? - Doswell WTP Facility & North Anna River Intake
We need to establish a workflow to follow for retrieving props/ts data from one feature on a VAHydro site and pushing it to another.
Long-term Solution:
- Make view that runs dh_get_dh_propts_tree dhmodule function and simply returns pid
- R script uses pid to pull all fields using REST get_props/ts function
- Reset all PID values so they don't override anything when pushed
- Pushes updates to VAHydro via rest
- Note: RB and JM are leaning towards this option as it leverages a dhmodule function that already exists
We'll want this completed before the May 2020 QA Cycle when we set the 5 Year Average Property (wd_current_mgy).
The text was updated successfully, but these errors were encountered: