feat: update Observed PM2.5 sensor data

[bodom0015]

Problem

Observed Particulate Matter (PM2.5) data needs to be updated

Fixes #148

Approach

• feat: use new data + metadata links from @jluiuc to display this data in the ChiVes frontend

How to Test

1. Navigate to https://deploy-preview-152--chicago-env-explorer.netlify.app/map
2. From the Variables dropdown, select "Observed Particulate Matter (PM2.5)" from the Air Quality category
   • You should see the data is displayed in the map to the right
   • You should see some overlayed sensor readings appear in the map (do these values need to be updated as well?)
   • You should see some additional controls in the panel, such as "2D or 3D" and "Aggregated by Tract or Source Data"
3. Toggle from "Aggregated by Tract" to "Source Data"
   • You should see that different values now appear in the map
4. Toggle from 2D to 3D
   • You should see the perspective shift slightly to show a 3D rendering of this data on the map

[netlify]

✅ Deploy Preview for chicago-env-explorer ready!

Name	Link
🔨 Latest commit	d16535f
🔍 Latest deploy log	https://app.netlify.com/sites/chicago-env-explorer/deploys/664e209ec55aa300087f3d4b
😎 Deploy Preview	https://deploy-preview-152--chicago-env-explorer.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jluiuc]

It looks like the overlaid sensor readings are from the old data, as they contain values higher than the new data's highest value. Also, I noticed the legend properly shows the true min and max at each end, but in between the value do not match this.

[jluiuc]

It looks like the overlaid sensor readings are from the old data, as they contain values higher than the new data's highest value. Also, while the Aggregated by Tract/Source Data button works, I'm not sure what the differences are from, as I only submitted values aggregated to each tract. Perhaps this is also from the old data? I also noticed the legend properly shows the true min and max at each end, but in between the values do not match this (but the min and max are definitely correct).

[bodom0015]

Hey, @jluiuc! Thank you for bringing these issues up, and sorry for overlooking them in my first attempt 🙏

I removed the old/hardcoded bins - this should fix the Legend at the bottom to display quantile bins 👍

@mradamcox and I are looking into the toggle for "Aggregated vs Source Data" as well as the "Weekly PM2.5" overlay, since they both appear to be using old sensor data as you mentioned. We've tracked down the PM2.5 overlay values to an archived process here. I don't have direct access to the S3 bucket here, so we're trying to figure out the best way to update this data going forward 🤔

[jluiuc]

Great, the legend looks good now! Also, I have the raster from the initial interpolation before aggregating to tracts. Maybe that is what the Aggregated vs Source Data button did? I'm also thinking the number overlays might correlate to each sensor from the previous data. I also have the reading averages and lat/long for each sensor if that is desired.

[bodom0015]

Per @Makosak I've updated the bins + color scale so that they mostly match the other Air Quality variables, despite the differing number of bins:

@jluiuc let me know if there's any other information I can provide that might help with updating the "Source Data" toggle and/or the overlayed sensor values 😄