-
Notifications
You must be signed in to change notification settings - Fork 92
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
Datasets that need more aggregated columns #846
Comments
It may be worth considering: can these aggregate columns be computed, rather than manually entered? This may depend on the indicator, but presumably any sum or average aggregates could be computed by the platform, which would save work for the data providers. To take an example, the first one: https://sdg.data.gov/2-2-2/ which needs an "all" column. The platform could easily add the 2 types of malnutrition (0.6% wasting and 8.1% overweight) together to get an "all" column of 8.7%. |
Thank you, Brock. I think for the most part, we will need to ask the data providers for the suitable "total" statistic. Some of the categories are not things that conceptually should be totaled--for example, adding wasting and overweight in 2.2.2. I think this is something that Kali could reach out to individual data providers about. |
@JenPark9 Sounds great, thank you! |
Looking forward to the possibility of showing disaggregations on indicators, I notice some datasets need additional aggregated columns. These datasets contain the disaggregated values (which is a great start!) but may be missing some overall sum/average/etc columns. Here is the list I came up with:
@Kali2017SDG I may be off-base with the above, but I think it's worth checking into. Do you have any thoughts? If it helps, I could create each item as a separate Github issue, and we could loop in the data provider for that particular indicator.
The text was updated successfully, but these errors were encountered: