Fix plotRGB errors in Ep. 5

[mneilson-usgs]

Remove scale argument from plotRGB() calls, as this argument currently is misleading (should not be larger than max value of bands within the raster).

Closes #476

[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-490

The following changes were observed in the rendered markdown documents:

 05-raster-multi-band-in-r.md                           |  10 ++--------
 ...and-in-r-rendered-plot-rbg-image-linear-1.png (new) | Bin 0 -> 466193 bytes
 ...-band-in-r-rendered-plot-rgb-image-hist-1.png (new) | Bin 0 -> 519899 bytes
 md5sum.txt                                             |   2 +-
 4 files changed, 3 insertions(+), 9 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 2025-08-08 21:08:22 +0000

[jonjab]

Thanks for the explanation. We knew it didn't do anything, and weren't even sure why one would want to do this.