reservoirs.earth logo
Reservoirs.EARTH
← Back to map

Transparency

Methodology

This page covers two methodologies:

Part 1

Data Methodology

reservoirs.earth is built on official government data. This section explains exactly where the data comes from, how it is processed, and what its limitations are.

Fill levels & capacity

Reservoir data

Reservoir fill levels are sourced directly from official national hydrological bulletins published by each country's water authority. Data is updated weekly and covers all reservoirs above a minimum capacity threshold (typically 5 hm³).

Spain

Spanish data comes from the MITECO Boletín Hidrológico Semanal, published by the Ministry for Ecological Transition and the Demographic Challenge. MITECO aggregates readings from the 16 hydrographic confederations covering the entire Iberian Peninsula, Canary Islands and Balearic Islands.

The source database (BD-Embalses) covers 401 reservoirs with weekly readings going back to 1988. We download the full database weekly and recompute all derived metrics.

SourceMITECO BD-Embalses (Access database)
Update frequencyWeekly (published every Tuesday)
Coverage401 reservoirs · 16 hydrographic confederations
Historical depth1988 – present
LicenceOpen government data (datos.gob.es)

United States

US data is drawn from four official federal and state government sources, combined into a unified dataset covering 41 states and over 540 reservoirs. All data is published by US government agencies and is in the public domain. reservoirs.earth does not modify the underlying measurements — it only aggregates, normalises units, and presents them visually.

Capacity is estimated as the highest observed storage reading over a two-year rolling window, since no single federal catalogue provides certified usable-capacity figures for all reservoirs. Fill percentage is computed as current storage divided by that estimated capacity.

California

SourceCDEC — California Data Exchange Center (CA Dept. of Water Resources)
ParameterSensor 15 — reservoir storage (acre-feet), daily
Coverage32 reservoirs
URLcdec.water.ca.gov

Oregon · Idaho · Montana

SourceBOR RISE — Bureau of Reclamation Integrated System Explorer
ParameterStorage timeseries (acre-feet), daily
Coverage58 reservoirs
URLdata.usbr.gov/rise/api

All other states — primary

SourceUSGS NWIS — National Water Information System (US Geological Survey)
Parameter00054 — reservoir storage (acre-feet), daily values
Site typeLK — Lake/reservoir
URLwaterservices.usgs.gov/nwis/dv

All other states — supplements

Source 1USACE CWMS — US Army Corps of Engineers Water Management System
Source 2BOR RISE — Bureau of Reclamation (for non-OR/ID/MT states with BOR dams)

USACE CWMS covers 16 districts across the country and provides .Stor. timeseries in m³ (converted to acre-feet). BOR RISE supplements states where BOR operates dams not captured by USGS. Both sources are deduplicated against the primary USGS dataset.

States without data — and why

Nine states appear on the map but have no reservoir storage data. This is not a limitation of reservoirs.earth — it reflects the absence of public machine-readable storage gauges in federal systems for those states:

Delaware · Maine · Michigan · New Hampshire · New Jersey · Rhode Island · Vermont

No USGS parameterCd=00054 gauges exist for any reservoir in these states. USACE CWMS districts NAE (New England), NAN (New York) and LRE (Detroit) were also scanned — no .Stor. timeseries found. State-level agencies (NJ DEP, etc.) hold this data but do not expose it through public machine-readable APIs.

Alaska · Hawaii

No significant reservoirs tracked in any of the three federal databases (USGS NWIS, USACE CWMS, BOR RISE).

Utah and Nevada show partial data: their main reservoirs (Lake Powell, Lake Mead, Flaming Gorge) are operated by the Bureau of Reclamation and are subject to BOR RISE API rate limits during bulk data collection. Their readings are marked as pending and will be completed in a subsequent update.

Data responsibility disclaimer

