Manual measurements currently has a temporary table structure while we resolve questions related to dtw and waterelevation measurements.
Before dropping cut/hold fields: Should check that DTW below casing values match expected values based on cut/hold
Before dropping Conductivity: Need to move values to field measurements table
Before dropping well name- make sure we feel good about the locationids matching the well names
Before dropping water elevation- See if values follow from dtwbelowcasing and stickup height
Regarding the dtw/water elevation issue:
dtwbelowground is easiest to understand, standard used by USGS, but isn't tied to our measurments very well
dtwbelowcasing is directly tied to what we measure, less transformation needed
waterelevation- can be calculated, needs to be recalculated if we change the waterelevation in the verticalmeasure table
Currently, I like the idea of sticking with dtwbelowcasing and current_stickup_height. The latter could just be a default value and only change after extreme events (well stepped on or driven over, etc.). I think we could also adjust the stickup value to account for the rare cases where ground elevation changed by creating a proxy value that would get you to the correct elevation, with a note indicating why the stickup changed. I think this option does the best to preserve the info we used for our calculations and helps us keep track of site history. This would require changing Pete's variable stickup data to just the values that denote real change
I assume we could create a calculated field with dtwbelowground and waterelevation and or maybe a view
Manual measurements currently has a temporary table structure while we resolve questions related to dtw and waterelevation measurements.
Regarding the dtw/water elevation issue:
Currently, I like the idea of sticking with dtwbelowcasing and current_stickup_height. The latter could just be a default value and only change after extreme events (well stepped on or driven over, etc.). I think we could also adjust the stickup value to account for the rare cases where ground elevation changed by creating a proxy value that would get you to the correct elevation, with a note indicating why the stickup changed. I think this option does the best to preserve the info we used for our calculations and helps us keep track of site history. This would require changing Pete's variable stickup data to just the values that denote real change
I assume we could create a calculated field with dtwbelowground and waterelevation and or maybe a view