Learning Objectives
- Describe the purpose of the
dplyrandtidyrpackages.
- Select certain columns in a data frame with the
dplyrfunctionselect().
- Select certain rows in a data frame according to filtering conditions with the
dplyrfunctionfilter().
- Link the output of one
dplyrfunction to the input of another function with the ‘pipe’ operator%>%.
- Add new columns to a data frame that are functions of existing columns with
mutate().
- Use the split-apply-combine concept for data analysis.
- Use
summarize(),group_by(), andcount()to split a data frame into groups of observations, apply summary statistics for each group, and then combine the results.
- Describe the concept of a wide and a long table format and for which purpose those formats are useful.
- Describe what key-value pairs are.
- Reshape a data frame from long to wide format and back with the
pivot_wider()andpivot_longer()commands from thetidyrpackage.
- Export a data frame to a .csv file.
Open your Environmental Data Analysis project, and create a new script named “A6_DataWrangling”.
dplyr and tidyrBracket subsetting is handy, but it can be cumbersome and difficult
to read, especially for complicated operations. Enter
dplyr. dplyr is a package for making tabular
data wrangling easier. It pairs nicely with tidyr, which
enables you to swiftly convert between different data formats for
plotting and analysis.
Packages in R are basically sets of additional functions that let you
do more stuff. The functions we’ve been using so far, like
str() or data.frame(), come built into R;
packages give you access to more of them. Before you use a package for
the first time you need to install it on your machine, and then you
should import it in every subsequent R session when you need it. We have
already installed the tidyverse package. This is an
“umbrella-package” that installs several packages useful for data
analysis which work together well such as tidyr,
dplyr, ggplot2, tibble, etc.
The tidyverse package tries to address 3 common issues
that arise when doing data analysis with some of the functions that come
with R:
To load the package type:
# load the tidyverse packages, including dplyr
library(tidyverse)
dplyr and tidyr?The package dplyr provides easy tools for the most
common data wrangling tasks. It is built to work directly with data
frames, with many common tasks optimized by being written in a compiled
language (C++). An additional feature is the ability to work directly
with data stored in an external database. The benefits of doing this are
that the data can be managed natively in a relational database, queries
can be conducted on that database, and only the results of the query are
returned.
This addresses a common problem with R in that all operations are conducted in-memory and thus the amount of data you can work with is limited by available memory. The database connections essentially remove that limitation in that you can connect to a database of many hundreds of GB, conduct queries on it directly, and pull back into R only what you need for analysis. This includes “big data” datasets as well as spatial data.
The package tidyr addresses the common problem of
wanting to reshape your data for plotting and use by different R
functions. Sometimes we want data sets where we have one row per
measurement. Sometimes we want a data frame where each measurement type
has its own column, and rows are instead more aggregated groups - like
plots or aquaria. Moving back and forth between these formats is
nontrivial, and tidyr gives you tools for this and more
sophisticated data reshaping.
To learn more about dplyr and tidyr after
the workshop, or to refresh your memory in the future, you may consult
the cheatsheets for dplyr and tidyr available
on the course Brightspace page.
We’ll read in our data using the read_csv() function,
from the tidyverse package readr, instead of
read.csv(). If you do not have the data_raw
folder with the data that we set up earlier in the semester, you can
access the “portal_data_joined.csv” data directly from the course
Brightspace page and set up a new data_raw folder.
# Import data file
surveys <- read_csv("data_raw/portal_data_joined.csv")
## Rows: 34786 Columns: 13
## ── Column specification ────────────────────────────────────────────────────────
## Delimiter: ","
## chr (6): species_id, sex, genus, species, taxa, plot_type
## dbl (7): record_id, month, day, year, plot_id, hindfoot_length, weight
##
## ℹ Use `spec()` to retrieve the full column specification for this data.
## ℹ Specify the column types or set `show_col_types = FALSE` to quiet this message.
# Inspect the data
str(surveys)
# Call data table as a new tab
View(surveys)
Notice that the class of the data is tbl_df.
This is referred to as a “tibble”. Tibbles tweak some of the behaviors of the data frame objects we introduced in the “Starting with Data” workshop. The data structure is very similar to a data frame. For our purposes the only differences are that:
We’re going to learn some of the most common dplyr
functions:
select(): subset columnsfilter(): subset rows on conditionsmutate(): create new columns by using information from
other columnsgroup_by() and summarize(): create summary
statistics on grouped dataarrange(): sort resultscount(): count discrete valuesTo select columns of a data frame, use select(). The
first argument to this function is the data frame surveys,
and the subsequent arguments are the columns to keep.
select(surveys, plot_id, species_id, weight)
To select all columns except certain ones, put a “-” in front of the variable to exclude it.
select(surveys, -record_id, -species_id)
This will select all the variables in surveys except
record_id and species_id.
To choose rows based on a specific criterion, use
filter().
filter(surveys, year == 1995)
What if you want to select and filter at the same time? There are three ways to do this: use intermediate steps, nested functions, or pipes.
With intermediate steps, you create a temporary data frame and use that as input to the next function, like this:
surveys2 <- filter(surveys, weight < 5)
surveys_sml <- select(surveys2, species_id, sex, weight)
This is readable, but can clutter up your work space with lots of objects that you have to name individually. (I also tend to run out of creativity after two or three object names.) With multiple steps, all the new object names can also be hard to keep track of.
You can also nest functions (i.e., one function inside of another), like this:
surveys_sml <- select(filter(surveys, weight < 5), species_id, sex, weight)
This is handy, but can be difficult to read if too many functions are nested, as R evaluates the expression from the inside out (in this case, filtering, then selecting).
The last option, pipes, is a more recent addition to
R. Pipes let you take the output of one function and send it directly to
the next, which is useful when you need to do many things to the same
dataset. Pipes in R look like %>% and are made available
via the magrittr package, installed automatically with
dplyr. If you use RStudio, you can type the pipe with
Ctrl + Shift + M if you have a PC
or Cmd + Shift + M if you have a
Mac.
surveys %>%
filter(weight < 5) %>%
select(species_id, sex, weight)
In the above code, we use the pipe to send the surveys
dataset first through filter() to keep rows where weight is
less than 5, then through select() to keep only the
species_id, sex, and weight
columns. Since %>% takes the object on its left and
passes it as the first argument to the function on its right, we don’t
need to explicitly include the data frame as an argument to the
filter() and select() functions any more.
Some may find it helpful to read the pipe like the word “then”. For
instance, in the above example, we took the data frame
surveys, then we filtered for rows with
weight < 5, then we selected columns
species_id, sex, and weight. The
dplyr functions by themselves are somewhat simple, but by
combining them into linear workflows with the pipe, we can accomplish
more complex wrangling of data frames.
If we want to create a new object with this smaller version of the data, we can assign it a new name:
# Create new tibble object
surveys_sml <- surveys %>%
filter(weight < 5) %>%
select(species_id, sex, weight)
# View first few rows of new tibble
head(surveys_sml)
## # A tibble: 6 × 3
## species_id sex weight
## <chr> <chr> <dbl>
## 1 PF F 4
## 2 PF F 4
## 3 PF M 4
## 4 RM F 4
## 5 RM M 4
## 6 PF <NA> 4
Note that the final data frame is the leftmost part of this expression.
Challenge 1
Using pipes, subset the
surveysdata to include animals collected before 1995 and retain only the columnsyear,sex, andweight. Save the new tibble as an object namedsurveys_1995.
How many columns are in thesurveys_1995tibble?
How many rows are in thesurveys_1995tibble?
# Create new tibble
surveys_1995 <- surveys %>%
filter(year < 1995) %>%
select(year, sex, weight)
# Inspect tibble
str(surveys_1995)
## tibble [21,486 × 3] (S3: tbl_df/tbl/data.frame)
## $ year : num [1:21486] 1977 1977 1977 1977 1977 ...
## $ sex : chr [1:21486] "M" "M" NA NA ...
## $ weight: num [1:21486] NA NA NA NA NA NA NA NA 218 NA ...
Frequently you’ll want to create new “calculated” columns based on
the values in existing columns, for example to do unit conversions, or
to find the ratio of values in two columns. For this we’ll use
mutate().
To create a new column of weight in kg:
surveys %>%
mutate(weight_kg = weight / 1000)
You can also create a second new column based on the first new column
within the same call of mutate():
surveys %>%
mutate(weight_kg = weight / 1000,
weight_lb = weight_kg * 2.2)
If this runs off your screen and you just want to see the first few
rows, you can use a pipe to view the head() of the data.
(Pipes work with non-dplyr functions, too, as long as the
dplyr or magrittr package is loaded).
surveys %>%
mutate(weight_kg = weight / 1000) %>%
head()
The first few rows of the output are full of NAs, so if
we wanted to remove those we could insert a filter() in the
chain:
surveys %>%
filter(!is.na(weight)) %>%
mutate(weight_kg = weight / 1000) %>%
head()
is.na() is a function that determines whether something
is an NA. The ! symbol negates the result, so
we’re asking for every row where weight is not an
NA.
Challenge 2
Create a new data frame from the
surveysdata that meets the following criteria: contains only thespecies_idcolumn and a new column calledhindfoot_halfcontaining values that are half thehindfoot_lengthvalues. In thishindfoot_halfcolumn, there are noNAs and all values are less than 30.Hint: think about how the commands should be ordered to produce this data frame!
How many columns are in your new dataframe?
How many rows are in your new dataframe?
What type of variable isspecies_id?
# either
surveys_hindfoot_half <- surveys %>%
mutate(hindfoot_half = hindfoot_length / 2) %>%
filter(!is.na(hindfoot_half)) %>%
filter(hindfoot_half < 30) %>%
select(species_id, hindfoot_half)
# or
surveys_hindfoot_half <- surveys %>%
filter(!is.na(hindfoot_length)) %>%
mutate(hindfoot_half = hindfoot_length / 2) %>%
filter(hindfoot_half < 30) %>%
select(species_id, hindfoot_half)
# inspect new data frame
str(surveys_hindfoot_half)
## tibble [31,436 × 2] (S3: tbl_df/tbl/data.frame)
## $ species_id : chr [1:31436] "NL" "NL" "NL" "NL" ...
## $ hindfoot_half: num [1:31436] 16 15.5 16 17 16 16.5 16 16 16.5 15 ...
Many data analysis tasks can be approached using the
split-apply-combine paradigm: split the data into groups, apply
some analysis to each group, and then combine the results.
dplyr makes this very easy through the use of the
group_by() function.
group_by() is often used together with
summarize(), which collapses each group into a single-row
summary of that group. group_by() takes as arguments the
column names that contain the categorical variables for which you want
to calculate the summary statistics. So to compute the mean weight by
sex:
surveys %>%
group_by(sex) %>%
summarize(mean_weight = mean(weight, na.rm = T))
You may also have noticed that the output from these calls doesn’t run off the screen anymore. It’s one of the advantages of tbl_df over data frame.
You can also group by multiple columns:
surveys %>%
group_by(sex, species_id) %>%
summarize(mean_weight = mean(weight, na.rm = T))
When grouping both by sex and species_id,
the last few rows are for animals that escaped before their sex and body
weights could be determined. You may notice that the last column does
not contain NA but NaN (which refers to “Not a
Number”). To avoid this, we can remove the missing values for weight
before we attempt to calculate the summary statistics on weight. Because
the missing values are removed first, we can omit
na.rm = TRUE when computing the mean:
surveys %>%
filter(!is.na(weight)) %>%
group_by(sex, species_id) %>%
summarize(mean_weight = mean(weight))
Here, again, the output from these calls doesn’t run off the screen
anymore. If you want to display more data, you can use the
print() function at the end of your chain with the argument
n specifying the number of rows to display:
surveys %>%
filter(!is.na(weight)) %>%
group_by(sex, species_id) %>%
summarize(mean_weight = mean(weight)) %>%
print(n = 64)
Once the data are grouped, you can also summarize multiple variables at the same time (and not necessarily on the same variable). For instance, we could add a column indicating the minimum weight for each species for each sex:
surveys %>%
filter(!is.na(weight)) %>%
group_by(sex, species_id) %>%
summarize(mean_weight = mean(weight),
min_weight = min(weight))
It is sometimes useful to rearrange the result of a query to inspect the values. For instance, we can sort on min_weight to put the lighter species first:
surveys %>%
filter(!is.na(weight)) %>%
group_by(sex, species_id) %>%
summarize(mean_weight = mean(weight),
min_weight = min(weight)) %>%
arrange(min_weight)
To sort in descending order, we need to add the desc()
function. If we want to sort the results by decreasing order of mean
weight:
surveys %>%
filter(!is.na(weight)) %>%
group_by(sex, species_id) %>%
summarize(mean_weight = mean(weight),
min_weight = min(weight)) %>%
arrange(desc(mean_weight))
When working with data, we often want to know the number of
observations found for each factor or combination of factors. For this
task, dplyr provides count(). For example, if
we wanted to count the number of rows of data for each sex, we would
do:
surveys %>%
count(sex)
The count() function is shorthand for something we’ve
already seen: grouping by a variable, and summarizing it by counting the
number of observations in that group. In other words,
surveys %>% count() is equivalent to:
surveys %>%
group_by(sex) %>%
summarize(count = n())
For convenience, count() provides the sort
argument:
surveys %>%
count(sex, sort = T)
Previous example shows the use of count() to count the
number of rows/observations for one factor (i.e.,
sex). If we wanted to count combination of factors, such as
sex and species, we would specify the first
and the second factor as the arguments of count():
surveys %>%
count(sex, species)
With the above code, we can proceed with arrange() to
sort the table according to a number of criteria so that we have a
better comparison. For instance, we might want to arrange the table
above in (i) an alphabetical order of the levels of the species and (ii)
in descending order of the count:
surveys %>%
count(sex, species) %>%
arrange(species, desc(n))
From the table above, we may learn that, for instance, there are 75
observations of the albigula species that are not specified for
its sex (i.e., NA).
Challenge 3
1. How many animals were caught in each
plot_typesurveyed?
surveys %>%
count(plot_type)
## # A tibble: 5 × 2
## plot_type n
## <chr> <int>
## 1 Control 15611
## 2 Long-term Krat Exclosure 5118
## 3 Rodent Exclosure 4233
## 4 Short-term Krat Exclosure 5906
## 5 Spectab exclosure 3918
2. Use
group_by()andsummarize()to find the mean, min, and max hindfoot length for each species (usingspecies_id). Also add the number of observations (hint: see?n).
What are the values for the first two species?
surveys %>%
filter(!is.na(hindfoot_length)) %>%
group_by(species_id) %>%
summarize(mean_hindfoot_length = mean(hindfoot_length),
min_hindfoot_length = min(hindfoot_length),
max_hindfoot_length = max(hindfoot_length),
n = n())
## # A tibble: 25 × 5
## species_id mean_hindfoot_length min_hindfoot_length max_hindfoot_length n
## <chr> <dbl> <dbl> <dbl> <int>
## 1 AH 33 31 35 2
## 2 BA 13 6 16 45
## 3 DM 36.0 16 50 9972
## 4 DO 35.6 26 64 2887
## 5 DS 49.9 39 58 2132
## 6 NL 32.3 21 70 1074
## 7 OL 20.5 12 39 920
## 8 OT 20.3 13 50 2139
## 9 OX 19.1 13 21 8
## 10 PB 26.1 2 47 2864
## # ℹ 15 more rows
3. What was the heaviest animal measured in each year?
Return the columnsyear,genus,species_id, andweight.
Based on your new tibble, what was thespecies_idfor the heaviest animal in 1977?
Based on your new tibble, what was thespecies_idfor the heaviest animal in 1979?
surveys %>%
filter(!is.na(weight)) %>%
group_by(year) %>%
filter(weight == max(weight)) %>%
select(year, genus, species_id, weight) %>%
arrange(year)
## # A tibble: 27 × 4
## # Groups: year [26]
## year genus species_id weight
## <dbl> <chr> <chr> <dbl>
## 1 1977 Dipodomys DS 149
## 2 1978 Neotoma NL 232
## 3 1978 Neotoma NL 232
## 4 1979 Neotoma NL 274
## 5 1980 Neotoma NL 243
## 6 1981 Neotoma NL 264
## 7 1982 Neotoma NL 252
## 8 1983 Neotoma NL 256
## 9 1984 Neotoma NL 259
## 10 1985 Neotoma NL 225
## # ℹ 17 more rows
pivot_longer() and
pivot_wider()In the spreadsheet lesson, we discussed how to structure our data leading to the four rules defining a tidy dataset:
Here we examine the fourth rule: Each type of observational unit forms a table.
In surveys, the rows of surveys contain the
values of variables associated with each record (the unit), values such
as the weight or sex of each animal associated with each record. What if
instead of comparing records, we wanted to compare the different mean
weight of each species between plots? (Ignoring plot_type
for simplicity).
We’d need to create a new table where each row (the unit) is
comprised of values of variables associated with each plot. In practical
terms this means the values of the species in genus would
become the names of column variables and the cells would contain the
values of the mean weight observed on each plot.
Having created a new table, it is therefore straightforward to
explore the relationship between the weight of different species within,
and between, the plots. The key point here is that we are still
following a tidy data structure, but we have reshaped the
data according to the observations of interest: average species weight
per plot instead of recordings per date.
The opposite transformation would be to transform column names into values of a variable.
We can do both these of transformations with two tidyr
functions, pivot_wider() and
pivot_longer().
pivot_wider() takes three principle arguments:
Further arguments include values_fill, which, if set,
fills in missing values with the value provided (e.g. 0 or
NA).
Let’s use pivot_wider() to transform surveys to find the
mean weight of each species in each plot over the entire survey period.
We use filter(), group_by() and
summarise() to filter our observations and variables of
interest, and create a new variable for the mean_weight. We
use the pipe as before too.
surveys_gw <- surveys %>%
filter(!is.na(weight)) %>%
group_by(genus, plot_id) %>%
summarize(mean_weight = mean(weight))
head(surveys_gw)
## # A tibble: 6 × 3
## # Groups: genus [1]
## genus plot_id mean_weight
## <chr> <dbl> <dbl>
## 1 Baiomys 1 7
## 2 Baiomys 2 6
## 3 Baiomys 3 8.61
## 4 Baiomys 5 7.75
## 5 Baiomys 18 9.5
## 6 Baiomys 19 9.53
This yields surveys_gw where the observations for each
plot are spread across multiple rows, 196 observations of 3 variables.
If we use pivot_wider() to create a new column for each
genus, containing values from mean_weight this becomes 24
observations of 11 variables, one row for each plot. We again use
pipes:
surveys_wide <- surveys_gw %>%
pivot_wider(names_from = "genus", values_from = "mean_weight")
head(surveys_wide)
## # A tibble: 6 × 11
## plot_id Baiomys Chaetodipus Dipodomys Neotoma Onychomys Perognathus Peromyscus
## <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl>
## 1 1 7 22.2 60.2 156. 27.7 9.62 22.2
## 2 2 6 25.1 55.7 169. 26.9 6.95 22.3
## 3 3 8.61 24.6 52.0 158. 26.0 7.51 21.4
## 4 5 7.75 18.0 51.1 190. 27.0 8.66 21.2
## 5 18 9.5 26.8 61.4 149. 26.6 8.62 21.4
## 6 19 9.53 26.4 43.3 120 23.8 8.09 20.8
## # ℹ 3 more variables: Reithrodontomys <dbl>, Sigmodon <dbl>, Spermophilus <dbl>
We may wish to fill in the missing values using
values_fill = 0.
surveys_gw %>%
pivot_wider(names_from = "genus", values_from = "mean_weight", values_fill = 0) %>%
head()
The opposing situation could occur if we had been provided with data
in the form of surveys_wide, where the genus names are
column names, but we wish to treat them as values of a genus variable
instead.
In this situation we are gathering the column names and turning them into a pair of new variables. One variable represents the column names as values, and the other variable contains the values previously associated with the column names.
pivot_longer() takes four principal arguments:
- to exclude
columnsTo recreate surveys_gw from surveys_wide we
would create a new column called genus and a value column
called mean_weight and pivot all columns except
plot_id (or columns 2 through 11). Here we drop
plot_id column with a minus sign.
# Pivot all columns except plot_id
surveys_long <- surveys_wide %>%
pivot_longer(names_to = "genus", values_to = "mean_weight", -plot_id)
head(surveys_long)
## # A tibble: 6 × 3
## plot_id genus mean_weight
## <dbl> <chr> <dbl>
## 1 1 Baiomys 7
## 2 1 Chaetodipus 22.2
## 3 1 Dipodomys 60.2
## 4 1 Neotoma 156.
## 5 1 Onychomys 27.7
## 6 1 Perognathus 9.62
Note that now the NA genera are included in the
re-gathered format. Pivoting wider and then pivoting longer can be a
useful way to balance out a dataset so every replicate has the same
composition.
We could also have used a specification for what columns to include.
This can be useful if you have a large number of identifying columns,
and it’s easier to specify what to pivot than what to leave alone. And
if the columns are in a row, we don’t even need to list them all out.
Just use the : operator! You can refer to columns by name
or by column number.
# Pivot columns by name
surveys_wide %>%
pivot_longer(names_to = "genus", values_to = "mean_weight", Baiomys:Spermophilus) %>%
head()
# Pivot columns 2 through 11
surveys_wide %>%
pivot_longer(names_to = "genus", values_to = "mean_weight", 2:11) %>%
head()
## # A tibble: 6 × 3
## plot_id genus mean_weight
## <dbl> <chr> <dbl>
## 1 1 Baiomys 7
## 2 1 Chaetodipus 22.2
## 3 1 Dipodomys 60.2
## 4 1 Neotoma 156.
## 5 1 Onychomys 27.7
## 6 1 Perognathus 9.62
Challenge 4
1.Pivot the
surveysdata frame wider, withyearas columns,plot_idas rows, and the number of genera per plot as the values. You will need to summarize before reshaping, and use the functionn_distinct()to get the number of unique genera within a particular chunk of data. It’s a powerful function! See?n_distinctfor more. Save your new data frame as objectrich_time.
How many rows are in your data frame?
How many columns are in your data frame?
How many genera were present in plot 1 in 1985?
# Create new data frame
rich_time <- surveys %>%
group_by(year, plot_id) %>%
summarize(n_genera = n_distinct(genus)) %>%
pivot_wider(names_from = "year", values_from = "n_genera")
# View new data frame
rich_time
## # A tibble: 24 × 27
## plot_id `1977` `1978` `1979` `1980` `1981` `1982` `1983` `1984` `1985` `1986`
## <dbl> <int> <int> <int> <int> <int> <int> <int> <int> <int> <int>
## 1 1 2 3 4 7 5 6 7 6 4 3
## 2 2 6 6 6 8 5 9 9 9 6 4
## 3 3 5 6 4 6 6 8 10 11 7 6
## 4 4 4 4 3 4 5 4 6 3 4 3
## 5 5 4 3 2 5 4 6 7 7 3 1
## 6 6 3 4 3 4 5 9 9 7 5 6
## 7 7 3 1 3 1 1 4 2 3 4 3
## 8 8 2 4 3 5 6 6 4 6 4 3
## 9 9 3 3 3 4 5 6 7 4 5 3
## 10 10 1 NA 2 5 5 8 4 2 3 1
## # ℹ 14 more rows
## # ℹ 16 more variables: `1987` <int>, `1988` <int>, `1989` <int>, `1990` <int>,
## # `1991` <int>, `1992` <int>, `1993` <int>, `1994` <int>, `1995` <int>,
## # `1996` <int>, `1997` <int>, `1998` <int>, `1999` <int>, `2000` <int>,
## # `2001` <int>, `2002` <int>
2. Now take that data frame and
pivot_longer(), so each row is a uniqueplot_idbyyearcombination.
How many rows are in the data frame?
How many columns are in the data frame?
rich_time %>%
pivot_longer(names_to = "year", values_to = "n_genera", -plot_id)
## # A tibble: 624 × 3
## plot_id year n_genera
## <dbl> <chr> <int>
## 1 1 1977 2
## 2 1 1978 3
## 3 1 1979 4
## 4 1 1980 7
## 5 1 1981 5
## 6 1 1982 6
## 7 1 1983 7
## 8 1 1984 6
## 9 1 1985 4
## 10 1 1986 3
## # ℹ 614 more rows
3.The surveys data set has two measurement columns:
hindfoot_lengthandweight. This makes it difficult to do things like look at the relationship between mean values of each measurement per year in different plot types. Let’s walk through a common solution for this type of problem. First, usepivot_longer()to create a dataset where we have a name column calledmeasurementthat specifies the type of measurement and a value column that takes on the value of eitherhindfoot_lengthorweight. Hint: You’ll need to specify which columns are being gathered. Save your new dataframe as objectsurveys_long.
How many rows are in thesurveys_longdata frame?
How many columns are in thesurveys_longdata frame?
# Create data frame
surveys_long <- surveys %>%
pivot_longer(names_to = "measurement", values_to = "value", c(hindfoot_length, weight))
#View data frame
surveys_long
## # A tibble: 69,572 × 13
## record_id month day year plot_id species_id sex genus species taxa
## <dbl> <dbl> <dbl> <dbl> <dbl> <chr> <chr> <chr> <chr> <chr>
## 1 1 7 16 1977 2 NL M Neotoma albigula Rodent
## 2 1 7 16 1977 2 NL M Neotoma albigula Rodent
## 3 72 8 19 1977 2 NL M Neotoma albigula Rodent
## 4 72 8 19 1977 2 NL M Neotoma albigula Rodent
## 5 224 9 13 1977 2 NL <NA> Neotoma albigula Rodent
## 6 224 9 13 1977 2 NL <NA> Neotoma albigula Rodent
## 7 266 10 16 1977 2 NL <NA> Neotoma albigula Rodent
## 8 266 10 16 1977 2 NL <NA> Neotoma albigula Rodent
## 9 349 11 12 1977 2 NL <NA> Neotoma albigula Rodent
## 10 349 11 12 1977 2 NL <NA> Neotoma albigula Rodent
## # ℹ 69,562 more rows
## # ℹ 3 more variables: plot_type <chr>, measurement <chr>, value <dbl>
4. With this new data set, calculate the average of each
measurementin eachyearfor each differentplot_type. Thenpivot_wider()into a data set with a column forhindfoot_lengthandweight. Hint: You only need to specify the names_from and values_from columns forpivot_wider().
How many rows are in the new data frame?
How many columns are in the new data frame?
What was the mean weight of individuals captured in control plots in 1978?
surveys_long %>%
group_by(year, measurement, plot_type) %>%
summarize(mean = mean(value, na.rm = T)) %>%
pivot_wider(names_from = "measurement", values_from = "mean")
## # A tibble: 130 × 4
## # Groups: year [26]
## year plot_type hindfoot_length weight
## <dbl> <chr> <dbl> <dbl>
## 1 1977 Control 36.1 50.4
## 2 1977 Long-term Krat Exclosure 33.7 34.8
## 3 1977 Rodent Exclosure 39.1 48.2
## 4 1977 Short-term Krat Exclosure 35.8 41.3
## 5 1977 Spectab exclosure 37.2 47.1
## 6 1978 Control 38.1 70.8
## 7 1978 Long-term Krat Exclosure 22.6 35.9
## 8 1978 Rodent Exclosure 37.8 67.3
## 9 1978 Short-term Krat Exclosure 36.9 63.8
## 10 1978 Spectab exclosure 42.3 80.1
## # ℹ 120 more rows
Now that you have learned how to use dplyr to extract
information from or summarize your raw data, you may want to export
these new data sets to share them with your collaborators or for
archival.
Similar to the read_csv() function used for reading CSV
files into R, there is a write_csv() function that
generates CSV files from data frames.
Before using write_csv(), we are going to create a new
folder, data, in our working directory that will store
this generated dataset. We don’t want to write generated datasets in the
same directory as our raw data. It’s good practice to keep them
separate. The data_raw folder should only contain the
raw, unaltered data, and should be left alone to make sure we don’t
delete or modify it. In contrast, our script will generate the contents
of the data directory, so even if the files it contains
are deleted, we can always re-generate them.
In preparation for our next lesson on plotting, we are going to prepare a cleaned up version of the data set that doesn’t include any missing data.
Let’s start by removing observations of animals for which
weight and hindfoot_length are missing, or the
sex has not been determined:
surveys_complete <- surveys %>%
filter(!is.na(weight),
!is.na(hindfoot_length),
!is.na(sex))
Because we are interested in plotting how species abundances have changed through time, we are also going to remove observations for rare species (i.e., that have been observed less than 50 times). We will do this in two steps: first we are going to create a data set that counts how often each species has been observed, and filter out the rare species; then, we will extract only the observations for these more common species:
# Extract the most common species_id
species_counts <- surveys_complete %>%
count(species_id) %>%
filter(n >= 50)
# Keep only the most common species
surveys_complete <- surveys_complete %>%
filter(species_id %in% species_counts$species_id)
To make sure that everyone has the same data set, check that
surveys_complete has 30463 rows and 13 columns by typing
dim(surveys_complete).
dim(surveys_complete)
## [1] 30463 13
Now that our data set is ready, we can save it as a CSV file in our data folder.
write_csv(surveys_complete, path = "data/surveys_complete.csv")
Okay, this was a lot! Fortunately, you do not need to memorize all
the functions at once. You can always refer back to this lesson or to
the dplyr and tidyr cheatsheets (available on
Brightspace) for the functions you need to accomplish what you want with
your data.