Modifies expected locations for current fire, lightning strike, and VIIRS hotspot data

Introduction This PR incorporates the changes made for the fire season in 2024, which includes getting rid of the fire shim code and the PostGIS database holding the recent lightning strikes in the state.

The three layers in question: Wildfires, Hotspots, last 48 hours, and Lightning strikes, last 36 hours have all been changed to be updated via Prefect using a script that generates shapefiles for each of these layers from their live remote sources that contain the necessary metadata properties to show acreage of a fire or amplitude of a lightning strike for example. For more information about how this is accomplished, go here to view the PR associated with that work.

For two of these layers (fire and VIIRS), a crafted WFS request is sent to the Geoserver instance that returns GeoJSON to be displayed on the map, while the lightning strikes are a WMS call that has a styling guide for how to return the lightning strikes based on their amplitude.

Lightning Strike Legend

Testing This can be tested locally by running this with npm. I currently am using lts/gallium so run the following: nvm use lts/gallium npm install npm run server

This will start up the local Node server and you can view the three layers.

What you should expect to see are a number of wildfire points and polygons with the ability to click on them to get more information about them (note these are from October 2023, so are not accurate for today), 3 lightning strikes that I spoofed that because they are from so long ago (48+ hours), their opacity is as low as it goes while still being visible, and several hot spots that were also spoofed from last year's data to show that the data layers are properly shown when coming from our production Geoserver instance.

As always, please ask questions if anything doesn't make sense!

ua-snap / alaska-wildfires

Modifies expected locations for current fire, lightning strike, and VIIRS hotspot data #51