Commit f99ccea
committed
docs(ogc): record the null measuring-point height default
water_well_summary, depth_to_water_trend_wells and
water_elevation_wells layers all substitute zero for a missing
measuring-point height, treating the measuring point as ground
surface. That has been in the SQL since those views were written
(COALESCE(measuring_point_height, 0)), but nothing said whether zero
was the intended default or an accident. BDMS-974 surfaced the
question and deferred it here rather than change the views on a guess.
Cris Morton and Ethan Mamer confirmed on 2026-08-26 that zero (ground
surface) is the right default, so the views are correct as written and
there is no code change to make. What was missing was the record: the
next person to read that substitution would ask the same question, and
without an answer on file the safe-looking move is to exclude those
rows, which would silently drop wells from three published layers.
The doc keeps the consequence visible rather than acting on it. Wells
with no recorded measuring point are less certain than the rest and
nothing in the output says so. Adding a flag column would touch three
view definitions and the field descriptions for a subset nobody has
sized yet, so the decision records the condition for revisiting it
instead.
Refs BDMS-9801 parent d3f5dcb commit f99ccea
1 file changed
Lines changed: 26 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
| 1 | + | |
| 2 | + | |
| 3 | + | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
| 11 | + | |
| 12 | + | |
| 13 | + | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
| 17 | + | |
| 18 | + | |
| 19 | + | |
| 20 | + | |
| 21 | + | |
| 22 | + | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
0 commit comments