This introductory practical vignette has largely been replaced by the workbook “Reproducible Road Safety Research with R”, which can be found at https://itsleeds.github.io/rrsrr/ and as a PDF at racfoundation.org (Lovelace 2020). That workbook is more comprehensive than the content in this tutorial and is the recommended place to learn about using R for reproducible road safety research.
This document provides information, code and exercises to test and improve your R skills with an emphasis on road safety research. It was initially developed to support a 2 day course. The course is based on open road crash records from the stats19 package (Lovelace et al. 2019). However, the content should be of use for anyone working with road crash data that has (at a minimum):
You should type, run and ensure you understand each line of code in this document.
Code and data supporting the content can be found in the package’s GitHub repo at github.com/ropensci/stats19. The ‘issue tracker’ associated with that repo is a good place to ask questions about the course.
If you are not experienced with R, it is strongly advised that you read-up on and more importantly test out R and RStudio before attempting analyse road crash data with R. See the stats19-training-setup
vignette at https://docs.ropensci.org/stats19/articles/stats19-training-setup.html for guidance on getting started with R, RStudio and installing R packages.
The completing the course requires that the following packages, which can be installed with install.packages()
, can be loaded as follows:
library(pct) # access travel data from DfT-funded PCT project
library(sf) # spatial vector data classes
library(stats19) # get stats19 data
library(stplanr) # transport planning tools
library(tidyverse)# packages for 'data science'
library(tmap) # interactive maps
You should type, run and ensure you understand each line of code in this document.
#> Warning in utils::citation(..., lib.loc = lib.loc): could not determine year
#> for 'stats19' from package DESCRIPTION file
The learning outcomes of this first session are to learn: RStudio main features and scripts, R objects and functions, subsetting, basic plotting, and getting help.
The first exercise is to open up RStudio and take a look around and identify the main components, shown in the figure below. Explore each of the main components of RStudio. Try changing the Global Settings (in the Tools menu) and see RStudio’s short cuts by pressing Alt-Shift-K
(or Option+Shift+K
on Mac).
Projects are a way to organise related work together. Each project has its own folder and Rproj file. Advice: always working from projects will make your life easier! Start a new project with:
File > New Project You can choose to create a new directory (folder) or associate a project with an existing directory. Make a new project called stats1-course and save it in a sensible place on your computer. Notice that stats1-course now appears in the top right of RStudio.
Scripts are the files where R code is stored. Keeping your code in sensibly named, well organised and reproducible scripts will make your life easier: you could simply type all our code into the console, but that require retyping commands each time you run it. Instead, code that you want to keep and share should be saved script files, plain text files that have the .R
extension.
Make a new script with Flie > New File > Rscript or Ctrl+Shift+N
Save the script and give it a sensible name like stats19-lesson-1.R
with File > Save, the save button on the toolbar, or Ctrl+S.
Pro tip: You can also create new R scripts by typing and running this command in the R console:
file.edit("stats19-lesson-1.R")
Keeping scripts and other files associated with a project in a single folder per project (in an RStudio project) will help you find things you need and develop an efficient workflow.
Let’s start with some basic R operations. Write this code into your new stats19-lesson-1.R
R script and execute the result line-by-line by pressing Ctrl+Enter
1:5
x = c(0, 1, 3, 9, 18)
y =plot(x, y)
This code creates two objects, both are vectors of 5 elements, and then plots them (bonus: check their length using the length()
function). Save the script by pressing Ctrl+S.
There are several ways to run code within a script and it is worth becoming familiar with each. Try running the code you saved in the previous section using each of these methods:
Ctrl+Enter
to run that line of code.Ctrl+Enter
to run the highlighted code.Ctrl+Shift+Enter
to run all the code in a script.source()
to run all the code in a script e.g. source("stats19-lesson-1.R")
Pro tip: Try jumping between the console and the source editor by pressing Ctl+1 and Ctl+2.
Create new objects by typing and running the following code chunk in a new script, e.g. called objects.R
.
c("car", "bus", "tank")
vehicle_type = c("pedestrian", "cyclist", "cat")
casualty_type = seq(from = 20, to = 60, by = 20)
casualty_age =set.seed(1)
sample(x = c(TRUE, FALSE), size = 3, replace = TRUE)
dark = matrix(1:24, nrow = 12)
small_matrix = data.frame(vehicle_type, casualty_type, casualty_age, dark) crashes =
We can view the objects in a range of ways:
crashes
and small_matrix
, and run that code. Scroll up to see the numbers that didn’t fit on the screen.head()
function to view just the first 6 rows e.g. head(small_matrix)
n
argument in the previous function call to show only the first 2 rows of small_matrix
crashes
object in the environment tab to View it in a spreadsheet.View(vehicle_type)
. What just happened?We can also get an overview of an object using a range of functions, including summary()
, class()
, typeof()
, dim()
, and length()
.
You can, for example, view a summary of the casualty_age
variable by running the following line of code:
summary(casualty_age)
#> Min. 1st Qu. Median Mean 3rd Qu. Max.
#> 20 30 40 40 50 60
Exercise try these functions on each of the objects, what results do they give?
Bonus: Find out the class of the column vehicle_type
in the data frame crashes
with the command class(crashes$vehicle_type)
. Why has it changed? Create a new object called crashes_char
that keeps the class of the character vectors intact by using the function tibble::tibble()
(see tibble.tidyverse.org and Section 4 for details).
RStudio can help you write code by autocompleting it. RStudio will look for similar objects and functions after typing the first three letters of a name.
When there is more than one option you can select from the list using the mouse or arrow keys. Within a function, you can get a list of arguments by pressing Tab.
Every function in R has a help page. You can view the help using ?
for example ?sum
. Many packages also contain vignettes, these are long form help documents containing examples and guides. vignette()
will show a list of all the vignettes available, or you can show a specific vignette for example vignette(topic = "sf1", package = "sf")
.
It is good practice to use comments in your code to explain what it does. You can comment code using #
For example:
# Create vector objects (a whole line comment)
1:5 # a seqence of consecutive integers (inline comment)
x = c(0, 1, 3, 9, 18.1) y =
You can comment/uncomment a whole block of text by selecting it and using Ctrl+Shift+C
.
Pro tip: You can add a comment section using Ctrl + Shift + R
The Environment tab shows all the objects in your environment, this includes datasets, parameters, and any functions you have created. By default, new objects appear in the Global Environment but you can see other environments with the drop-down menu. For example, each package has its own environment.
Sometimes you wish to remove things from your environment, perhaps because you no longer need them or things are getting cluttered.
You can remove an object with the rm()
function e.g. rm(x)
or rm(x, y)
or you can clear your whole environment with the broom button on the Environment Tab.
x
that was created in a previous section.x
by entering it into the console?save.image(); rm(list = ls()); load(".RData")
. What happened?.RData
file in your project’s folder?.Rdata
file with file.remove(".Rdata")
.All the code shown so far is reproducible. To test RStudio’s debugging features, let’s write some code that fails, as illustrated in the figure below.
Always address debugging prompts to ensure your code is reproducible
We have already seen that you can save R scripts. You can also save individual R objects in the RDS format.
saveRDS(crashes, "crashes.Rds")
We can also read back in our data.
readRDS("crashes.Rds")
crashes2 =identical(crashes, crashes2)
#> [1] TRUE
R also supports many other formats, including CSV files, which can be created and imported with the functions readr::read_csv()
and readr::write_csv()
(see also the readr package).
::write_csv(crashes, "crashes.csv")
readr readr::read_csv("crashes.csv")
crashes3 =identical(crashes3, crashes)
Notice that crashes3
and crashes
are not identical, what has changed? Hint: read the help page associated with ?readr::write_csv
.
Subsetting returns part of an R object. It can be done by providing numbers representing the positions of the elements we want (e.g. the 2nd element) or with a logical vector, with values associated with TRUE
returned. Two dimension object such as matrices and data frames can be subset by rows and columns. Subsetting in base R is done with square brackets []
after the name of an object. Run the following commands to practice subsetting.
2:3] # second and third casualty_age
casualty_age[c(1, 2), ] # first and second row of crashes
crashes[$vehicle_type # returns just one column
crashesc("casualty_type", "casualty_age")] # first and third columns crashes[,
$
operator to print the dark
column of crashes
.[,]
syntax so that only the first and third columns of crashes
are returned.crashes
dataset.crashes
dataset.class()
of the objects created by each of the previous exercises?It is also possible to subset objects by the values of their elements. This works because the [
operator accepts logical vectors returned by queries such as ‘is it less than 3?’ (x < 3
in R) and ‘was it light?’ (crashes$dark == FALSE
), as demonstrated below:
c(TRUE, FALSE, TRUE, FALSE, TRUE)] # 1st, 3rd, and 5th element in x
x[== 5] # only when x == 5 (notice the use of double equals)
x[x < 3] # less than 3
x[x < 3] = 0 # assign specific elements
x[x %% 6 == 0] # just the ages that are a multiple of 6
casualty_age[casualty_age $dark == FALSE, ] crashes[crashes
casualty_age
object using the inequality (<
) so that only elements less than 50 are returned.crashes
data frame so that only tanks are returned using the ==
operator.R objects can have a value of NA. This is how R represents missing data.
c(4, 5, NA, 7) z =
NA values are common in real-world data but can cause trouble, for example
sum(z) # result is NA
Some functions can be told to ignore NA values.
sum(z, na.rm = TRUE) # result is equal to 4 + 5 + 7
You can find NAs using the is.na()
function, and then remove them
is.na(z)
z[!is.na(z)] # note the use of the not operator !
z_nona =sum(z)
If you remove records with NAs be warned: the average of a value excluding NAs may not be representative.
Sometimes you may want to change the class of an object. This is called class coercion, and can be done with functions such as as.logical()
, as.numeric()
and as.matrix()
.
vehicle_type
column of crashes
to the class character
.crashes
object into a matrix. What happened to the values?summary()
on character
and factor
variables?Often it is useful to ‘recode’ values. In the raw STATS19 files, for example, -1 means NA. There are many ways to recode values in R, the simplest and most mature of which is the use of factors, as shown below:
c(1, 2, -1, 1, 3)
z = c(NA, "a", "b", "c") # labels in ascending order
l = factor(z, labels = l)
z_factor = as.character(z_factor)
z_charcter =
z_charcter#> [1] "a" "b" NA "a" "c"
z
to Slight, Serious and Fatal for 1:3 respectively.?dplyr::case_when
and try to recode the values using this function.Bonus: reproduce the following plot
c(2.3, 4, 3.7, 4)
eyes = matrix(eyes, ncol = 2, byrow = T)
eyes = c(2, 2, 2.5, 1.3, 3, 1, 3.5, 1.3, 4, 2)
mouth = matrix(mouth, ncol = 2, byrow = T)
mouth =plot(eyes, type = "p", main = "RRR!", cex = 2, xlim = c(1, 5), ylim = c(0, 5))
lines(mouth, type = "l", col = "red")
R has over 15,000 packages (effectively plugins for base R), extending it in almost every direction of statistics and computing. Packages provide additional functions, data and documentation. They are very often written by subject-matter experts and therefore tend to fit well with the workflow of the analyst in that particular specialism. There are two main stages to using a package: installing it and loading it. A third stage is updating it, this is also important.
Install new packages from The Comprehensive R Archive Network with the command install.packages()
(or remotes::install_github()
to install from GitHub). Update packages with the command update.package()
or in Tools > Check for Package Updates in RStudio. You only need to install a package once.
install.packages("sf")
# remotes::install_github("r-spatial/sf")
Installed packages are loaded with the command library()
. Usually, the package will load silently. In some cases the package will provide a message, as illustrated below.
library(sf)
#> Linking to GEOS 3.12.1, GDAL 3.8.4, PROJ 9.3.1; sf_use_s2() is TRUE
To use a function in a package without first loading the package, use double colons, as shown below (this calls the tibble()
function from the tibble
package).
tibble::tibble(
crashes_tibble =
vehicle_type,
casualty_type,
casualty_age,
dark )
stats19
package is installed on your computer?update.packages()
. What happens? Why?Let’s take a look at a particular package. ggplot2
is a generic plotting package that is part of the ‘tidyverse’ meta-package, which is an “opinionated collection of R packages designed for data science”. All packages in the tidyverse “share an underlying design philosophy, grammar, and data structures”. ggplot2
is flexible, popular, and has dozens of add-on packages which build on it, such as gganimate
. To plot non-spatial data, it works as follows (see figure below, left for result):
library(ggplot2)
ggplot(crashes) + geom_point(aes(x = casualty_type, y = casualty_age))
Note that the +
operator adds layers onto one another.
ggplot2
that begins with with gg
. Hint: enter install.packages(gg)
and hit Tab when your cursor is between the g
and the )
.?package_name::function()
syntax.ggthemes
package, try other themes).Another useful package in the tidyverse is dplyr
. It provides functions for manipulating data frames and using the pipe operator %>%
. The pipe puts the output of one command into the first argument of the next, as shown below (note the results are the same):
library(dplyr)
#>
#> Attaching package: 'dplyr'
#> The following objects are masked from 'package:stats':
#>
#> filter, lag
#> The following objects are masked from 'package:base':
#>
#> intersect, setdiff, setequal, union
class(crashes)
#> [1] "data.frame"
%>% class()
crashes #> [1] "data.frame"
Useful dplyr
functions are demonstrated below.
%>%
crashes filter(casualty_age > 50) # filter rows
%>%
crashes select(casualty_type) # select just one column
%>%
crashes group_by(dark) %>%
summarise(mean_age = mean(casualty_age))
dplyr
to filter row in which casualty_age
is less than 18, and then 28.arrange
function to sort the crashes
object in descending order of age (hint: see the ?arrange
help page).dplyr::mutate()
. What does the function do?birth_year
, in the crashes
data.frame which is defined as the current year minus their age.%>%
operator to filter the output from the previous exercise so that only observations with birth_year
after 1969 are returned.For the analysis and manipulation of temporal data we will first load the R package lubridate
:
library(lubridate)
The simplest example of a Date object that we can analyze is just the current date, i.e.
today()
#> [1] "2024-07-31"
We can manipulate this object using several lubridate
functions to extract the current day, month, year, weekday and so on…
today()
x =day(x)
month(x)
year(x)
weekdays(x)
Exercises:
month
to see how it is possible to extract the current month as character vectorDate variables are often stored simply as a character vectors. This is a problem, since R is not always smart enough to distinguish between character vectors representing Dates. lubridate
provides functions that can translate a wide range of date encodings such as ymd()
, which extracts the Year Month and Day from a character string, as demonstrated below.
as.Date("2019-10-17") # works
as.Date("2019 10 17") # fails
ymd("2019 10 17") # works
dmy("17/10/2019") # works
Import function such as read_csv
try to recognize the Date variables. Sometimes this fails. You can manually create Date objects, as shown below.
c("2009-01-01", "2009-02-02", "2009-03-03")
x = ymd(x)
x_date =
x_date#> [1] "2009-01-01" "2009-02-02" "2009-03-03"
Exercises:
x_date
."09/09/93"
into a date object and extract its weekday.as.Date
and strptime
for further details on base R functions for dates.lubridate
package.We can use Dates also for subsetting events in a dataframe. For example, if we define x_date
as before and add it to the crash
dataset, i.e.
$casualty_day = x_date crashes
then we can subset events using Dates. For example
filter(crashes, day(casualty_day) < 7) # the events that ocurred in the first week of the month
#> vehicle_type casualty_type casualty_age dark casualty_day
#> 1 car pedestrian 20 TRUE 2009-01-01
#> 2 bus cyclist 40 FALSE 2009-02-02
#> 3 tank cat 60 TRUE 2009-03-03
filter(crashes, weekdays(casualty_day) == "Monday") # the events occurred on monday
#> vehicle_type casualty_type casualty_age dark casualty_day
#> 1 bus cyclist 40 FALSE 2009-02-02
Exercises:
crashes
) that occurred in Januaryleap_year
)Now we’ll take a look at the time components of a Date. Using the function hms
(acronym for Hour Minutes Seconds) and its subfunctions such as hm
or ms
, we can parse a character vector representing several times as an Hour object (which is tecnically called a Period object).
c("18:23:35", "00:00:01", "12:34:56")
x = hms(x)
x_hour =
x_hour#> [1] "18H 23M 35S" "1S" "12H 34M 56S"
We can manipulate these objects using several lubridate
functions to extract the hour component, the minutes and so on:
hour(x_hour)
#> [1] 18 0 12
minute(x_hour)
#> [1] 23 0 34
second(x_hour)
#> [1] 35 1 56
If the Hour data do not specify the seconds, then we just have to use a subfunction of hms
, namely hm
, and everything works as before.
c("18:23", "00:00", "12:34")
x =x_hour = hm(x))
(#> [1] "18H 23M 0S" "0S" "12H 34M 0S"
We can use Hour data also for subsetting events, like we did for Dates. Let’s add a new column to crashes data,
$casualty_hms = hms(c("18:23:35", "00:00:01", "12:34:56"))
crashes$casualty_hour = hour(crashes$casualty_hms) crashes
Exercises:
>= 12
.library(stats19)
2022 = stats19::get_stats19(year = 2022, type = "ac")
crashes_2022 crashes_
Extract the weekday from the variable called date
. How many crashes happened on Monday?
Advanced challenge: calculate how many crashes occurred for each day of the week. Then plot it with ggplot2. Repeat the same exercises extracting the hour of the car accident from the variable called time. How would you combine the two informations in a single plot?
All road crashes happen somewhere and, in the UK at least, all collisions recorded by the police are given geographic coordinates, something that can help prioritise interventions to save lives by intervening in and around ‘crash hotspots’. R has strong geographic data capabilities, with the sf
package provides a generic class for spatial vector data: points, lines and polygons, are represented in sf
objects as a special ‘geometry column’, typically called ‘geom’ or ‘geometry’, extending the data frame class we’ve already seen in crashes
.
Create an sf
data frame called crashes_sf
as follows:
library(sf) # load the sf package for working with spatial data
crashes # create copy of crashes dataset
crashes_sf =$longitude = c(-1.3, -1.2, -1.1)
crashes_sf$latitude = c(50.7, 50.7, 50.68)
crashes_sf st_as_sf(crashes_sf, coords = c("longitude", "latitude"), crs = 4326)
crashes_sf =# plot(crashes_sf[1:4]) # basic plot
# mapview::mapview(crashes_sf) # for interactive map
crashes_sf
(hint: the solution may contain $geometry
). If the result is like the figure below, congratulations, it worked!).crashes_sf
, only showing the age variable.sf
functions begin with st_
)?You can read and write spatial data with read_sf()
and write_sf()
, as shown below (see ?read_sf
).
write_sf(zones, "zones.geojson") # save geojson file
write_sf(zones, "zmapinfo", driver = "MapInfo file")
read_sf("zmapinfo") # read in mapinfo file
See Chapter 6 of Geocomputation with R for further information.
Note: the code beyond this point is not evaluated in the vignette:
::opts_chunk$set(eval = FALSE) knitr
sf
objects can also represent administrative zones. This is illustrated below with reference to zones
, a spatial object representing the Isle of Wight, that we will download using the pct
package (note: the [1:9]
appended to the function selects only the first 9 columns).
pct::get_pct_zones("isle-of-wight")[1:9] zones =
zones
object?Like index and value subsetting, spatial subsetting can be done with the [
notation. Subset the zones
that contain features in crashes_sf
as follows:
zones[crashes_sf, ] zones_containing_crashes =
To plot a new layer on top of an existing sf
plot, use the add = TRUE
argument. Remember to plot only the geometry
column of objects to avoid multiple maps. Colours can be set with the col
argument.
Geographic joins involve assigning values from one object to a new column in another, based on the geographic relationship between them. With sf
objects it works as follows:
st_join(zones[1], crashes_sf) zones_joined =
casualty_age
variable of the new zones_joined
object (see the figure below to verify the result).geo_code
column from the zones
and the dark
column from crashes_sf
and use the left = FALSE
argument to return only zones in which crashes occured. Plot the result.See Chapter 4 of Geocomputation with R (Lovelace, Nowosad, and Muenchow 2019) for further information on geographic joins.
Get and set Coordinate Reference Systems (CRSs) with the command st_crs()
. Transform CRSs with the command st_transform()
, as demonstrated in the code chunk below, which converts the ‘lon/lat’ geographic CRS of crashes_sf
into the projected CRS of the British National Grid:
st_transform(crashes_sf, 27700) crashes_osgb =
crashes_osgb
. What does the error message say?zones_osgb
by transforming the zones
object.st_crs()
to find out the units measurement of the British National Grid?For more information on CRSs see Chapter 6 of Geocompuation with R.
Buffers are polygons surrounding geometries of a (usually) fixed distance. Currently buffer operations in R only work on objects with projected CRSs.
sf
’s buffer function.crashes_1km_buffer
representing the area within 1 km of the crashes.crashes_sf
object. What happens?Because sf
objects are data.frame
s, we can do non-spatial operations on them. Try the following attribute operations on the zones
data.
# load example dataset if it doesn't already exist
pct::get_pct_zones("isle-of-wight")
zones = zones$all > 3000 # create a subsetting object
sel = zones[sel, ] # subset areas with a popualtion over 100,000
zones_large =2 = zones[zones$geo_name == "Isle of Wight 002",] # subset based on 'equality' query
zones_ zones[c(1, 3)]
zones_first_and_third_column = zones["all"] zones_just_all =
sf data.frame
object zones
:
zones_small
which contains only regions with less than 3000 people in the all
columnsel_high_car
which is TRUE
for regions with above median numbers of people who travel by car and FALSE
otherwisezones_foot
which contains only the foot attribute from zones
zones_foot
using the function plot
to show where walking is a popular mode of travel to workfilter()
from the dplyr
package to subset small regions where car use is high.st_area()
, as.numeric()
and use the ‘all’ column)?I think you forgot something here. For example we could introduce st_nearest_feature
? Or counting using st_within
and st_buffer
.
So far we have used the plot()
function to make maps. That’s fine for basic visualisation, but for publication-quality maps, we recommend using tmap
(see Chapter 8 of Geocomputation with R for reasons and alternatives). Load the package as follows:
library(tmap)
tmap_mode("plot")
plot()
and tm_shape() + tm_polygons()
functions (note: the third figure relies on setting tmap_mode("view")
.Based on the saying “don’t run before you can walk”, we’ve learned the vital foundations of R before tackling a real dataset. Temporal and spatial attributes are key to road crash data, hence the emphasis on lubridate
and sf
. Visualisation is key to understanding and policy influence, which is where tmap
comes in. With these solid foundations, plus knowledge of how to ask for help (read R’s internal help functions, ask colleagues, create new comments on online forums/GitHub, generally in that order of priority), you are ready to test the methods on some real data.
Before doing so, take a read of the stats19
vignette, which can be launched as follows:
vignette(package = "stats19") # view all vignettes available on stats19
vignette("stats19") # view the introductory vignette
This should now be sufficient to tackle the following exercises:
stats19
package that converts a data.frame
object into an sf
data frame. Use this function to convert the road crashes into an sf
object, called crashes_sf
, for example.local
)st_crs()
?)month
in the crash data using the function lubridate::month()
and the date
column.a_zones_may
representing all the crashes that happened in the Isle of Wight in the month of Maymean
) speed limit associated with each crash that happened in May across the zones of the Isle of Wight (the result is shown in the map)Road network data can be accessed from a range of sources, including OpenStreetMap (OSM) and Ordnance Survey. We will use some OSM data from the Ilse of Wight, which can be loaded as follows:
"https://github.com/ropensci/stats19/releases/download/1.1.0/roads_key.Rds"
u = readRDS(url(u))
roads_wgs = roads_wgs %>% st_transform(crs = 27700) roads =
You should already have road crashes for the Isle of Wight from the previous stage. If not, load crash data as follows:
"https://github.com/ropensci/stats19/releases/download/1.1.0/car_collisions_2022_iow.Rds"
u = readRDS(url(u)) crashes_iow =
aggregate()
function to identify how many crashes happened per segment and plot the result (hint: see ?aggregate.sf
and take a read of Section 4.2.5 of Geocomputation with R) with tmap
and plot the crashes that happened outside the road buffers on top.Identify a region and zonal units of interest from https://geoportal.statistics.gov.uk/ or from the object police_boundaries
in the stats19
package.
sf
objectLovelace, Robin. 2020. “Reproducible Road Safety Research with R.” Royal Automotive Club Foundation.
Lovelace, Robin, Malcolm Morgan, Layik Hama, Mark Padgham, and M Padgham. 2019. “Stats19 A Package for Working with Open Road Crash Data.” Journal of Open Source Software 4 (33): 1181. https://doi.org/10.21105/joss.01181.
Lovelace, Robin, Jakub Nowosad, and Jannes Muenchow. 2019. Geocomputation with R. CRC Press.