Lesson 1 updated by replacing calls to raster and rgdal packages

[albhasan]

Lesson 1 updated by replacing calls to raster and rgdal packages with calls to terra package.

#368 #363

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 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:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

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

The following changes were observed in the rendered markdown documents:

 01-raster-structure.md                             | 387 +++++-----
 config.yaml (gone)                                 |  95 ---
 ...rendered-demonstrate-no-data-black-ggplot-1.png | Bin 119921 -> 122868 bytes
 ...cture-rendered-demonstrate-no-data-ggplot-1.png | Bin 166788 -> 171149 bytes
 ...raster-structure-rendered-unnamed-chunk-7-1.png | Bin 221085 -> 214918 bytes
 ...raster-structure-rendered-unnamed-chunk-9-1.png | Bin 109504 -> 109498 bytes
 ...integration-rendered-compare-data-extents-1.png | Bin 33244 -> 33202 bytes
 ...tion-rendered-repeat-compare-data-extents-1.png | Bin 33244 -> 33202 bytes
 md5sum.txt                                         |  50 +-
 renv.lock (gone)                                   | 810 ---------------------
 10 files changed, 235 insertions(+), 1107 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.

⏱️ Updated at 2023-03-06 15:11:37 +0000

[jsta]

should this text specifying the raster package be replaced with terra?

[albhasan]

You're right. I changed the text from raster to terra. Thanks!

[drakeasberry]

Thank you for your contribution on transitioning to terra. A few notes below on updating text content for learners to follow along with updated code will be very helpful:

Line 84 references GDAL() function that has now been removed and should be updated to reflect describe()
Line 151 references raster() and should be updated to reflect the forcing of dataframe creation
Lines 319-332 references raster() and nlayers()

[albhasan]

Thank you for reporting the typos. I fixed them.

[jsta]

Looks good to me. I say we go ahead and merge given that the lesson url is pinned to the 2023/2/6 snapshot. Anyone else have thoughts?

Only thing I'm on the fence about is the very long output of describe. Is there an easy way to shorten?

[albhasan]

@jsta I agree with you regarding describe. We could try the meta argument to get the file metadata instead, but I guess we get the opposite problem instead; I mean, barely a line of metadata:

describe("data/NEON-DS-Airborne-Remote-Sensing/HARV/DSM/HARV_dsmCrop.tif", meta = TRUE)
> [1] "AREA_OR_POINT=Area"

[jsta]

Thanks for taking this on @albhasan!