You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Way forward: turning the calendar-map into a dynamic, cost-effective storymap stack
#2
The DevelopmentSeed blog post Science Storytelling argues that screenshots are no longer the right unit of scientific publication- the page should talk to the data (engagement-first, source-connected, scientist-owned). For this challenge, that's exactly what the per-day storymap behind the calendar-map needs to become. We already have a working MDX publication routine in arco-ibf · cmra-web, visible at the live CRMA event page — but today its maps are baked PNGs and GIFs, not live tiles.
The way forward is to make those maps live by wiring them to TiTiler (raster, arco-ibf · titiler-pgstac) and TiPg (vector, arco-ibf · tipg) — possibly reusing the existing eafw_geoserve stack so we don't run two backends. The cost-effectiveness rule is simple: keep the calendar overview pre-rendered and only pay for live tiles on the per-day drill-down, cache everything (the ~1,000-day archive is finite and historical), and use vector for admin-1 / raster only for the grid layer.
Small starting step: take one event day mdx file, re-publish its page as an MDX file, swap one PNG for a live TiTiler tile of the same date, add one TiPg overlay for the BN admin-1 risk from bn-ibf · jua-bnet/flood_ibf, and measure cost per page-view. Once that's stable, the per-day pattern scales to the rest of the archive as a markdown edit, not a code change. @Bkoome
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The DevelopmentSeed blog post Science Storytelling argues that screenshots are no longer the right unit of scientific publication- the page should talk to the data (engagement-first, source-connected, scientist-owned). For this challenge, that's exactly what the per-day storymap behind the calendar-map needs to become. We already have a working MDX publication routine in
arco-ibf·cmra-web, visible at the live CRMA event page — but today its maps are baked PNGs and GIFs, not live tiles.The way forward is to make those maps live by wiring them to TiTiler (raster,
arco-ibf · titiler-pgstac) and TiPg (vector,arco-ibf · tipg) — possibly reusing the existingeafw_geoservestack so we don't run two backends. The cost-effectiveness rule is simple: keep the calendar overview pre-rendered and only pay for live tiles on the per-day drill-down, cache everything (the ~1,000-day archive is finite and historical), and use vector for admin-1 / raster only for the grid layer.Small starting step: take one event day mdx file, re-publish its page as an MDX file, swap one PNG for a live TiTiler tile of the same date, add one TiPg overlay for the BN admin-1 risk from
bn-ibf · jua-bnet/flood_ibf, and measure cost per page-view. Once that's stable, the per-day pattern scales to the rest of the archive as a markdown edit, not a code change.@Bkoome
All reactions