Using the website
The site has three views, all reached from the header: the story page, Lake Watch and How we know. Every page carries the label "Provisional NISAR data".
The story page#
The story page explains why cloud hides glacial lakes and how radar keeps them in view. It is built from lakes.json, so its numbers always match the data in the build. The opening gives three figures (lakes watched, lakes holding water now, and NISAR passes over the lakes since the first pass), the latest radar pass, and seven numbered sections follow:
- The view: the same lake three days apart, radar against optical, and how shadows from mountains can hide a lake from either.
- The flood: the 2022 Shisper outburst and SUPARCO's 131 potentially dangerous lakes.
- The gap: the summer cloud, with SUPARCO's 2 July statement linked to its source.
- The measurement: Attabad's water read from radar, with its noise and status.
- The levels: the sites at Alert, Watch or Decrease noted, the other statuses folded by family, and every watched lake on a NASA MODIS map.
- Add a lake: the form for putting a new lake forward, covered below.
- The videos: the demo and how it works, with captions on.
Open Lake Watch is the main button, and Lake Watch is highlighted in the header on every page. The line under the button ("3 lakes need attention: …") opens Lake Watch filtered to those lakes. Follow the story steps through the guided lake story, and Play the videos jumps to the videos.
Lake Watch#
Lake Watch is a table of every watched lake, made for the disaster management officers who follow these lakes.
- Count tiles: Lakes watched, Needs attention, Open water, Frozen, Above mapped outline, No lake now and Not measured, plus Alert: growing, Ice breaking up and Changed since last build when the build has any. Clicking a tile filters the table. The table can also be filtered by district or SUPARCO match, or searched by name or PDGL number.
- What the statuses mean: a key, closed until clicked, with each status's marker and one plain sentence. Hovering a status chip shows the same sentence.
- The table: lakes that need attention come first, under one line that says what to do for each of them: check recent optical imagery (Sentinel-2 or Landsat) or the site, then contact NDMA for Gilgit-Baltistan or PDMA for Khyber Pakhtunkhwa. Show first message opens a flagged lake's message (what changed, how sure, what it is not) in the row. Each row gives the status and its reason or evidence, the radar water area and its change, the share of the largest mapped outline (the bar's tick marks 100%), the recent trend and the latest pass.
- Show map: the lakes on a NASA MODIS picture, each with its status marker, and the mapped lakes not watched yet as grey dots (a checkbox hides them). One credit line under the map names the map data, with the licence notices below it.
- Phone: the same lists as cards, with filter chips (including Needs attention, Not measured and District) and a List / Map bar.
Selecting a lake opens its page:
- The message first: the status and its headline. Where the change began with NASA's processing update (P05036), a note says it may be a processing effect, not a real change. What to do comes next, naming the right authority, with buttons for Open recent Sentinel-2 imagery, the official contact (NDMA for Gilgit-Baltistan, PDMA for Khyber Pakhtunkhwa) and Print lake brief. Then what changed, how sure, and what it is not.
- Change against baseline: the latest change against the lake's baseline, as numbers and a gauge, dated by the latest assessment. A frozen lake shows an Ice card here instead, with its freeze evidence and its last open-water pass.
- Against the largest mapped outline: the radar area as a share of the largest mapped outline, and whether it is Above, Within or Within noise. Not shown while the lake is frozen.
- Radar picture: the latest HH picture with the water read from radar on top in blue, and the pass, track and radar water area beside it. It is a crop on the UTM grid with north up, a picture and not a map overlay.
- History on track …: the chart and readings for the lake's status track only (a track is one repeating orbit path, and each sees the lake from its own angle), with the lake's normal range, the passes that set a level, any processing version change, and every pass left out and why. The readings table shows the newest six, or all of them.
- Sources and limits: the limits in plain words (with the technical wording folded), and the sources and processing details in a closed section.
Pages can be linked directly: #start (or no hash) opens the story page, #lakes Lake Watch, #lakes?show=attention Lake Watch with a filter, #lakes/passu a lake, #story the guided story, #evidence How we know and #videos the videos.
What each status means#
Every valid pass is compared with the median of earlier passes on its own track (its baseline) and that track's noise: z = (area − baseline) / noise. A measured lake has one of four levels; every other status says why there is none. On the site the statuses are grouped: the two frozen statuses show as Frozen with their evidence on a second line, and the five "not" statuses show as Not measured with their reason.
| Status | Meaning |
|---|---|
| Alert: growing | Two valid passes in a row, on any tracks, each more than twice the noise above its track's baseline. The chip is a solid yellow pill with a ▲ mark. A banner at the top of the story page names the lake, Lake Watch adds an Alert: growing count tile, and the lake's message says what to do (check recent optical imagery or the site, and contact NDMA for Gilgit-Baltistan or PDMA for Khyber Pakhtunkhwa), what changed, how sure and what it is not (not an outburst forecast). Official warnings come from PMD, NDMA, GBDMA and PDMA. |
| Watch | One pass more than twice the noise from its baseline, either way, or small changes in one direction that add up over several passes (a CUSUM reaching 4). Not confirmed: the next pass shows whether it holds. |
| Decrease noted | Two passes in a row more than twice the noise below their baselines. Information only, never an Alert: the radar sees a lake drawing down onto wet sediment at only about a tenth to a fifth of the real decrease, so check optical imagery. |
| No change | The latest pass is within twice the noise of its baseline. Most lakes read this way most of the time. |
| Not yet validated against Sentinel-2 | The lake has no current Sentinel-2 check of its radar water (none yet, one made before the method, zone or point changed, or one that failed or found no clear pair). Its area is shown as information only and it gets no level until a check is made; each data refresh tries again. A newly accepted lake is checked in the same refresh against the 2026 summer passes; it waits only when none of them is valid or no clear Sentinel-2 scene falls within 3 days of one. |
| Not measurable | The lake's Sentinel-2 check overlapped radar water with an IoU under 0.4, so the method is not trusted there: its area is shown as information only and it gets no level. |
| Frozen (likely) | The air at the lake (NASA POWER, adjusted to the lake's height) has had a daily mean below 0 °C for at least 7 days in a row and at least 30 freezing degree-days since 1 Sep. Radar cannot tell new ice from open water, so there is no level; the area is shown greyed, and passes taken while frozen are greyed and left out of the comparison. Lake Watch shows the lake as Frozen with "By air temperature since …" under it, and the lake page's Ice card gives the temperature run, the degree-days, the last Sentinel-2 view and the last open-water pass. |
| Frozen (seen by Sentinel-2) | A clear Sentinel-2 image shows snow or ice on at least 80% of the lake itself (its outline, or its summer radar water core). It holds until a clear image shows open water or the air warms enough to call break-up. Otherwise as Frozen (likely). |
| Break-up likely | A frozen lake has had 7 warm days in a row, or a radar pass shows its core much brighter than in summer, a brightening that matches ice going out. Still no level until the lake is released: "Radar back within its summer range", "Open water seen by Sentinel-2", or, for a lake with no radar summer level, "No freeze signal in air temperature since" a date, with open water not confirmed. |
| Not seen this pass | The newest NISAR pass over the lake was left out or gave no valid reading. |
| Not observable | Less than half of the lake's zone can be seen on any pass (outside the swath or masked). |
| Not enough NISAR looks yet | No track has 3 earlier valid passes to compare a new one with yet. |
| No lake now | Recent imagery shows no lake at the site, such as the empty basin of an ice-dammed lake that has drained. There is no level and no area curve, and the dark radar area there is not counted as lake area. SARtale keeps the site to watch for a lake forming: every data refresh, all year, it looks for a Sentinel-2 view of the site clear of cloud, snow and ice. The status gives the date of the last such view, and says when none has come since. |
| Lake may be forming | A site with no lake now where two clear, snow-free Sentinel-2 views at least 5 days apart both show water above the site's threshold (one such view alone is noted on the site as waiting for the next). There is no level. The radar dark area is shown but not yet treated as lake area; the SARtale team reviews the site to add it as a measured lake. |
A level describes radar water area only. It is not a measure of volume, depth or hazard, and an Alert is slow-growth monitoring, 5–12 days after a change begins, not outburst warning. A lake that recent imagery does not confirm, such as a narrow strip of ice and water, keeps its status and says so under Limits for this lake.
How we know#
This view sets out the evidence. It opens with how SARtale reads a lake in four steps, and a sentence, computed from the data, that explains the lake counts: the sites watched, how many hold water now or have no lake now, and how many of those holding water had a clear Sentinel-2 scene to check against. Short sections on frozen lakes and where the method falls short follow. Technical details, closed until clicked, holds the lake method, the Sentinel-2 cross-check and what is not validated, frozen lakes, the data, the map data licences, the limits, and how to check it yourself. Read it before quoting a number from the site.
Add a lake#
In the story page's Add a lake section, under Know a lake we are not watching?, anyone can put forward a lake:
- Enter the lake's name, its latitude and longitude, and where the coordinates come from (an inventory, a paper, a field survey or a map).
- Choose Request a lake. The site checks the input: the point must be in Gilgit-Baltistan or upper KP (34.4–37.6 °N, 70.8–76.6 °E).
- The site then opens a GitHub issue form with your answers filled in. Press Submit new issue. You need to be signed in to GitHub.
- A bot comments on the issue with the number of NISAR passes over the point. The request appears on the map as a requested lake.
- The team reviews it. An accepted lake joins the register and gets a level once a track has 3 earlier looks to compare a new pass with. A rejected one is closed with a reason.
A point within 1 km of a watched or already requested lake is turned down with the name of that lake. The details, including the labels you will see, are in Lake requests.
SARtale Guide