For projects that have multiple categories, numerous edge cases can be hit when rendering charts that group by category. For example, see the charts rendered when specifying category=agriculture:
We should revisit the queries we're using to construct these charting responses to:
Avoid double-counting projects/credits (this is very important)
Only group projects by categories that are included in the category query param list (less crucial, but would prevent the unexpected forest bar showing up in the case above)
For projects that have multiple categories, numerous edge cases can be hit when rendering charts that group by category. For example, see the charts rendered when specifying
category=agriculture
:We should revisit the queries we're using to construct these charting responses to:
category
query param list (less crucial, but would prevent the unexpected forest bar showing up in the case above)