Skip to content

BDMS 389: historic well notes#291

Merged
jirhiker merged 4 commits into
well-inventory-csvfrom
bdms-389-historic-well-notes
Dec 11, 2025
Merged

BDMS 389: historic well notes#291
jirhiker merged 4 commits into
well-inventory-csvfrom
bdms-389-historic-well-notes

Conversation

@jacob-a-brown

Copy link
Copy Markdown
Contributor

Why

This PR addresses the following problem / context:

  • The Gherkin file well-inventory-csv.feature has a field for historic water levels. Since this isn't a measured water level, it may just be from the memory of the owner, it shouldn't go into the observation table. It should go into the polymorphic notes table instead with a note_type of Historic.

How

Implementation summary - the following was changed / added / removed:

  • If historic_depth_to_water_ft is defined a note is added with the content being f"Historic depth to water: {model.historic_depth_to_water_ft} ft".
    • This field doesn't indicate how/where the historic depth to water is from so I can't put that in the note. Should there be another field to indicate that? Or does this note suffice?

Notes

Any special considerations, workarounds, or follow-up work to note?

  • Use bullet points here

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
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@jirhiker

jirhiker commented Dec 11, 2025

Copy link
Copy Markdown
Member

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

@chasetmartin

chasetmartin commented Dec 11, 2025

Copy link
Copy Markdown
Collaborator

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:
"Sometimes it’s what is in the drilling log
Sometimes it’s what the person just says to you"

I'll check with a couple others to make sure.

@TylerAdamMartinez TylerAdamMartinez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@chasetmartin

Copy link
Copy Markdown
Collaborator

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.
@jacob-a-brown

Copy link
Copy Markdown
Contributor Author

Thoughts on the new note? Should I change the wording?

@jirhiker jirhiker merged commit 9bf285f into well-inventory-csv Dec 11, 2025
4 checks passed
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.

4 participants