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

Additional text about pH and specificConductance values #63

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kcawley
Copy link
Contributor

@kcawley kcawley commented Aug 1, 2023

This is additional text to clarify which pH and specific conductance values that users should prioritize using.

@cklunch
Copy link
Collaborator

cklunch commented Aug 11, 2023

@kcawley Thanks! I think it would be helpful to add a sentence at the start of the new text:

"A few measurements in this data product are also available via the in-stream sensors, most notably specific conductance and pH. Given the potential for additional uncertainty arising from sample collection/processing, shipping, and storage time prior to analysis, we strongly recommend using the in-situ Water quality (DP1.20288.001) sensor data whenever possible, particularly for specificConductance and pH. Alternatively..."

Otherwise it sounds a little bit like we're recommending no one use the water chemistry data product at all.

And I'm wondering if it would be good to use different language in the groundwater chemistry QSG - does the water quality data really reflect what's happening in the groundwater? Or is there a groundwater sensor we can point them to?

@cklunch
Copy link
Collaborator

cklunch commented Feb 23, 2024

@kcawley Checking in on this stale PR - any thoughts? Thanks!

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

Successfully merging this pull request may close these issues.

2 participants