All US reservoir data shown on reservoirs.earth originates from official US federal government agencies (USGS, USACE, BOR, CA DWR). reservoirs.earth is an independent project that collects, processes and aggregates this public-domain data solely to make it more visually accessible. We are not affiliated with any of these agencies, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. For authoritative figures, always consult the original agency source directly.

Unit conversion1 acre-foot = 0.001233482 MCM (all values stored in MCM)
Update frequencyRebuilt on demand via build script (not live)
Historical depth2-year rolling window from build date
LicencesUS federal data is public domain (17 U.S.C. § 105)

Portugal

Portuguese data is sourced from SNIRH (Sistema Nacional de Informação de Recursos Hídricos), operated by APA (Agência Portuguesa do Ambiente), the national water authority under the Ministry for Environment and Climate Action. SNIRH publishes weekly reservoir storage bulletins for all 8 hydrographic regions (Regiões Hidrográficas RH1–RH8) covering the continental territory.

Data is retrieved by parsing the structured HTML tables published on the SNIRH web portal. No dedicated public REST API exists; all extraction is done against the official published HTML. Capacity figures and coordinates come from the official SNIRH Características das Albufeiras register and APA public records. reservoirs.earth does not modify any of the underlying measurements — it only aggregates, normalises and presents them visually.

SourceSNIRH / APA — Agência Portuguesa do Ambiente
URLsnirh.apambiente.pt
Update frequencyWeekly
Coverage~50 reservoirs · 11 river basins · 8 hydrographic regions
Historical depthSeasonal (basin-level fill % from APA Boletim de Armazenamento)
Unitshm³ (= MCM, 1:1 conversion)
LicenceOpen government data (dados.gov.pt)

Data responsibility disclaimer

All Portuguese reservoir data shown on reservoirs.earth originates from SNIRH / APA, an official Portuguese Government agency. reservoirs.earth is an independent project that collects, processes and aggregates this publicly available data solely to make it more visually accessible. We are not affiliated with APA or any Portuguese government body, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. For authoritative figures, always consult SNIRH directly.

Brazil

Brazilian data is sourced from ONS (Operador Nacional do Sistema Elétrico), the Brazilian electricity grid operator that monitors hydropower reservoir levels nationwide as part of its grid-balancing mandate. ONS publishes daily hydrological data as open CSV files on its public S3 bucket.

Reservoir metadata

SourceONS — RESERVATORIOS.csv (S3 open data)
FieldsName, total capacity (hm³), useful capacity, basin, river, subsystem, coordinates
URLons-aws-prod-opendata.s3.amazonaws.com/dataset/reservatorio/RESERVATORIOS.csv

Daily readings

SourceONS — DADOS_HIDROLOGICOS_RES_{year}.csv (S3 open data)
Key fieldval_volumeutilcon — useful storage as fill percentage (%)
UpdatesThree times daily: 09:15, 14:15 and 17:00 BRT

Only reservoirs with a total capacity ≥ 200 hm³ are included, to exclude small run-of-river plants that do not contribute meaningfully to storage. Reservoirs are grouped by ONS subsystem (Norte, Nordeste, Sudeste/Centro-Oeste, Sul) and by Brazilian state. reservoirs.earth does not modify any of the underlying measurements.

Update frequencyDaily (rebuilt on demand via build script)
Coverage~270 reservoirs ≥ 200 hm³ · 4 ONS subsystems
Historical depth2024 – present
Unitshm³ (= MCM, 1:1 conversion)
LicenceOpen data — dados.ons.org.br

Data responsibility disclaimer

All Brazilian reservoir data shown on reservoirs.earth originates from ONS, an official Brazilian federal body. reservoirs.earth is an independent project that collects, processes and aggregates this publicly available data solely to make it more visually accessible. We are not affiliated with ONS or any Brazilian government body, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. For authoritative figures, always consult dados.ons.org.br directly.

India

Indian data is sourced from two official government portals that together cover the country's major storage reservoirs:

Primary — CWC Weekly Storage Bulletin

