The #30DayChartChallenge is a chart-a-day challenge to encourage creativity, exploration, and community in data visualization. For each day of the month of April, there is a prompt that participants create charts to fit within and share on twitter. Each prompt fits within 5 broader categories: comparisons, distributions, relationships, timeseries, uncertainties. This year's categories will be unveiled in stages as April 1st approaches. See this blog post with the USGS contributions from 2021.
We welcome contributions that highlight science, data, and/or work relevant to USGS. Select the prompt you would like to do, and let us ([email protected] and [email protected]) know. We will allow multiple charts under the same prompt if there is interest from more than one person, or we can help you find a prompt that fits your data/concept if you are unsure.
This repo is to house code and related files for the charts shared via the @USGS_DataSci account. Each chart should have a subdirectory within this repo using the naming convention day_prompt_name (e.g. /01_part-to-whole_cnell) that will be populated with associated files. Submit contributions via pull requests and tag @ceenell (R), @hcorson-dosch (python), or both (javascript/other) as reviewers. Tools and languages outside of those listed in the previous sentence are welcomed, and may or may not make sense to document in this repo.
When you are ready for review, submit a PR with your final chart and a brief description that includes:
- Overall messaging. How does the chart connect to the day/category? What is the 1-2 sentence takeaway?
- The data source and variables used. Where can the data be found? Is it from USGS or elsewhere? Did you do any pre-processing?
- Tools & libraries used
Do not include:
- Data files. Ideally data sources are publicly available and can be pulled in programmatically from elsewhere, like ScienceBase, NWIS, or S3. We will not be distributing previously unreleased datasets. Works-in-progress are great! If you are concerned about sharing your data, let's talk about the best way to appraoch it.
We will review PRs from a design/conceptual/documentation perspective and not necessarily for the data processing and code itself. However, we are happy to engage with you and troubleshoot with you as you develop your chart.