DEV Community

Cover image for Pretty flood maps are liars. One live gauge. Zero flood pins. We refused to paint the county.
Alex
Alex

Posted on Originally published at atlas.modelmarket.dev

Pretty flood maps are liars. One live gauge. Zero flood pins. We refused to paint the county.

Split still: a blue county blob vs one USGS pin at Baton Rouge

You know the dashboard that fills a whole county with blue and calls it a flood.

It photographs well. It is not hydrology.

A river gage sells a stage, a discharge, a named place. It does not sell a polygon. The product UI quietly upgrades that pin into a lake because blue looks like water, and water looks like a decision.

We already said this about fire. FIRMS sold 152 heat detections and refused to draw a perimeter. Flood maps do the same trick with a different crayon.

So we shipped the unsexy sibling: Flood Glass. Cite the pin. Do not invent the lake.

Live (English UI, crypto off): atlas.modelmarket.dev/?layers=flood,river


This run (2026-08-20)

One invoke of atlas.situation.brief@v1. Gulf / Lower Mississippi. Layers flood + river. Sample bbox, not “the Mississippi as a myth.”

Field Value
LIVE river citations 1 — Mississippi at Baton Rouge
Discharge 6909.3 m³/s
Gage height 2.48 m
Flood pins in the box 0
Score 41 / 100 — ranks cited layers. Does not simulate water
Source USGS National Water Information System (U.S. Government public domain)

Honest citation table: one LIVE pin, flood alerts zero
The whole movie. Empty flood stays empty. Adults can live with that.

The brief printed the sentence on the paper:

Not a forecast or insurance trigger.

A score of 41 is not a flood model dressed as a map. It is how heavy the citations felt in that box that morning.


Who painted the county

A huge blue oval labeled interior design
The gauge never gave this shape. The dashboard painted it because blue looks decisive.

If a kitchen tap drips, you do not sketch a house-shaped ocean and tape it to the fridge.

You look at which sink. You look at how high. You do not brief a board with a cartoon lake.

Pairing is co-presence, not a forecast: a watch next to a gage, two receipts, one table. We did not merge them into a shoreline. When only the gage speaks, that is the movie. Do not invent the missing alert to fill the silence.

Four stamps: not a forecast, not 911, not NFIP, not a payout
Print the refusal. Pretty maps invent lakes. Briefs do not.


What this is not (say it like you mean it)

Claim people hear What is actually true
“The county is underwater” One LIVE USGS pin. Flood alerts in that box: zero
“AI predicted the flood” No model. A snapshot you can cite
“This is 911 / NFIP / a payout quote” It is none of those. Not parametric. Not an insurance trigger
“The score is the water” The score ranks citations. It does not move a cubic meter

Same honesty we already put on fire. The desk files the refusal. Flood Glass is the hydrology snapshot.


Open the glass

  1. atlas.modelmarket.dev/?layers=flood,river — English UI
  2. Idea path: use.modelmarket.dev → flood hydrology
  3. Capability: atlas.situation.brief@v1

Receipt strip: sha256 + ed25519 signed
A screenshot is not evidence. The receipt is.

This run’s digest: 8df928bf10b8593adeae9651039d9b32f97c682d… · Ed25519 signed · atlas 0.1.0 · 2026-08-20T09:43:03Z.

YouTube Season 37 walks the same refusal: Pretty Flood Maps Are Liars.

Stop painting the county.

Top comments (0)