Conversation
✅ Deploy Preview for gbof-c19nyc-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for juel-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for registro-project ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for padp-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for universities-studying-slavery-staging ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for juel-ancestry ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for pss-scavenger-hunt ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for libertos ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for juel-life ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
…-data-places into feature/cdp428_preload_map
This pull request implements the ability to preload map data at build time. This is particularly useful for projects which use large spatial data sets.
Note: This pull request is dependent on a release of
peripleoandreact-components. I figured I'd open the PR and set it as a draft to get eyes on it while those releases are in progress.Screen.Recording.2026-01-28.at.3.05.03.PM.mov
The change introduces a new environment variable,
PRELOAD_MAP. If set totrue, at build time we will fetch the geometry data and store it in the Astro content layer (separate from the Place data). At request time, each item on the map will load the geometry data from an Astro endpoint. This reduces the memory load on the browser.If we're preloading map data, all items on the map will be rendered as individual layers, as opposed to a single GeoJSON layer. As a results, there is a work-around in
MapSearchContextProviderto calculate the bounding box for the visible layers.