leppott / ContDataQC

Quality control checks on continuous data. Example data is from a HOBO data logger with 30 minute intervals.
https://leppott.github.io/ContDataQC/
MIT License
20 stars 10 forks source link

water level vs sensor depth vs gage height #100

Closed JenStamp closed 3 years ago

JenStamp commented 3 years ago

Hi Erik, We’re running into the water level/sensor depth/gage height issue again. We are working with files that come with one of the following three labels for water level - • Sensor Depth = HOBOware output if they don’t enter a reference water level • Water Level = HOBOware output if they enter a reference water level • GageHeight ft - from USGS NWIS site

At this point it’s a fairly even mix of people generating sensor depth vs. water level outputs. Knowing what we know now, it’s probably important to keep that distinction.

Right now, we have the following two entries in the config file: sensor depth and gage height.

Possible options – • Enter ‘Water Level’ into the config file as a third option • If we want to stick with two possible entries vs entering ‘Water Level’ into the config file as a third option, I’d vote for changing GageHeight to WaterLevel. If people use USGS gage data, their focus will be on discharge, not GageHeight. o If we still want to carry GageHeight through (probably a good idea), perhaps you can have it change ‘GageHeight’ to ‘WaterLevel’ when R reformats the file coming in from NWIS. Then we'll be able to stick with two possible entries.

Thanks for your help on this!

leppott commented 3 years ago

Works now with v2.0.5.9056
https://github.com/leppott/ContDataQC/commit/78bfe009e12ef8cacb7810227013835931619ad3

leppott commented 3 years ago
leppott commented 3 years ago

Update formatHobo() to use water level (v2.0.5.9057).

leppott commented 3 years ago

Water level not showing in output file.

Fixed in v2.0.5.9060. https://github.com/leppott/ContDataQC/commit/8f22dab4bbcabdc052fe965f50d3f6f26e8e0f06