Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.
Using the amazing package rayshader I wanted to render a video of my tour to Alpe d’Huez. Now I created an R package that can use any GPX file and return a 3D video animation from it.
< !-- /wp:heading --> < !-- wp:paragraph -->In July 2019 my friend Tjark and I went to France to cycle the 21 hairpin bends to Alpe d’Huez. The climb has a distance to the summit (at 1,860 m (6,102 ft)) of 13.8 km (8.6 mi), with an average gradient of 8.1% and a maximum gradient of 13%. Two years before we climbed up the amazing Mont Ventoux in Provence, and now we wanted to do Alpe d’Huez. Due to a lack of Hotels, we stayed up at the village itself. We started our tour facing down the Col de Sarenne, via Mizoën and through the valley up the 21 hairpins. It was hot, it was steep, it was exhausting.
< !-- /wp:paragraph --> < !-- wp:paragraph -->I was not at my best fitness. But I am a data scientist and I wanted to know how “slow” was I? There are several ways to find out. I could look at my average speed, a line chart or do a video. Even Strava, the app I used for tracking, has a built-in app to make a video called FlyBy. This tool is just two- dimensional. But on twitter and github I found the amazing package rayshader. It allows creating a 3D landscape out of any elevation data. Moreover, you can overlay your landscape with different maps or light conditions. So I thought, why don’t I put my GPS data on top of it? Said and done:
< !-- /wp:paragraph --> < !-- wp:html -->
In the next chapters, I will explain how you can create your own video from any .gpx file with my package rayshaderanimate.
< !-- /wp:paragraph --> < !-- wp:heading {"level":4} -->Downloading Elevation data
< !-- /wp:heading --> < !-- wp:image {"id":4449,"align":"center","width":350,"height":288} -->
My first problem was getting the elevation data around Alpe d’Huez. Thus I found the great package raster. You can download elevation data for a boundary box all over the world by calling:
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r"} -->raw_data <- raster::getData("SRTM", lon = bbox[1, 1], lat = bbox[2, 2]))
data_cropped <- raster::crop(raw_data, raster::extent(bbox))
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:paragraph -->
I wrapped this function inside my package rayshaderanimate. It would allow you to download the data. It then filters the data for the boundary box (not done by raster). Afterward, you can transform it into a rayshader readable format:
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r"} -->devtools::install_github("zappingseb/rayshaderanimation")
library(rayshader)
library(rayshaderanimation)
bbox <- data.frame(min = c(6.022108, 45.012030),
max = c(6.179801, 45.11066))
el_mat <- get_elevdata_from_bbox()
elmat_rayshade <- el_mat %>% unlabel_elevdata()
elmat_rayshade %>%
sphere_shade(texture = "desert") %>%
plot_3d(elmat_rayshade, zscale = 22,
fov = 0, theta = 135, zoom = 0.75,
phi = 45, windowsize = c(1000, 800))
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:paragraph -->
Please note that the SRTM data has a resolution of about 250m. If you would like a higher resolution you would need to register at the EU-DEM portal at: https://land.copernicus.eu/imagery-in-situ/eu-dem/eu-dem-v1.1?tab=downloada .
< !-- /wp:paragraph --> < !-- wp:paragraph -->There you can download large GEOTiff data. I also wrapped loading this data inside my package:
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r","lineNumbers":false} -->el_mat_eudem <- get_elevdata_from_bbox(bbox = bbox, type ="EUDEM", file = "eu_dem_v11_E40N20/eu_dem_v11_E40N20.TIF")< !-- /wp:syntaxhighlighter/code --> < !-- wp:paragraph -->
The difference between EU-DEM and SRTM data can be visualized using this code:
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r"} -->plot_2d_elevdata(el_mat %>% unlabel_elevdata) plot_2d_elevdata(el_mat_eudem %>% unlabel_elevdata)< !-- /wp:syntaxhighlighter/code --> < !-- wp:html -->
Reading in GPX files
< !-- /wp:heading --> < !-- wp:html -->The next task for me was to read in my gps data. The plotKML package has a function for that. I wrapped it inside my package. It outputs my GPX file as a table with longitudinal, latitudinal coordinates and a time vector. The table gets stored in the gpx_table variable and the boundary box gets stored inside the bbox variable.
gpx_file_loc <- system.file("Alpe_d_Huez.gpx", package="rayshaderanimate")
gpx_table <- get_table_from_gpx(gpx_file_loc) %>%
get_enriched_gpx_table()
bbox <- get_bbox_from_gpx_table(gpx_table)
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:heading {"level":4} -->
Making a ggplot video from elevation data and GPS data
< !-- /wp:heading --> < !-- wp:paragraph -->Animating the line of the GPS data means painting it on top of the landscape. I came to the conclusion that I need to paint every video scene image by image. Meaning if the line should move for two seconds, I would need 48 images to get a frame-rate of 24 images per second.
< !-- /wp:paragraph --> < !-- wp:paragraph -->I did not find any better way than creating a 2D graphic of the elevation data and rendering it as a 3D ggplot. Meaning each step of the video has to be rendered as a ggplot. Afterward, using rayshader I make a 3D image out of this. I take a snapshot and continue the process with a longer line of my GPS data.
< !-- /wp:paragraph --> < !-- wp:paragraph -->The trouble with GPS data is that it does not get captured in equally distributed time frames. Sometimes my phone would capture my position every second, sometimes every 30 seconds. So first I needed to create a function that equally distributes the time from my GPX table. The function is inside my package:
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r","lineNumbers":false} -->video_indeces <- get_video_indeces(time_data = gpx_table$time_right, number_of_screens = number_of_screens)< !-- /wp:syntaxhighlighter/code --> < !-- wp:paragraph -->
where number_of_screens is the number of frames going into the video. In my case, I wanted to capture ~300 screens to make it a ten second video.
For each screen, I needed to paint a ggplot. Ggplot needs the elevation data in a long format. This call will transform the elevation data to a ggplot format:
elmat_long <- get_elevdata_long(el_mat)< !-- /wp:syntaxhighlighter/code --> < !-- wp:paragraph -->
From the elevation data, the gpx table and the video indeces I can create every snapshot by rendering a ggplot:
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r"} -->my_plot <- ggplot() +
geom_tile(
data = elevdata_long,
aes_string(
"as.numeric(as.character(variable))",
"deg_elmat_lat",
fill = "value"),
alpha = 0.75) +
scale_x_continuous(
paste0("Longitude | ",
gpx_table$time[video_indx]),
expand = c(0,0)) +
scale_y_continuous("Latitude", expand = c(0,0)) +
scale_fill_gradientn("Elevation",
colours = terrain.colors(10)) +
coord_fixed() +
geom_path(
data = gpx_table[1:video_indx, ],
aes_string(x = "lon", y = "lat",
color = "-rel_speed"),
shape = 15, size = 1, stroke = 0) +
scale_color_viridis_c(option = "A") +
guides(colour=FALSE)
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:paragraph -->
As you can see I inserted a column rel_speed inside the gpx table to make faster pieces of the track darker. The x-axis label will show the real time of each image being captured.
To render this plot as a 3D graphic rayshader provides the function plot_gg. The image changes by tweeking angles and zooms. To take a picture from the 3D graphic I used the render_snapshot function.
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r"} -->plot_gg(my_plot, shadow_intensity = 0.7, width = 5, height = 5,
multicore = TRUE, scale = 350, raytrace = TRUE)
render_snapshot(filename = file.path(tempdir(),
paste0("video", video_indx, ".png")),
clear = TRUE)
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:image {"id":4464} -->
The difficult part is rendering all 300 images into a video. ffmpeg provides a simple API under Windows for this task. The links to all images get stored inside a txt file. From this text file ffmpeg can render the video as an mp4.
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"bash"} -->ffmpeg -y -f concat -r 24 -safe 0 -i "video_path.txt" -vf "fps=24,format=yuv420p" output.mp4< !-- /wp:syntaxhighlighter/code --> < !-- wp:paragraph -->
I also added functionality to render videos as gifs inside my package. Although I do not recommend rendering them as a gif. The gif files can become rather large. For more details on creating the video, please read the package vignette of rayshaderanimate package.
< !-- /wp:paragraph --> < !-- wp:html -->
How about a storytelling video?
< !-- /wp:heading --> < !-- wp:paragraph -->The video rendered up-to-now does not look like the video I showed at the top. I wanted to use the rayshader sphere shade with a map overlay for the video, too. Therefore I read the article at https://wcmbishop.github.io/rayshader-demo/ . While trying an image overlay with my data from Alpe d’Huez I noticed, that just the EUDEM data has a resolution that is high enough to render a sphere shade.
< !-- /wp:paragraph --> < !-- wp:paragraph -->But there were certain tweeks needed. I’ll not describe them in detail, but the major problem was rayshader beeing programmed for having data from the US, meaning west of Greenich Meridian. My data points are located east of Greenich Meridian. I created the function get_elevdata_list to overcome this problem.
< !-- /wp:paragraph --> < !-- wp:paragraph -->My function get_image_overlay can be used to derive an overlay image for a certain area. Adding the overlay image can simply be done by using the functionalities of rayshader, meaning add_overlay and plot_3d.
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r"} --># Format elevation data for west of Greenich
elevation_data_list <- get_elevdata_list(el_mat_eudem)
elevation_matrix <- elevation_data_list$elevation_matrix
# Calculate shadow and water
elevation_matrix %>%
sphere_shade(texture = "desert") %>%
add_water(detect_water(elevation_matrix), color = "desert") %>%
add_shadow(ray_shade(elevation_matrix,
zscale = 3, maxsearch = 300), 0.5)
# Receive Overlay Image from arcgis with a specific boundary box
bbox <- get_bbox_from_gpx_table(gpx_table, arcgis = TRUE)
overlay_img <- get_image_overlay(bbox_arcgis)
# Plot 3D with overlay image
elev_elem <- elev_elem %>% add_overlay(overlay_img, alphalayer = 0.5)
elev_elem %>%
plot_3d(elevation_matrix, zscale = 15, fov = 1, theta = 280,
zoom = 1.5, phi = 60, windowsize = c(1200, 800))
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:image {"id":4493} -->
Now the only things missing are the place markers and the route. Both can be added from the gpx_table. To do this I needed to map the latitude and longitude of the gpx_table to my elevation matrix resulting in lat_idx and lon_idx. Additionally, I added a label to some places, as you can see in this case it is place number 100.
< !-- /wp:paragraph --> < !-- wp:syntaxhighlighter/code {"language":"r","makeURLsClickable":false} -->for (i in 1:100) {
render_label(elevation_matrix,
x = gpx_table[1, "lon_idx"],
y = gpx_table[1, "lat_idx"],
z = 100, zscale = 15,
text = NULL, textsize = 15,
linewidth = 6, freetype = FALSE,
color = "#0f9ad1")
}
render_label(elevation_matrix,
x = gpx_table[100, "lon_idx"],
y = gpx_table[i, "lat_idx"],
z = 2200, zscale = 15,
text = gpx_table[100, "label"],
textsize = 1, linewidth = 7, freetype = FALSE,
color = "#0f9ad1", family = "mono", antialias = TRUE)
< !-- /wp:syntaxhighlighter/code -->
< !-- wp:image {"id":4499} -->
I perform this process for each single point of the gpx_table. At each point I take a snapshot by rayshader::render_snapshot. All snapshots will be stored and converted to a video by ffmpeg. I added some additional features as an elevation profile or a title image. Those were added to the snapshots using magick::image_append. All these features went into my function video_animation_rayshade. This function will create a whole video with a flyover over the map, adding the points and the elevation profile.
< !-- /wp:paragraph --> < !-- wp:heading {"level":4} -->Why the video?
< !-- /wp:heading --> < !-- wp:paragraph -->Two-dimensional animations cannot really describe the loss of speed uphill. The human perception of mountains is not represented by elevation lines. But elevation lines are the only way to visualize them in two-dimensional plots. The rayshader package allows a way better impression height and steepness. This is why I wanted to use it to visualize my climb to Alpe d’Huez.
< !-- /wp:paragraph --> < !-- wp:image {"id":4440,"align":"center","width":768,"height":576} -->
Now please enjoy watching the video of my cycling climb. You can truly see at the end of the video how I was suffering from the heat at the 21 hairpins. The last passage of the video describes me being slow. The color of the GPS line is bright and it takes long until it reaches the mountain top. Just to give you an impression I added a photo of the lowest 8 hairpins.
< !-- /wp:paragraph --> < !-- wp:html -->Final words
< !-- /wp:heading --> < !-- wp:image {"id":4470} -->
The package to create such videos is open-source and available on:
< !-- /wp:paragraph --> < !-- wp:list --> < !-- /wp:list --> < !-- wp:paragraph -->I track my cycling trips on STRAVA
< !-- /wp:paragraph --> < !-- wp:list --> < !-- /wp:list --> < !-- wp:paragraph -->More videos are available at my YouTube channel:
< !-- /wp:paragraph --> < !-- wp:list --> < !-- /wp:list -->R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.