From cd38c00e732b2a66c99ce35cfee694754dcf8870 Mon Sep 17 00:00:00 2001 From: jakeross Date: Sat, 22 Aug 2026 15:47:31 -0700 Subject: [PATCH] docs(ogc): describe actively_monitored_wells as all-groups BDMS-974 drops the "group name = 'water level network'" predicate from ogc_actively_monitored_wells, so the layer now covers currently-monitored wells in any group. The published prose still described the old filter and would have shipped wrong the moment that migration ran. The collection description now keys the layer on the monitoring status alone, and says what the join actually produces: a well in several groups appears once per group. That last point matters enough to repeat at field level -- the id column is no longer unique within the collection, which is the kind of thing a client discovers by having its keyed-by-id map silently drop rows. group_name loses its claim that it is always the Water Level Network. Keywords drop water-level-network for monitoring-status. Co-Authored-By: Claude Opus 5 --- core/ogc-field-descriptions.yml | 11 +++++++++-- core/pygeoapi-config-internal.yml | 17 +++++++++-------- core/pygeoapi-config.yml | 17 +++++++++-------- 3 files changed, 27 insertions(+), 18 deletions(-) diff --git a/core/ogc-field-descriptions.yml b/core/ogc-field-descriptions.yml index 2c83681f..c335f6f4 100644 --- a/core/ogc-field-descriptions.yml +++ b/core/ogc-field-descriptions.yml @@ -281,6 +281,12 @@ water_well_summary: x-ogc-unitLang: QUDT actively_monitored_wells: + id: + title: Feature ID + description: >- + Identifier of the well. Not unique within this collection: a well that + belongs to several monitoring groups appears once per group, and every + one of those features carries the same well id. elevation_method: title: Elevation method description: >- @@ -321,8 +327,9 @@ actively_monitored_wells: group_name: title: Network name description: >- - Name of the monitoring network the well belongs to. Always the Water - Level Network in this collection. + Name of the monitoring group this feature's membership is for. A well + belonging to several groups appears once per group, each feature naming + a different one. group_type: title: Network type description: Kind of grouping the network record represents. diff --git a/core/pygeoapi-config-internal.yml b/core/pygeoapi-config-internal.yml index 578bc8da..bf3ac246 100644 --- a/core/pygeoapi-config-internal.yml +++ b/core/pygeoapi-config-internal.yml @@ -361,15 +361,16 @@ resources: title: Actively Monitored Wells description: >- The wells being measured today, rather than every well ever recorded. - A well appears here only if it belongs to the Water Level Network - group and its most recent monitoring-status entry reads "Currently - monitored"; the summary statistics attached to each one are the same - water-level figures published in water_well_summary. Use it to see the - live monitoring network -- where measurements are still being - collected, and where coverage is thin. + A well appears here when its most recent monitoring-status entry reads + "Currently monitored", whichever monitoring group it belongs to; the + summary statistics attached to each one are the same water-level + figures published in water_well_summary. A well in several groups + appears once per group, so the same well id can occur on more than one + feature. Use it to see the live monitoring network -- where + measurements are still being collected, and where coverage is thin. keywords: [ - water-wells, monitoring, water-level-network, actively-monitored, - monitoring-network, groundwater-level + water-wells, monitoring, actively-monitored, monitoring-network, + monitoring-status, groundwater-level ] extents: spatial: diff --git a/core/pygeoapi-config.yml b/core/pygeoapi-config.yml index 4dbf0c97..3ad364ee 100644 --- a/core/pygeoapi-config.yml +++ b/core/pygeoapi-config.yml @@ -271,15 +271,16 @@ resources: title: Actively Monitored Wells description: >- The wells being measured today, rather than every well ever recorded. - A well appears here only if it belongs to the Water Level Network - group and its most recent monitoring-status entry reads "Currently - monitored"; the summary statistics attached to each one are the same - water-level figures published in water_well_summary. Use it to see the - live monitoring network -- where measurements are still being - collected, and where coverage is thin. + A well appears here when its most recent monitoring-status entry reads + "Currently monitored", whichever monitoring group it belongs to; the + summary statistics attached to each one are the same water-level + figures published in water_well_summary. A well in several groups + appears once per group, so the same well id can occur on more than one + feature. Use it to see the live monitoring network -- where + measurements are still being collected, and where coverage is thin. keywords: [ - water-wells, monitoring, water-level-network, actively-monitored, - monitoring-network, groundwater-level + water-wells, monitoring, actively-monitored, monitoring-network, + monitoring-status, groundwater-level ] extents: spatial: