Closed Stefankirby closed 1 year ago
Added a conductivity column to the existing readings table available at: https://webmaps.geology.utah.gov/arcgis/rest/services/Groundwater/GWDP_V2/MapServer/12
The column only has data for one site - locationid 139
I would also like this. We need it for four sites, 138, 139, 140, and 141, to provide the data requested by the project funders, National Park Service.
See my logger type add data to layer request for more info on when we have conductivity data for these four wells.
Thanks, @lance-weaver, @marthajensen, and I will discuss what's needed to implement this and get back to you.
Is there any progress on this? I have taken over the project from Stefan Kirby. I'm doing the annual report now and in last year's report we promised the NPS these conductivity AND TEMPERATURE data would be available on our data portal website. Can I give the NPS people a projected completion date? Do you need me to provide the conductivity data for the other three wells and temperature for all four? Thanks.
@LucyJordan
We were discussing this issue this morning. Do you mind sending me the conductivity and temperature data for these wells? Thanks!
@LucyJordan Also, we might need a little clarification on how exactly you'd like this presented in the web interface. Maybe a video chat sometime might be best to explain it?
The conductivity and temperature are fields in the ugsgwp.sde.reading
table. Temperature is populated, but is doesn't look like there are data in the conductivity field yet.
The Levelogger LTC and InSitu AquaTroll Transducers both measure Conductivity, so wells with id 138, 139, 140, and 141 all should have conductivity measurements. I will need to pull these from the raw data and add them to the database.
Courthouse Wash and Sevenmile Canyon Logger Log
Log of Logger Types installed in wells
Last saved by Lucy Jordan on 12/20/2022 10:45:00 AM
138 CHWENT
Solinst levelogger 3-14-2012 to 10-16-2019;
Solinst levelogger LTC 10-16-2019 to current
139 CHWNVJ
Solinst levelogger 3-14-2012 to 10-16-2019;
Solinst levelogger LTC 10-16-2019 to 5-28-2021;
logger malfunction 5-28-2021 to 10-7-2021;
Solinst levelogger 10-7-2021 to 10-18-2022;
In Situ AquaTroll 10-18-2022 to current
140 SMCENT Solinst levelogger 10-27-2020 to 7-19-2022; InSitu AquaTroll 7-19- 2022 to current
141 SMCNVJ
Solinst levelogger 10-27-2020 to 7-19-2022;
InSitu AquaTroll 7-19- 2022 to current
Update on this enhancement:
Last Thursday, @inkenbrandt sent me the conductivity data for these wells. The data will be added to the 'conductivity' field in the "reading" table. This addition of data is a little more complex than usual because I have to add the data using both the readingdate and the locationid fields to update the data in the table.
@LucyJordan Also, we might need a little clarification on how exactly you'd like this presented in the web interface. Maybe a video chat sometime might be best to explain it?
@LucyJordan, just making sure you saw this comment from Lance.
Yes, sorry. Should have done it today but I got busy. I'm unavailable for video conf until Friday or can do next week. If conductivity and temperature will be added, I think we'll need a separate time series graph below the water level graph for those two parameters. Conductivity on the primary x axis and temperature on the secondary. If only conductivity will be added, you could just put it on the water level graph using the secondary axis.
@lance-weaver See thread above. All four of these wells have water level, temperature, and conductivity data. 138 384149109400902 CHWENT 139 384149109400901 CHWNVJ 140 384022109400401 SMCENT 141 384022109400402 SMCNVJ @marthajensen said the conductivity data is in the 'conductivity' field in the "reading" table. I don't have access to those tables, but I'm betting temperature is there too. Conductivity is in units of microSiemens per centimeter, abbreviated uS/cm. If you have the ability to use Greek letters, replace the u with small Greek letter mu. Temperature is in Celsius.
Add has_cond
field to ugsgwp.sde.ugs_ngwmn_monitoring_locations
to designate if the well/spring has conductivity readings that need to be shown.
@nmpayne
We are very close to having this wrapped up. I think all that has to be done to leverage the new field Nate added and publish the resulting graphs on the main page.
Lance has submitted this to me for final review. I'm hoping to get to this review today or early next week.
Great! Thanks for the update.
It would be awesome if we had this up and running before March 30. I am submitting a final report to National Park Service detailing our data for these wells and if I could point users to the data portal, they will be very pleased. Lucy
On Thu, Mar 16, 2023, 09:06 Paul @.***> wrote:
Great! Thanks for the update.
— Reply to this email directly, view it on GitHub https://github.com/UGS-GIO/groundwaterMonPortal/issues/5#issuecomment-1472160351, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4CSYXXMRLOCXDDMLAKGNCLW4MT7LANCNFSM4MVVSYQA . You are receiving this because you were mentioned.Message ID: @.***>
This feature has been pushed to the live web application. The conductivity chart shows up beneath the groundwater elevation chart.
So awesome. Thanks everyone! Just to double check, the two Sevenmile Canyon wells will be able to accept conductivity data once we upload it, correct? We have conductivity data but it has not been QCed for upload yet.
We need the ability to store and graph conductivity data at the courthouse wash site.
This would take the form of an additional numeric field in the database. That could then be simply graphed.