You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There appears to be a data issue with the information displayed in the "Number of systems in violation" bar graph on the homepage of water.openoakland.org. How this data is generated and displayed should be reviewed.
This issues was noticed by Alissa Rubin
"- it seems for middle chart that the violation count maxes out at a lower number than the violation counts listed below in the spreadsheet, and not all systems in violation are shown? ex, when filtering for arsenic, it says 81 systems are in violation but the chart only goes to 40. I think a more useful way to display this would actually be to have past violation count as the X axis, and then # of systems in violation on the Y axis and have the bars somewhat discreet (aka spaced apart a little bit). A mouseover of each bar might list the systems at the level, or simply show the exact x and y axis numbers for easy reading."
The text was updated successfully, but these errors were encountered:
There appears to be a data issue with the information displayed in the "Number of systems in violation" bar graph on the homepage of water.openoakland.org. How this data is generated and displayed should be reviewed.
This issues was noticed by Alissa Rubin
"- it seems for middle chart that the violation count maxes out at a lower number than the violation counts listed below in the spreadsheet, and not all systems in violation are shown? ex, when filtering for arsenic, it says 81 systems are in violation but the chart only goes to 40. I think a more useful way to display this would actually be to have past violation count as the X axis, and then # of systems in violation on the Y axis and have the bars somewhat discreet (aka spaced apart a little bit). A mouseover of each bar might list the systems at the level, or simply show the exact x and y axis numbers for easy reading."
The text was updated successfully, but these errors were encountered: