← Back to catalogue
Previous version

Water Body & Hydrology

vr.wm-plc-003 · world-p3-water-body-and-hydrology

Rivers, lakes, seas, aquifers and their regimes

World Models Physical world and living systems PHY.PLC.WAT

Bundle → Layer → Finding → Questions Incomplete

3 bundles · 9 layers · 0 findings · 0 questions

hydrography What water bodies exist, where they are and how they connect

waterFeature

rivers, lakes, seas, wetlands and springs as identified features

catchment

drainage areas and their nesting

networkTopology

upstream and downstream connectivity between features and nodes

aquifer

subsurface water bodies, their extent and confinement

regime How much water moves, when, and how variable it is

flowAndLevel

discharge, stage, tide and groundwater level observations

waterBalance

inflow, outflow, storage, recharge and abstraction returns over a period

extremeStatistics

flood and low-flow frequency, return periods and seasonality

quality What the water contains and what state that implies

physicoChemical

sampled determinands, concentrations and methods

biologicalStatus

indicator communities and classified ecological status

Note: Legacy card: layers named, findings and questions never written.

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
standalone-mm
Navigation path
NAV.PHY.PLC.WAT
Domain
PHY.PLC.WAT
Industry
Cross-industry
Tags
waterbodyphy.plc.wat
Also called
P3

What it is Derived, awaiting review

This meta-model describes surface and subsurface water as physical objects and as regimes: rivers, lakes, seas, wetlands and aquifers, the catchments that feed them, the flows and levels they carry through the year, and the measured quality of the water itself.

Note: First sentence of the legacy card introduction.

Why it exists Filled

Rivers, lakes, seas, aquifers and their regimes

Distinguishing features Derived, awaiting review

  • It is its own model because a water body is a connected, moving system whose identity survives changes of level and course, and because the network topology of upstream and downstream relations is the basis for almost every other water question.

What robots and AI may and may not do Missing, in the backlog

Not described yet. This gap is in the card backlog.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Filled

Steward

An ecology commons steward keeps the hydrological register: it delineates bodies and catchments, operates or accredits monitoring, and publishes regimes and status classifications, without holding any claim over the water itself.

Links to other meta-models Filled

references

  • world.terrainAndLandform - catchment boundaries and flow direction derive from the published elevation surface
  • world.subsurfaceAndMineralResource - aquifers are hosted in geological units described there
  • world.soilAndAgriculturalLand - infiltration, runoff and nutrient loading link soil state to water response
  • world.ecosystemAndBiome - aquatic and riparian ecosystems are assessed against the bodies defined here
  • world.naturalPhenomenonAndHazard - flood and drought occurrences are characterized against flow regimes and thresholds
  • world.atmosphereWeatherAndClimate - precipitation and evaporation observations drive the water balance
  • world.waterAndFoodSupply - abstraction, treatment and discharge are described there and reference bodies here
  • world.emissionAndEnvironmentalFlux - abstraction, treatment and discharge are described there and reference bodies here
  • world.physicalInfrastructureNetwork - dams, weirs, canals and levees are engineered structures that modify the regime

imports

  • ogc-hy-features - EXTEND: the hydrologic feature and catchment backbone this model specializes
  • inspire - ALIGN: hydrography theme for cross-register comparability
  • iso-19156-observations-and-measurements - COMPOSE: the observation, procedure and result pattern used by readings and samples
  • ogc-waterml - ALIGN: time series exchange shape for hydrometric feeds

requires

  • vr.wm-blt-003
  • vr.wm-ear-001
  • vr.wm-ear-003
  • vr.wm-ear-004
  • vr.wm-ear-005
  • vr.wm-flw-002
  • vr.wm-liv-006
  • vr.wm-plc-001

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Derived, awaiting review

  • waterBody: an identified body or reach of water; key attributes: identifier, feature type, geometry, permanence (perennial, seasonal, ephemeral), salinity class
  • watershed: a drainage area contributing to an outlet; key attributes: identifier, geometry, area, outlet node reference, parent watershed reference
  • gaugingStation: an installed monitoring point; key attributes: station identifier, location, measured variables, operating period, rating curve reference
  • aquifer: a subsurface unit holding recoverable water; key attributes: identifier, extent, confinement, storativity, recharge estimate

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Derived, awaiting review

  • gaugeReadingRecorded: a station reported a level, discharge or groundwater value for a moment in time
  • floodStageExceeded: an observed level crossed a defined threshold at a station
  • lowFlowThresholdCrossed: flow fell below a stated low-flow reference for a reach
  • waterBodyDelineationRevised: the geometry or identity of a body or catchment was redrawn after new evidence
  • channelCourseChanged: a river changed course, or an avulsion or channel migration was mapped
  • qualitySampleAnalyzed: laboratory results for a sample became available and were attached to the sampling point
  • ecologicalStatusReclassified: the classified status of a body changed after an assessment cycle

Legacy events listed as state transitions.

Hazards and failure modes optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • hydrometricFeedContract: terms for real-time or near-real-time delivery of station readings, including latency, quality flags and outage notice
  • qualityLaboratoryExchangeContract: terms for laboratories submitting analyses, covering method declaration, detection limits and re-analysis
  • transboundaryBasinExchange: terms for exchanging flow and quality data with a neighbouring register for a shared basin
  • abstractionReturnDisclosure: terms under which operators report abstracted and returned volumes at agreed grain
  • publicRiverLevelView: current level, flow and threshold status by station; omits raw sensor diagnostics and provisional unvalidated values
  • catchmentBalanceSummary: inflow, outflow, storage change and recharge per catchment and period; omits point-level observations
  • qualityStatusMap: classified status by water body; omits sample-level results, sampler identity and site coordinates for sensitive points

Context of use required Filled

  • Access to restricted station feeds, sensitive sampling locations or pre-validation data is granted by the steward through S2 access contracts, and reads are logged in S4.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Superseded by a researched world model? Map this legacy card to its successor or retire it.

Machine files

Provenance

legacy MMAS card (world-models v0.2) · legacy

Built from: models/world-p3-water-body-and-hydrology/spec.yaml, models/docs/planet-nature/P3-water-body-and-hydrology.md