SourceCWC — Central Water Commission (Ministry of Jal Shakti)
URLcwc.gov.in/reservoir-level-storage-bulletin
Coverage~166 major reservoirs · 5 regions · ≈71% of India's national live storage capacity
RegionsNorthern · Eastern · Western · Central · Southern
UnitsBCM (1 BCM = 1,000 MCM)
FrequencyWeekly

The CWC bulletin and its portal are only accessible from Indian IP addresses. Outside India, the build script uses the data.gov.in CWC API as a globally accessible fallback (free registration required; resource ID 65bc6185-0f45-4932-b86b-6cbb03d39e54).

Supplement — Maharashtra WRD Portal

SourceMaharashtra Water Resources Department (WRD)
URLmahahp.gov.in / wrd.maharashtra.gov.in
CoverageMajor Maharashtra dams not individually tracked by CWC
UnitsMCM
FrequencyDaily

Also only accessible from Indian IP addresses. Data is retrieved via ASP.NET UpdatePanel async postback.

Historical depthWeekly snapshots from build date
LicenceOpen government data (data.gov.in — NOGI licence)

Data responsibility disclaimer

All Indian reservoir data shown on reservoirs.earth originates from the Central Water Commission and the Maharashtra Water Resources Department, both official Indian Government bodies. reservoirs.earth is an independent project that collects, processes and aggregates this publicly available data solely to make it more visually accessible. We are not affiliated with CWC, WRD or any Indian government body, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. For authoritative figures, always consult cwc.gov.in directly.

South Africa

South African data is sourced from the Department of Water and Sanitation (DWS) weekly province dam-level bulletin pages. DWS publishes structured HTML tables for each of South Africa's 9 provinces every Tuesday or Wednesday. No dedicated public API exists; data is extracted by parsing the official HTML.

SourceDWS — Department of Water and Sanitation (South African Government)
URL patterndws.gov.za/Hydrology/Weekly/ProvinceWeek.aspx?region=XX
Update frequencyWeekly (Tuesday / Wednesday)
Coverage~218 dams · 9 provinces (WC, EC, FS, GP, KZN, LP, MP, NC, NW)
Historical depthWeekly snapshots from build date
LicenceOpen government data (www.gov.za)

Reservoir coordinates, river names and engineering metadata (dam height, dam type, year built) are enriched from the publicly available DWS National Integrated Asset Management register and GRanD (Global Reservoir and Dam) database v1.3. reservoirs.earth does not modify any of the underlying measurements.

Data responsibility disclaimer

All South African reservoir data shown on reservoirs.earth originates from the Department of Water and Sanitation, an official South African Government department. reservoirs.earth is an independent project that collects, processes and aggregates this publicly available data solely to make it more visually accessible. We are not affiliated with DWS or any South African government body, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. For authoritative figures, always consult dws.gov.za directly.

Pakistan

Pakistani data is sourced from the daily water situation reports published by IRSA (Indus Rivers System Authority), the federal body responsible for managing and distributing Indus basin water among Pakistan's four provinces. IRSA publishes a PDF report each day (typically with a 2-day lag) containing current water levels for the country's main storage dams.

Water levels are provided in feet and converted to fill percentage using piecewise linear elevation–storage curves derived from published WAPDA (Water and Power Development Authority) engineering reports and dam O&M manuals. Only the most recent ~10 days of PDFs are available on the IRSA server at any given time.

Reservoirs covered

Tarbela DamIndus · Khyber Pakhtunkhwa · 13,690 MCM
Mangla DamJhelum · Azad Jammu & Kashmir · 9,116 MCM
Chashma DamIndus · Punjab · 261 MCM

These three reservoirs represent approximately 80% of Pakistan's total regulated storage capacity and are the only ones for which IRSA publishes systematic daily data.

SourceIRSA — Indus Rivers System Authority (Government of Pakistan)
URL patternpakirsa.gov.pk/Doc/Data{DD}-{MM}-{YYYY}.pdf
Update frequencyDaily (2-day lag)
Coverage3 major reservoirs · ≈80% of Pakistan's total storage capacity
Historical depthRolling ~10 days (PDF availability on IRSA server)
ParsingPDF text extraction via Python pdfplumber

