BDMS 389: historic well notes#291
Conversation
The historic water level doesn't really go into the water level table because it's not a measurement, but it's good ot note. Since it is recorded it's being put into Historic notes for a well
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Please follow up with @chasetmartin and Marissa to verify your assumption about the historic water level. This seems reasonable; but " Since this isn't a measured water level, it may just be from the memory of the owner," I can't tell if that is your reasoning or based on feedback from AMP |
One AMP member: I'll check with a couple others to make sure. |
Confirmed during the Ocotillo Coordination meeting with AMP. @jacob-a-brown Also noted during the meeting that WellData.DepthSource from NM Aquifer refers to both well depth and historic depth to water. |
AMP indicated that the well depth source is the same as the historic depth to water source.
|
Thoughts on the new note? Should I change the wording? |
Why
This PR addresses the following problem / context:
observationtable. It should go into the polymorphic notes table instead with anote_typeofHistoric.How
Implementation summary - the following was changed / added / removed:
historic_depth_to_water_ftis defined a note is added with the content beingf"Historic depth to water: {model.historic_depth_to_water_ft} ft".Notes
Any special considerations, workarounds, or follow-up work to note?