datacarpentry / r-raster-vector-geospatial

Introduction to Geospatial Raster and Vector Data with R
https://datacarpentry.org/r-raster-vector-geospatial
Other
113 stars 110 forks source link

Typo in episode 3 Reproject and Plot Digital Terrain challenge #419

Closed kristi-sara closed 1 year ago

kristi-sara commented 1 year ago

on lines 321 and 328, original challenge says DTM_hill_SJER,

but it should be DSM_hill_UTMZ18N_SJER (321) and DSM_hill_SJER_df(328)

https://datacarpentry.org/r-raster-vector-geospatial/03-raster-reproject-in-r.html#challenge-reproject-then-plot-a-digital-terrain-model

github-actions[bot] commented 1 year ago

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:

Rendered Changes

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

The following changes were observed in the rendered markdown documents:

 03-raster-reproject-in-r.md | 4 ++--
 md5sum.txt                  | 2 +-
 2 files changed, 3 insertions(+), 3 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-07-18 18:17:56 +0000

drakeasberry commented 1 year ago

Thank you for contributing.