Skip to content

andrewlengly.com/fish-maps-casestudy :: fish maps case study

# A 3D map of San Francisco Bay showing where king tides land today and how much sea level rise makes them an everyday high.

designed page ......... /fish-maps-casestudy

THE SHORT VERSION

  Fish Maps is a 3D map of San Francisco Bay that shows how much sea level rise turns the
  year's highest tide into an ordinary high tide. It ranks the highest predicted tides at 7
  Bay gauges and draws NOAA's sea level rise water on the shoreline one foot at a time. It
  is built with Next.js, MapLibre, deck.gl and d3, and it has been live since November 6,
  2026.

the question .......... How much sea level rise turns today’s highest tide of the year into
                        an ordinary high tide, and where does that water go?
what i did ............ Built a 3D map that ranks the year’s highest predicted tides at 7
                        Bay gauges and draws NOAA’s sea level rise water on the shoreline,
                        one foot at a time.
where it stands ....... Live since November 6, 2026. Every source works with no key, and
                        there’s no database.

kind .................. Case study · Build
role .................. Developer
year .................. 2026
tools ................. Next.js, MapLibre, deck.gl, d3, Claude Code

what it does .......... A 3D map of San Francisco Bay that shows where king tides land today
                        and where everyday highs reach with 1 to 10 ft of sea level rise.

WHY I BUILT IT

  # A king tide is a preview of an ordinary high tide.

  King tides are the highest predicted tides of the year. In San Francisco Bay they arrive
  around the winter and summer solstices. On a calm day one may only wet low paths and
  parking lots.

  With enough sea level rise, that same water shows up on an ordinary day. Fish Maps puts a
  number on that gap at each gauge and draws the matching water on the shoreline.
official dates and photos
                        California King Tides Project

WHAT IT DOES

  # Everything sits on one map of the Bay.

3d map ................ Seven Bay gauges on 3D terrain, with NOAA’s mapped water for 0 to 10
                        ft of sea level rise.
tide scrubber ......... Plays the predicted tide and adds it to the slider, so the shoreline
                        moves with the water.
king tide calendar .... The 20 highest predicted tides in the next 12 months across the Bay,
                        from NOAA alone.
check a place ......... Tap the map or search an address to see the first foot of rise where
                        that spot goes under, and roughly when the state expects it.
go see it ............. The next king tide, when to arrive, a warning for peaks after dark
                        and spots to stand at near the gauge.
station pages ......... One page per gauge, with predicted days over its flood level today
                        and with 1, 2 and 3 ft of rise.
shoreline spots ....... 15 places people go to watch king tides, each with the first NOAA
                        step that floods it.

HOW I BUILT IT

  # Checks changed the build right up to launch.

  # From 87 source calls to the first real deploy
  01. 87 source calls
      86 came back OK
      Skipped: USGS CoSMoS. Its map service returned the one 404
  02. NOAA’s live answers
      Thresholds taken from station metadata
      Sea level rise tiles at zoom 16, about 2.4 m a pixel
  03. Spots traced to sources
      Every fact matched to a source page, then re-checked
      Wording scaled to the evidence behind it
      Moved: Sausalito, from Bridgeway to Kappas Marina, where the flooding is documented
  04. Tests before launch
      53 unit tests, every derived metric covered
      25 browser tests at phone and desktop widths
      Bug: Floating-point math pushed a tide at the threshold over it
  05. First real deploy
      Flat land color hid the poster image on a cold load
      Until imagery arrived, about 3 s on fast wifi
      Fixed: The canvas stays transparent until imagery loads, up to 8 s, and a browser test
      covers it

  Some NOAA services answered wrong. The map works around each one.
source ................ What the data got wrong

  # How a spot page words its evidence
water reported ........ a source reports water at the spot during king tides (8 spots)
viewing event ......... a source reports a viewing event, and the page says only that (4
                        spots)
dated photo ........... a dated photo caption is the only record (2 spots)
nothing found ......... no source documents king tide flooding there, and the page says so
                        (Redwood Shores)
  At the Embarcadero, reports show water at king tides, and NOAA’s layer first floods it at
  4 ft. Its page says so. That gap is a limit of the screening layer.

THE 3D MAP

  # Buildings turn coral when the water reaches them.

  I modeled the map on FireTrace, Dilum Sanjaya’s wildfire map. It recolors its imagery with
  a Mapbox paint property that MapLibre doesn’t have.

  So Fish Maps repaints each USGS imagery tile in the browser onto a gray-blue ramp. It
  keeps a quarter of the original color, so marsh and mudflat still read apart from
  pavement.
the map i modeled this on
                        FireTrace

buildings in the water
                        From zoom 15, every building on screen is tested against NOAA’s
                        connected water at the foot the map shows. Wet ones turn coral, and
                        the slider panel counts them.
staff gauges .......... Each gauge stands as a staff marked every foot. A 6 ft figure stands
                        at the high-tide line for scale.
key events ............ Each day’s highest high this week, king tides, crossings of the
                        minor flood level and the largest observed surge. Each row jumps the
                        scrubber.
terrain height ........ 1x, 2x, 3x or 5x, saved in the link. The Bay floor is set flat so
                        the water stays one surface.

coral building ........ one whose footprint center sits in NOAA’s connected water at the
                        whole foot the map shows
  That’s one point per building tested against a screening layer, so a coral building may
  stay dry and a gray one may not. Up to 1,500 buildings are tested at a time, or 600 on
  phones.

HOW IT WORKS

  # No database, and no keys.

  # How a tide moves from NOAA to the map
  01. NOAA CO-OPS
      Tide predictions
      Observed water levels
      Datums and flood levels
  02. Next.js server
      Cached pages
      King tide and flood-day math
      Refreshes: Predictions once a day from a Vercel cron, observed water every 6 minutes
  03. Browser map
      MapLibre with 3D terrain
      deck.gl gauge staffs
      Also reads: NOAA sea level rise tiles, repainted pixel by pixel

  NOAA caps high and low requests at a year and 6-minute requests at a month, so longer
  ranges get split. Datums and flood levels change rarely, so a script builds them once and
  they’re committed.

THE MATH

  # Every number starts from mean higher high water.

  Mean higher high water (MHHW) is the average height of each day’s higher high tide. It’s
  where the shoreline sits on an ordinary day.

height above mhhw ..... predicted height minus MHHW
future-tide equivalent
                        the larger of 0 and the height above MHHW
surge ................. the largest gap between observed and predicted water in the last 72
                        hours
  The equivalent is the sea level rise at which a water level becomes an ordinary daily
  high. It assumes the tide range holds as the sea rises.

days(+x ft) ........... Pacific days with a predicted high where height + x minus MHHW tops
                        NOAA’s minor flood level
  Counted for 0 to 3 ft of rise over the next 12 months. Three gauges have only an action
  level, and their pages count that and say so.

level ................. slider + the tide above MHHW at the selected gauge
first flood step ...... the lowest foot where a quarter of a 5 by 5 grid of points at the
                        spot is wet and connected
  NOAA publishes one layer per whole foot. At 2.4 ft the map draws the 2 ft water plus 40
  percent of the band between 2 and 3 ft. That blend is visual, since NOAA models no
  fractional feet.

WHAT IT FOUND

  # At Alameda, 2 ft of rise tops the flood level on more than half the days of the year.

  # Predicted days over the minor flood level at Alameda, as of November 6, 2026
no rise added ......... 0
1 ft of rise .......... 22
2 ft of rise .......... 198
3 ft of rise .......... 341
  Each bar adds its rise to every predicted high in the next 12 months. A full bar would be
  all 365 days.

  # Predicted days over each gauge’s threshold with 2 ft of rise, as of November 13, 2026
point reyes ........... 226
port chicago .......... 219
san francisco ......... 217
richmond (action level)
                        209
martinez (action level)
                        204
alameda ............... 194
redwood city (action level)
                        176
  Gauges marked action level have no NOAA minor flood level, so they count days over the
  action level, a watch point. Crossing it doesn’t mean flooding. Counts move as the window
  rolls forward. Alameda’s was 198 on November 6.
source ................ Fish Maps station pages

  The week Fish Maps went live, five Bay gauges ran about 1.05 to 1.13 ft above prediction,
  with a 1.6 ft peak at Alameda on November 3. Predictions use a 1983 to 2001 reference, so
  part of every gap is sea level rise that has already happened.

WHAT THE DATA GOT WRONG

  # NOAA’s own services gave a few wrong answers.

  The identify service returned the same polygon at every point
    risk .............. Every spot reads the same step
    call .............. Read pixels straight from the level 16 tiles

  NOAA’s tiles paint the whole Bay one navy
    risk .............. The Bay turns navy at every step
    call .............. Repaint tiles in the browser so open water clears

  The terrain tiles include Bay bathymetry
    risk .............. At 3x the Golden Gate channel becomes a 300 m trench
    call .............. Set everything below sea level to zero

  Only four of seven gauges have a minor flood level
    risk .............. Flood-day counts with no threshold
    call .............. Count the action level and label it

  First-pass spot points sat on high ground
    risk .............. China Camp read 8 ft and Point Isabel stayed dry through 10 ft
    call .............. Move each point to its lowest public road or path

  8.5 − 6.6 comes out to 1.9000000000000004
    risk .............. A tide right at the threshold counts as over it
    call .............. Round to a thousandth of a foot before comparing

  USGS imagery bands over open water
    risk .............. Stripes and gaps across the Bay
    call .............. Cover the Bay with a flat water tint