Data responsibility disclaimer

All Pakistani reservoir data shown on reservoirs.earth originates from IRSA, an official Pakistani federal authority. reservoirs.earth is an independent project that collects, processes and aggregates this publicly available data solely to make it more visually accessible. We are not affiliated with IRSA, WAPDA or any Pakistani government body, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. For authoritative figures, always consult pakirsa.gov.pk directly.

Australia

Australian data is sourced entirely from the Bureau of Meteorology (BOM), the Australian Government's official national weather, climate and water agency. Two complementary BOM services are used together:

Reservoir metadata — BOM ArcGIS Water Storages layer

SourceBOM Australia_Water_Storages MapServer (ArcGIS REST)
FieldsName, total capacity (ML), accessible capacity (ML), river, state, year completed, coordinates
Derived fromGeofabric V3.2 AHGFWaterbodies (national hydrological framework)
URLhosting.wsapi.cloud.bom.gov.au/arcgis/rest/services/Australia_Water_Storages/MapServer
Auth requiredNone (public)

Storage readings — BOM KiWIS Water Data Online

SourceBOM Water Data Online — KiWIS REST API
ParameterStorage Volume (ML), daily quality-controlled mean (DMQaQc.Merged.DailyMean.24HR)
Coverage~250 publicly-owned reservoirs across all states and territories
URLwww.bom.gov.au/waterdata/services
Auth requiredNone (public)

State agencies (WaterNSW, Melbourne Water, Seqwater, SunWater, SA Water, Water Corporation WA, Hydro Tasmania, etc.) report storage data to BOM under legal obligation established by the Water Act 2007 and Water Regulations 2008. BOM consolidates this into Water Data Online — the Australian equivalent of the US USGS NWIS system.

Capacity figures are sourced from the BOM ArcGIS layer (total design capacity, not estimated from historical maximums). Fill percentage is computed as current storage volume divided by total design capacity.

Data responsibility disclaimer

All Australian reservoir data shown on reservoirs.earth originates from the Bureau of Meteorology, an official Australian Government agency. reservoirs.earth is an independent project that collects, processes and aggregates this publicly available data solely to make it more visually accessible to any user who needs it. We are not affiliated with the Bureau of Meteorology or any Australian government body, we do not alter the underlying measurements, and we accept no responsibility for the accuracy, completeness or timeliness of the source data. Data is reproduced under the terms of the Creative Commons Attribution 4.0 licence and attributed as © Commonwealth of Australia (Bureau of Meteorology). For authoritative figures, always consult BOM Water Data Online directly.

Unit conversion1 ML = 0.001 MCM (all values stored in MCM / hm³)
Update frequencyRebuilt on demand via build script (not live)
Historical depth3-year rolling window from build date
Licence© Commonwealth of Australia (Bureau of Meteorology) — CC BY 4.0

Other countries (planned)

We plan to add more countries as standardised open datasets become available. The architecture is country-agnostic: each country maps to a region → reservoir hierarchy with the same fill-level schema.

How numbers are calculated

Derived metrics

Fill percentage

Fill percentage is calculated directly from the source data as:

fill_pct = (volume_stored_hm³ / total_capacity_hm³) × 100

Both values come from the official bulletin. Total capacity may change over time if a reservoir is modified or its survey is revised; we always use the capacity reported in the same weekly reading.

Status thresholds

Status labels are derived from fill percentage:

Critical< 20 %
Low20 – 40 %
Normal40 – 80 %
High80 – 100 %
Full> 100 %

Historical monthly average

For each reservoir we compute the mean fill percentage for each calendar month across all available years (1988–present). This gives 12 reference values used to contextualise the current reading against the historical norm. It is updated whenever the full database is refreshed.

Regional aggregates

