Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The Hurricane Ian Replay with its NWS Official Alerts

Open
  • Is something wrong?
#52 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
css, github, typescript
Domain
backend-api-design, data-visualization, frontend

Research direction

Read docs/specs/regions-events-and-sandbox.md when branch 21-grill-regions merges, then inspect the Fort Myers pack, checked-in sources/ files, and the build and Node tests named in the acceptance criteria. Start by checking blockers #48 and #51 and the source README; the ticket also notes NOAA and USGS hosts may be blocked by the proxy. Done means the Ian Event, filtered alerts, gauge replay, reconstructed-station labels, timing note, theme roles, and passing scripts/check.sh meet the listed criteria.

Written by the indexing model from the issue text.

Description

area: node feature ready-for-agent

Parent

#26

What to build

The build generates the Ian Event (28 September 2022) for Fort Myers from the checked-in sources/ files (spec decision 5):

  • Water: the Fort Myers gauge (NOAA 8725520, 6-minute verified) is one station, converted from MHHW to NAVD88 with the station's published datum offset. Estero Bay and Fort Myers Beach are stations whose series is the Fort Myers curve scaled to NHC's 12.7 ft MHHW peak at Fort Myers Beach Pier, marked reconstructed, and the Replay says so on screen.
  • Official Alerts come from the NWS Tampa Bay warnings file: Lee County zones FLZ165 and FLZ265, issued or upgraded inside the window, with these phenomena: storm surge, hurricane, tropical storm, flood, flash flood (watches and warnings). Each is headed by phenomenon and significance ("Storm Surge Warning") at its utc_issue time, shown in Eastern time.
  • Official Gauge: 8725520's recorded series plays on the Event clock as a REPLAY Official Gauge.
  • Weather from the Weather Grid over the window, plus named phases (landfall at Cayo Costa).

Spec

docs/specs/regions-events-and-sandbox.md

Acceptance criteria

  • The Fort Myers pack contains the Ian Event; the build only re-fetches sources when asked
  • Build test: the Event surface is in the Region's datum; Official Alerts are filtered to FLZ165 and FLZ265 and the kept phenomena
  • Node test: Official Alerts from the Ian file appear at their Event clock times
  • The 8725520 series plays as a REPLAY Official Gauge
  • Reconstructed stations are labelled reconstructed on screen
  • The known timing error (the beach peak plays at the Fort Myers gauge's peak time) is written down in the Region's sources README
  • The look stays swappable (spec decision 8): every new visual value (colour, radius, shadow, font, motion) is a theme role in theme.css; map fills, line widths and opacities go in the one map style module (the first ticket that needs it creates it); Panel placement is set in the layout CSS, not the component; no look polish. The mock-ups (https://claude.ai/artifact/AjDsPvQPY3DFkSp1qzVCTH) show content and behaviour only, not the look.
  • scripts/check.sh passes; glossary entries, docs and lessons lines this change makes untrue are fixed in the same PR

Proxy note: cloud agent sessions run behind a proxy that blocks NOAA (tidesandcurrents.noaa.gov, api.tidesandcurrents.noaa.gov) and USGS (stn.wim.usgs.gov, 3DEP hosts). This ticket needs those hosts allowlisted in the environment's network policy, or a run on a laptop. CI never fetches from the network.

Blocked by

  • #48
  • #51
Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
56m
Merged PRs (30d)
42

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from StormShields/Stormshield

All issues in StormShields/Stormshield

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.