Updates 2024->2025

[norlandrhagen]

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
forest-offsets-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 8, 2025 7:37pm

[katamartin]

Thanks for setting up this PR @norlandrhagen!

Before updating the text, I believe we normally update the data so that we only show fire boundaries starting in 2025 (i.e. none from 2024) -- @badgley is that right?

This also seems like a good time to assess whether we want to save an archival version of the 2024 fires map.

[badgley]

Yes, we need to both "archive previous year" and "update tool for current year."

Updating for 2025 involves two additional tasks:

1. cleaning up the tiles so no 2024 fire boundaries appear
2. updating project boundaries to include any new projects

That's where things get a little delicate — cleaning tiles for 2025 affects "archive previous year". We need to save a final version of the 2024 tiles before we wipe them, otherwise we have to jump through a few more hoops later to recreate the 2024 record. Ideally, these would be separate tasks but given the realities of the code / data the two tasks are intertwined and we should probably tread carefully to minimize headaches around accomplishing both tasks.

I opened #166, which we'll need to resolve before merging.

[katamartin]

Thanks for writing that up @badgley!

I've started to set up the frontend page for the 2024 archive in this PR. So once we're done with the data updates, all we should need to do on the frontend is a simple update of data pointers.