Regional and national fill figures are capacity-weighted: total water in storage divided by total capacity across the reservoirs in scope, at the time of the latest reading. A large reservoir therefore counts far more than a small one — consistent with the Reservoir Transparency Index, which scores coverage by capacity rather than by reservoir count.

Precipitation & forecasts

Weather data

Meteorological context is provided by Open-Meteo, a free and open-source weather API that aggregates numerical weather model output. No API key is required.

For each reservoir we query the Open-Meteo Forecast API using the reservoir's coordinates, requesting:

  • ·precipitation_sum — daily precipitation (mm), past 30 days + 14-day forecast
  • ·temperature_2m_mean — mean daily air temperature (°C)
  • ·et0_fao_evapotranspiration — reference evapotranspiration (mm/day), proxy for reservoir evaporation
  • ·snow_depth_water_equivalent_max — snowpack water equivalent (mm), relevant for Alpine and Pyrenean basins

Weather data is fetched on demand per reservoir page, cached for 1 hour server-side, and used to display a 44-day precipitation chart (30 past + 14 forecast) alongside a qualitative trend indicator. Responses are proxied through an internal API route to avoid CORS and to apply caching.

ProviderOpen-Meteo (open-source, free)
ModelBest-match ensemble (GFS, ECMWF, ICON)
Past data30 days
Forecast14 days
Cache1 hour (server-side)

Coordinates & administrative boundaries

Geocoding

