Info exchanges don't issue their own forecasts but want to surface forecasts from neighboring centers. This was part of the original #269 ask, explicitly deferred out of that issue's MVP.
Two pieces
1. Map: surrounding forecast zones in the danger map
Show neighboring centers' forecast zones (e.g., for E Idaho: BTAC, SNFAC, GNFAC, maybe UAC) in the NAC danger-map widget rendered on the homepage.
This is a NAC widget-side feature — Chris/NAC would need to enable cross-center zone rendering in the danger-map widget for the info-exchange center. Per @busbyk in #269: "the surrounding forecast areas being shown on the map is a widgets feature that will have to be enabled on their end."
2. Nav: links to neighboring forecasts
Add neighboring-center forecast links to the info-exchange site's navigation. Lower-tech than #1: each link points to the neighboring center's forecast page (e.g., https://bridgertetonavalanchecenter.org/forecasts/avalanche).
Open design question: a tenant-configurable neighborCenters: relationship[] field on Tenants, or a hardcoded per-tenant table?
Dependencies
Info exchanges don't issue their own forecasts but want to surface forecasts from neighboring centers. This was part of the original #269 ask, explicitly deferred out of that issue's MVP.
Two pieces
1. Map: surrounding forecast zones in the danger map
Show neighboring centers' forecast zones (e.g., for E Idaho: BTAC, SNFAC, GNFAC, maybe UAC) in the NAC danger-map widget rendered on the homepage.
This is a NAC widget-side feature — Chris/NAC would need to enable cross-center zone rendering in the
danger-mapwidget for the info-exchange center. Per @busbyk in #269: "the surrounding forecast areas being shown on the map is a widgets feature that will have to be enabled on their end."2. Nav: links to neighboring forecasts
Add neighboring-center forecast links to the info-exchange site's navigation. Lower-tech than #1: each link points to the neighboring center's forecast page (e.g.,
https://bridgertetonavalanchecenter.org/forecasts/avalanche).Open design question: a tenant-configurable
neighborCenters: relationship[]field onTenants, or a hardcoded per-tenant table?Dependencies