Albert Rapp Profile picture
May 12 24 tweets 11 min read Twitter logo Read on Twitter
The best way to learn data analysis is to actually practice it.

Each week, the #tidyTuesday challenge gives you plenty of opportunity for this.

Don't know how to get started with the challenge? In case you missed it, I've put together an #rstats guide in January.
First, get the data.

Head over to the tidyTuesday's GitHub repo at github.com/rfordatascienc…

Just copy the code from the "Get the data" section. Image
Next, I suggest that you use the clean_names() function from the {janitor} package.

This will format the column names of your data set so that it's easier to work with.

Huge time saver! Image
Now, take a look at the column names of your cleaned data set.

Together with the data dictionary from the GitHub repo, you can find out what the data means. Image
It looks like there are many 'fed_in' variable names in the 'site_data' data set.
Let's take a look at all of them.

select() + Tidyselect helpers will target the right columns Image
This looks weird.
It's only zeroes, ones and NAs.
Probably a true/false kind of thing.

Let's bring more columns into this.
There's `loc_id` and `proj_period_id` as well. Image
This is starting to make sense.

Each feeding site has a unique location and a project id that contains what looks like a year.

Let's check how many project IDs there are. Image
All project IDs contain the same prefix.

Let's remove it and transform the character vector into an actual numeric vector.

`parse_number()` can take care of that. Image
Next, we're going to take care of missing values.

Let's have a look how many missing values there are.

Here are two ways to do that:
1️⃣ summarise() + across()
2️⃣ for-loop ImageImage
There is missing data. Let’s filter those that have missing data in any of the month columns.

The `fed_yr_round` column can be filled by us later on.

Once again, here are two possible ways:
1️⃣ pmap() from {purrr}
2️⃣ rowSums() (treating TRUE as 1) ImageImage
Now, let us bring our data into a tidy format.

That’s what `pivot_longer()` will do for us. Image
Next, we’re able to do a little bit of counting.

This is always an easy but valuable thing to do. Just throw count() at the data to see what's (and how much) is in it. Image
Using these counts we can check how many sites there are in each year.

Looks like overall the number of sites increased over the years.

This plot was just something we did for ourselves. No need to customize it further. ImageImage
Finally, let’s have a look at how many feeding sites feed all-year.

Maybe over time more or maybe less bird sites are active every month.

As it happens, it looks like there is a trend that more and more bird sites are active every month. Let’s make this viz a bit prettier. ImageImage
First, let’s apply `theme_minimal()` and make the bars wider. Also, black borders for the bars could be nice. ImageImage
Second, add labels. Add a descriptive title and don’t forget to put your Twitter handle into the caption. ImageImage
Third, let us format the y-axis as percent. ImageImage
Fourth, pick better colors manually. ImageImage
Fifth, get rid of the extra spacing surrounding the bars. ImageImage
Finally, move the legend and title. ImageImage
There’s lots more one can do with the data or the plot. But this is probably okay as a start.

At this point, you can share your plot on Twitter using the #tidyTuesday hashtag.
If you share your plot, think about sharing your code as well.

Common practices for sharing the code:
- A dedicated tidyTuesday repo on Github.
OR
- Upload the code at gist.github.com.

This thread's code is available at github.com/AlbertRapp/Pub…
I hope this helps you to get started with the tidyTuesday challenge.

If you want more help, check out the R screencasts rscreencasts.com.

They're a great resource on learning data wrangling using tidyTuesday data sets.
That's a wrap. I hope you've enjoyed this thread.

If you want to see more content like this, follow @rappa753.

See you next time 👋

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Albert Rapp

Albert Rapp Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @rappa753

May 5
I used to think tables are boring.

But they can be beautiful & engaging.

Here's a nice example from @infobeautiful.

It uses many eye-catching elements but you don't need them to create a great table.

Just stick to these guidelines 🧵#dataviz A huge table describing wha...
Let's start with a not so great table and improve it.

Here's a table I would have created just a few months ago.

Not so sexy, right? Let's clean that up. Image
1. Avoid vertical lines

The above table uses waaaay to many grid lines.

Without vertical lines, the table will look less cramped.

Have a look for yourself. Image
Read 16 tweets
Apr 28
I hate code duplication. It's just a sure way to bloat code and do copy-and-paste mistakes 🙈

In Shiny, modules help me to avoid that.

BONUS: They move the app's logic to separate + reusable functions for cleaner code.

Here's how modules work. #rstats
Let's build an app that displays a scatterplot of two variables of a given data set.

Let's imagine that each data set needs its own page in our app. Here's how that could look. ImageImage
Every element of our app will need to get a unique ID. And we will need to repeat that for every data set.

For two data sets a non-modularized Shiny UI could look something like this.

Notice how I have to append "_iris" each time for the second tabPanel / data set. Image
Read 11 tweets
Apr 4
Paired bar charts suck at comparing values. The only reason they're used all the time is because they are easy to create.

But there are better alternatives that are just as easy.

Here's how to create 4 better alternatives with #rstats.
0 // Where's the code?

The code for all plots can be found at albert-rapp.de/posts/ggplot2-…

This thread walks you through the code quickly.
1 // Dot plot

Instead of using bars next to each other, why not points on the same line?

Makes comparison suuper easy.

And it takes only a geom_point() layer. Dead-simple, right?

I think it's even easier to create than a paired bar chart.
Read 15 tweets
Mar 31
Tired of lackluster visualizations that don't tell you anything?

Discover how storytelling and nuanced color use can
- transform your bar charts.
- inform readers on key insights & actions

Here's a step-by-step guide (with full code at the end). #rstats
Here's our starting point.

Note that this tutorial is a ggplot2 recreation of

(And once you've mastered the technique you can enhance this visual with advanced stats beyond comparing error rates to average.)
// Labels on y-axis

First, move the names to the y-axis.

This is important when the labels are real names instead of IDs.

No one likes to tilt their head for reading.
Read 19 tweets
Mar 29
Data visualization doesn't have to be complicated. 🤯

In fact, ggplot makes it dead-simple to implement some of the most effective dataviz principles.

Here are six dataviz principles that are so easy that any beginner’s course should teach them. #rstats
1 // Make sure your labels are legible

This one is super easy to fix. Any beginner can do it.

Img 1: Way too small fonts & unclear labels
Img 2: Fixed with labs() and theme_gray(base_size = 20)
Img 3: Full code ImageImageImage
2 // Use a minimal theme

As a rule of thumb, you should minimize everything that could potentially distract your audience.

That’s why I usually recommend to use a minimal theme: Just use `theme_minimal()` instead of `theme_gray()`. Image
Read 9 tweets
Mar 25
Manually sifting through mountains of data is annoying. 🥱

But with the point & click interface of analytics dashboards, data exploration is more fun.

And building a dashboard is simple too, especially with R & Shiny. Here's how to get started now. #rstats
1 // Data

First, you need data.

It's always fun to work with your personal data, so I will use my the last three months of my Twitter analytics data. You can download yours at analytics.twitter.com
2 // Data cleaning

Next, do a bit of data cleaning. In my case, I just have to clean the column names and select a few columns.

{janitor} and {dplyr} make that easy.
Read 13 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(