Reservoir coordinates (latitude / longitude) are obtained from official sources where available, or reverse-geocoded using Nominatim (OpenStreetMap's geocoding service). Province and autonomous community assignments are derived from the same Nominatim reverse-geocoding step.

Community boundary polygons used in the choropleth map are sourced from click_that_hood (MIT licence), based on OpenStreetMap data.

GeocoderNominatim / OpenStreetMap (ODbL licence)
Boundariesclick_that_hood / OpenStreetMap
Rate limit respected1 request / second

Honesty first

Limitations & caveats

  • !Data is updated weekly. Intra-week fluctuations (heavy rain, emergency releases) are not reflected.
  • !Fill percentages above 100 % occur when reservoirs temporarily hold water above their nominal capacity (flood control). This is normal operating practice.
  • !Historical averages include years of drought and flood. They are descriptive, not normative targets.
  • !Weather forecasts beyond 7 days carry significant uncertainty and should be treated as indicative only.
  • !82 reservoirs currently lack precise coordinates and appear only in confederation-level aggregates. Geocoding is in progress.
  • !This site is not affiliated with any government body. All data originates from official government sources and is reproduced here for informational purposes only. We do not alter measurements and accept no responsibility for their accuracy. When in doubt, consult the original source agency directly.

How often data refreshes

Update schedule

Reservoir readingsWeekly (Tuesday, after MITECO publishes)
Historical averagesWeekly (recomputed from full BD-Embalses)
GeocodingOn demand, when new reservoirs are added
WeatherOn demand, cached 1 h per reservoir
Map boundariesStatic (updated manually when OSM data changes)

Part 2 · v1.3.0

Reservoir Transparency Index (RTI) Methodology

The Reservoir Transparency Index scores each country on 7 weighted dimensions of water data openness. All evaluations are evidence-based, publicly auditable, and re-evaluated every six months (H1 / H2).

How to read this

What an RTI score means in 30 seconds

  • ·The RTI is a 0–100 score measuring how openly a country publishes its national reservoir storage data.
  • ·It is not a measure of water governance, climate performance, or how much water a country has — only data openness.
  • ·The dominant component is Coverage (30% weight): share of total national reservoir storage capacity (Mm³) with public data.
  • ·Countries with no significant reservoirs (Tuvalu, Vatican, Bahrain) are not rated — they are listed separately as N/A rather than given an F, because the absence of reservoirs is a geographic fact, not a transparency failure.
  • ·Denominators (total national capacity) are estimated conservatively: adds 5–15% for private hydropower, irrigation, and industrial reservoirs typically excluded from official datasets.

Scoring formula

Total score

The total score is a weighted sum of the 7 dimension scores (each 0–100):

score = Σ (dimension_score × weight)

Dimensions

The 7 dimensions

Coverage

30%

Capacity-weighted: % of total national reservoir storage capacity (Mm³) that has public data. Score = round(100 × covered_capacity / total_capacity).

score = round(100 × covered_capacity_hm³ / total_national_capacity_hm³)
Reference points
100SpainMITECO BD-Embalses covers ~56,000 of ~57,000 Mm³ total national capacity (~98%)
95CyprusWDD covers 290 of ~308 Mm³ total (~94%)
85BrazilANA SAR + ONS covers ~570,000 of ~670,000 Mm³ (~85%)
60USAFederal+state APIs cover ~480,000 of ~830,000 Mm³ NID total (~58%)
35ItalyLaghi.net + Sardegna + ARPAs cover ~5,300 of ~15,000 Mm³ (~35%)
5ChinaPublic coverage ~50,000 of ~1,000,000 Mm³ MWR total (~5%)

Linear scale. No bands. The denominator is the sum of operating-storage capacity of all reservoirs in the country (use ICOLD World Register, AQUASTAT, or national dam authority). The numerator is the sum of capacity of reservoirs whose levels appear in any structured public data source. Run-of-river plants contribute ~0 to both numerator and denominator and effectively cancel out. Pumped-storage cycles are counted once at design capacity. Document both numbers in the justification.

Data Availability

20%

Publication completeness and granularity for reservoirs whose capacity contributes to the covered total

100Daily data for >95% of covered capacity
e.g. Cyprus — WDD Dams Monitor live dashboard for all major reservoirs
80–99Daily data for >50% of covered capacity
e.g. Brazil — ONS publishes daily for SIN reservoirs
60–79Weekly data, or daily for <50% of covered
e.g. Spain — MITECO Boletín Hidrológico Semanal
40–59Monthly data
e.g. Cuba — INRH monthly Boletín Hidrológico PDF
20–39Only sporadic / event-driven reports
e.g. Iran — ministerial press conferences during drought
0–19No structured publication
e.g. Tajikistan — leaks during crises only

Technical Accessibility

15%

Machine-readability of the COVERED data — API availability, downloadable formats, open license

100Documented REST API + structured downloads + open license
e.g. South Korea — data.go.kr REST API for K-water + KRC
80–99API or structured downloads (one of the two)
e.g. Australia — BOM OGC SOS2 API
60–79Structured data requiring scraping
e.g. Czechia — Povodí HTML tables, no API
40–59Structured PDFs (tables)
e.g. Spain — BD-Embalses .mdb / structured PDF tables
20–39Narrative PDFs or images
e.g. Iran — Persian PDF bulletins
0–19No viable technical access
e.g. Sudan — no functioning portal

Historical Depth

13%

Median years of accessible historical series across COVERED reservoirs (weighted by capacity, not count)

100Median 20+ years across covered capacity
e.g. Spain — 38 continuous years for BD-Embalses (most of capacity)
80–99Median 10–20 years
e.g. USA — most federal reservoirs have 30+ yr median; small subset shorter
60–79Median 5–10 years
e.g. Czechia — Povodí portals show ~6-yr archives per dam
40–59Median 2–5 years
e.g. Colombia — SIMEM launched Sept 2023 (~2.5 yrs)
20–39Median less than 2 years
e.g. Costa Rica — CENCE dashboard current snapshot only
0–19Current reading only / no archive
e.g. Bangladesh — Kaptai press-release-only

Score the MEDIAN across the covered capacity. If 90+ year records exist for a few small stations but the majority of covered capacity has only 5 years online, score 60-79.

Update Frequency

10%

Typical refresh cadence for the COVERED capacity

100Real-time or sub-daily (<24h) for >50% of covered capacity
e.g. South Korea — K-water API 10-minute updates
80–99Daily for >50% of covered capacity
e.g. Brazil — ONS daily reservoir bulletin
60–79Weekly for >50% of covered capacity
e.g. Spain — MITECO weekly bulletin
40–59Monthly
e.g. Cuba — INRH monthly bulletin
20–39Quarterly or irregular
e.g. Burkina Faso — DGRE 10-day bulletins only during flood season
0–19On demand only / unscheduled
e.g. Eritrea — no schedule, no public output

Methodological Transparency

8%

Public documentation of measurement methods, capacity figures, elevation-volume curves, QC procedures for COVERED reservoirs

100Full methodology + per-reservoir metadata + documented QC for all covered
e.g. USA — USGS National Field Manual + 25k parameter codes
60–99Methodology partially published (capacity figures, basic curves)
e.g. Spain — design capacity public, no calibration docs
30–59Variable names only, no context
e.g. Italy — capacity in MIT register, no measurement methodology
0–29No documentation
e.g. Cambodia — Chinese operators publish nothing on methods

Language and Usability

5%

Language availability and UI quality across all published portals (independent of coverage)

100English + local language + modern UI
e.g. USA, Australia — fully English, modern dashboards
60–99Local language only, modern UI, some English navigation
e.g. Czechia — Povodí English navigation, data labels in CZ
30–59Local language only, dated UI
e.g. Spain — SAIH portals Spanish-only, mostly 2000s-era
0–29Unusable / no functioning interface
e.g. China — Mandarin only, paywalled API

Grades

Score to grade mapping

A+90100Exemplary
A8589Excellent
A-8084Very Good
B+7579Good
B7074Above Average
B-6569Average
C+6064Below Average
C5559Weak
C-5054Inadequate
D+4549Poor
D4044Very Poor
D-3539Critical
F034Opaque

Worked examples

How scores combine — six examples

Example 1 — Spain (real country, A- tier)

MITECO covers ~56,000 of ~57,000 Mm³ total national capacity. Weekly cadence. Proprietary .mdb format. Spanish only. 38 years of history.

98
coverage
92
data availability
45
technical accessibility
100
historical depth
75
update frequency
72
methodological transparency
42
language usability
0.30×98 + 0.20×92 + 0.15×45 + 0.125×100 + 0.10×75 + 0.075×72 + 0.05×42
Total29.40 + 18.40 + 6.75 + 12.50 + 7.50 + 5.40 + 2.10 = 82.05A-

Lesson: Comprehensive capacity coverage + deep history carries Spain to A-. Limited only by proprietary format and Spanish-only delivery.

Example 2 — Jamaica (real country, capacity-weighted recovery)

Country has only 2 reservoirs (Mona 3.67 + Hermitage 1.78 Mm³, total ~5.5 Mm³). Under the OLD >10 hm³ threshold, both fell below cutoff → coverage = 0. Under capacity-weighted: NWC publishes both weekly → coverage ≈ 100% of national storage.

100
coverage
52
data availability
18
technical accessibility
22
historical depth
48
update frequency
28
methodological transparency
82
language usability
0.30×100 + 0.20×52 + 0.15×18 + 0.125×22 + 0.10×48 + 0.075×28 + 0.05×82
Total30.00 + 10.40 + 2.70 + 2.75 + 4.80 + 2.10 + 4.10 = 56.85C

Lesson: Jamaica genuinely publishes its full reservoir stock weekly — the old methodology unfairly scored it 0 because both reservoirs were below 10 hm³. Capacity-weighting correctly recognises 'they publish everything they have'.

Example 3 — Hypothetical 'big country with weak coverage'

200,000 Mm³ total national capacity. Only 60,000 Mm³ is publicly reported, but those reservoirs have great APIs, 25 years history, daily updates.

30
coverage
90
data availability
95
technical accessibility
100
historical depth
90
update frequency
95
methodological transparency
100
language usability
0.30×30 + 0.20×90 + 0.15×95 + 0.125×100 + 0.10×90 + 0.075×95 + 0.05×100
Total9.00 + 18.00 + 14.25 + 12.50 + 9.00 + 7.13 + 5.00 = 74.88B

Lesson: Coverage gap costs ~21 points vs perfect. Even with world-class quality on what is published, a country with 30% capacity coverage cannot crack the A tier.

Example 4 — Hypothetical 'wide but shallow' country

All reservoirs reported, but only via monthly PDFs, 5 years of history, local language. Total national capacity = 50,000 Mm³, all publicly tracked.

100
coverage
50
data availability
40
technical accessibility
65
historical depth
50
update frequency
40
methodological transparency
40
language usability
0.30×100 + 0.20×50 + 0.15×40 + 0.125×65 + 0.10×50 + 0.075×40 + 0.05×40
Total30.00 + 10.00 + 6.00 + 8.13 + 5.00 + 3.00 + 2.00 = 64.13B-

Lesson: Comprehensive reporting in poor formats earns a meaningful B-. Coverage matters most, but quality of delivery is still ~65% of the total weight.

Example 5 — Structural N/A (no reservoirs)

Country has no surface reservoirs — entirely desalination/groundwater economy (Bahrain, Tuvalu, Vatican).

0
coverage
0
data availability
0
technical accessibility
0
historical depth
0
update frequency
0
methodological transparency
60
language usability
Only language_usability contributes
Total0.05 × 60 = 3.00F

Lesson: Structural N/A. Flag clearly in country narrative — this is not a governance failure, the country has no reservoirs to report.

Example 6 — Strategic withholding of dominant reservoir

Country has 200,000 Mm³ total capacity. One reservoir (160,000 Mm³, 80% of total) is treated as a state secret. The remaining 40,000 Mm³ across smaller reservoirs is reported monthly.

20
coverage
45
data availability
25
technical accessibility
55
historical depth
50
update frequency
30
methodological transparency
25
language usability
0.30×20 + 0.20×45 + 0.15×25 + 0.125×55 + 0.10×50 + 0.075×30 + 0.05×25
Total6.00 + 9.00 + 3.75 + 6.88 + 5.00 + 2.25 + 1.25 = 34.13F

Lesson: Capacity-weighted coverage CORRECTLY punishes hiding the biggest reservoir. Under count-based methodology, reporting 19 of 20 reservoirs scored 95% — but capacity-weighted shows the truth: 80% of the country's water is invisible.

Common pitfalls

What NOT to do

  • DO NOT use count-based coverage (% of reservoirs above some threshold). Use capacity-weighted coverage (% of national storage Mm³).
  • DO NOT score historical_depth = 100 because one station has 90 years. Score the MEDIAN across the covered capacity.
  • DO NOT inflate technical_accessibility for paid/login-gated APIs. A documented but auth-gated REST API is at most 80, not 100.
  • DO NOT count tweets, social media posts, or one-off press releases as 'data'. The data must be structured and recurrent.
  • DO acknowledge structural N/A explicitly in the country narrative — these are not governance failures.

Changelog

Methodology versions

v1.3.02026-05-29

Coverage redefined from count-based (% of reservoirs >10 hm³) to CAPACITY-WEIGHTED (% of total national reservoir storage capacity covered by public data). Eliminates the arbitrary >10 hm³ threshold and resolves the structural-zero problem for micro-states (Jamaica, Cape Verde, etc.) and the small-country bias problem. Directly answers: 'What share of the country's water storage is publicly trackable?'

v1.2.02026-05-29

Weights rebalanced. Coverage is now the most heavily weighted dimension (30%, up from 15%) because it bounds the meaningfulness of every other dimension.

v1.1.02026-05-29

Coherence patch. Coverage is now strictly linear; quality dimensions scoped to the COVERED subset; assessed on the typical (median) reservoir, not the best example.

v1.0.02026-05-25

Initial release. 7 dimensions, 194 countries evaluated.