-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: update Observed PM2.5 sensor data #152
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for chicago-env-explorer ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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).
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 🤔 |
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. |
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 😄 |
…ment-explorer into lambert8/feat/add-pm25-sensor-data
Problem
Observed Particulate Matter (PM2.5) data needs to be updated
Fixes #148
Approach
How to Test