Concept, design, development, data pipeline and copy.
This case shows my ability to build the full path from raw data, satellite-image analysis and backend data flows to a product-like experience people can understand and explore.
Arctic sea ice is an abstract topic despite rich data availability. NASA, NOAA/NSIDC and OWID datasets, Sentinel-2 imagery and historical perspectives existed separately and needed to become accessible to readers.
The challenge was the mix of data processing, visual explanation and interaction. The story needed a reliable pipeline that turns climate data and image analysis into comparable data points instead of embedding finished charts.
I built a Next.js story with maps, charts and scroll-driven transitions, plus Python pipelines for global climate data and Sentinel-2 fjord analysis, FastAPI endpoints, PostgreSQL/JSON fallbacks and a RAG chatbot for historical Inuit texts.
Good visualization starts with the data flow: which raw sources become reliable, comparable and understandable for users?
The story leads readers through the topic while leaving enough interaction for them to discover their own comparisons.
Pipelines, APIs, maps and RAG are useful because they make a difficult topic more concrete.
The visible story is only the final layer: public climate datasets, Sentinel-2 imagery, a dedicated processing CLI and backend data flows feed the same maps, charts and scroll scenes.
Time series are ingested, smoothed, aligned to calendars and anomalies, then modeled as comparable datasets.
Story, API & dataThe Uummannaq pipeline loads tiles, masks clouds, separates ice, water and land, and exports overlays plus CSV metrics.
Satellite pipelineGlobal climate data and fjord aggregates are delivered through backend endpoints and fallback files for resilient story loading.
Story, API & dataScroll scenes, maps, charts and chat connect the technical data flows to a readable experience for non-expert readers.