DECISIONS

  # Small choices that keep the map honest.

official dates kept apart
                        A row gets an official tag only once a Coastal Commission date is
                        entered by hand. The computed peaks never stand in for those dates.
point reyes off the bay calendar
                        It sits on the open coast and took 13 of the top 20 rows.
a light map ........... The project brief asked for a light map at #eef3f5, so Fish Maps
                        breaks from the dark maps in the series.
staffs drawn to be read
                        A 2 m tide range across a 30 km view is under a pixel at true scale.
                        Staffs scale to the screen, and each label prints the true value.
the map waits on phones
                        It boots on the first touch or 3.5 s after load.
maplibre pinned to 5.24
                        Grid Watch broke on version 6, so Fish Maps follows its pin.

DESIGN

  # The water darkens with every foot.

  Flooded land takes a blue that darkens with each foot of rise, over a light gray-blue map.
  Coral marks a staff past its flood level or a building in the water. Every step prints its
  foot value, so color never carries meaning alone.

type .................. Schibsted Grotesk for text and IBM Plex Mono for heights and times.
eleven steps .......... Lightness falls at every step from 0 to 10 ft, in normal vision and
                        simulated deuteranopia.

  # Color distance between map colors (ΔE), normal vision and simulated deuteranopia
columns ............... Normal | Deuteranopia
water vs flood coral
                        93.9 | 89.1
bay tint vs the 6 ft step
                        50.7 | 53.6
  Neighboring water steps sit 6.6 to 8.2 apart under deuteranopia. The slider prints each
  foot, and staffs print their height.

WHERE IT STANDS

  # Live, with the king tide season ahead.

tide gauges ........... 7
shoreline spots ....... 15
unit tests passing .... 53
api keys .............. 0

  # Lighthouse on mobile, production build
columns ............... Performance | Accessibility | Best practices | SEO
map ................... 100 | 100 | 100 | 100
crab cove spot page ... 100 | 100 | 100 | 100
alameda station page
                        94 | 100 | 100 | 100
king tide calendar .... 94 | 100 | 100 | 100
  The map page’s 100 leaves out the map itself. On phones it boots after Lighthouse stops
  measuring. With the map in the window, an early build scored 60 on Lighthouse’s software
  renderer.

WHAT’S NEXT

  # What I’d add after the first winter.

  # Next
storm scenarios ....... USGS CoSMoS models storm flooding on top of sea level rise. I found
                        no public map service for it yet.
a phone test .......... Interaction timings so far come from a laptop GPU with the CPU
                        throttled.
official dates ........ Enter the Coastal Commission’s dates by hand. The dates file is
                        still empty, so no row carries an official tag yet.
checks in ci .......... Run the tests and the source check on every pull request. So far
                        they run locally.

  # Known limits
screening layers ...... NOAA’s layers leave out storms and waves. A flooded step is a reason
                        to go look.
no weather in predictions
                        Tide predictions cover astronomy alone. The surge readout shows how
                        far real water is running from them.
no dates on the steps
                        Sea level rise here is a set of what-if steps. Fish Maps makes no
                        forecast of when any step arrives.

TL;DR

built ................. A 3D map of the Bay that ranks king tides at 7 gauges and draws sea
                        level rise by the foot.
found ................. At Alameda, 2 ft of rise tops the minor flood level on 198 predicted
                        days, more than half the year.
  # by the numbers
  22 .................. Days over Alameda’s minor flood level with 1 ft of rise
  198 ................. Days over it with 2 ft of rise
  341 ................. Days over it with 3 ft of rise
the catch ............. The rise steps are what-ifs. Fish Maps makes no forecast of when 2
                        ft arrives.
next .................. Add USGS CoSMoS storm flooding on top of sea level rise once I find
                        a public map service for it.

LINKS

open fish maps ........ tides.andrewlengly.com
read the methodology
                        tides.andrewlengly.com/methodology
code .................. github.com/AndrewLengLy/tideline
the developer side .... /machine/developer

# end of /machine/fish-maps-casestudy. andrew.leng.ly@gmail.com · leave machine mode