Episode 13 updated by replacing calls to raster and rgdal packages

Thank you!

Thank you for your pull request :smiley:

:robot: This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

:dart: correct output
:framed_picture: correct figures
:question: new warnings
:bangbang: new errors

Rendered Changes

:mag: Inspect the changes: https://github.com/datacarpentry/r-raster-vector-geospatial/compare/md-outputs..md-outputs-PR-398

The following changes were observed in the rendered markdown documents:

 13-plot-time-series-rasters-in-r.md                |  121 +--
 config.yaml (gone)                                 |   95 --
 ...ulti-band-in-r-rendered-plot-brick-1.png (gone) |  Bin 457926 -> 0 bytes
 ...integration-rendered-compare-data-extents-1.png |  Bin 33131 -> 33012 bytes
 ...tion-rendered-repeat-compare-data-extents-1.png |  Bin 33131 -> 33012 bytes
 md5sum.txt                                         |   50 +-
 renv.lock (gone)                                   | 1004 --------------------
 7 files changed, 91 insertions(+), 1179 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible. This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

:stopwatch: Updated at 2023-03-17 19:35:04 +0000

datacarpentry / r-raster-vector-geospatial

Episode 13 updated by replacing calls to raster and rgdal packages #398

Thank you!

Rendered Changes