BDMS-388 Create a standard set of PointIDs that can be used to test the frontend

[ksmuczynski]

BDMS-388 Create a standard set of PointIDs that can be used to test the frontend

Why

This PR addresses the following problem / context:

• This PR addresses the need to establish a consistent set of PointIDs that can be utilized for manual testing and demonstrations of frontend functionalities.

How

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

• A SQL query was written to select 5 random PointIDs from the NMAquifer legacy system that met the following criteria:

  • Location records must have SiteDate populated. The final dataset should contain 2 records with WL_Continuous = true and 3 records with WL_Continuous = false.
  • Owner info must have values for last name, first name, a physical address OR a mailing address , one phone number
  • WellData should have HoleDepth, WellDepth, CasingDiameter, Status, CurrentUse, and MonitoringStatus populated
  • WaterLevels must have at least 10 records and MeasuringAgency=NMBGMR

Notes

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

• Bullet points here

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

[jirhiker]

I really like the programmatic approach. Do all of these pointids also exist in Ocotillo?

[chasetmartin]

I really like the programmatic approach. Do all of these pointids also exist in Ocotillo?

Agreed. And yes I just looked they all exist in Ocotillo Staging

[chasetmartin]

Nice work. Hoping for confirmation from folks on whether this file should live in the repo and be merged in, or should we document these in a different spot?

[jacob-a-brown]

While WL_Continuous is a field that should indicate the existence of continuous water levels for that well, it may not have been maintained; we should confirm in the continuous water level tables that they're there.