: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:
The following changes were observed in the rendered markdown documents:
01-intro-raster-data.md | 63 +--
02-intro-vector-data.md | 30 +-
03-crs.md | 20 +-
04-geo-landscape.md | 24 +-
05-access-data.md | 310 +++++++++----
06-raster-intro.md | 418 +++++++++++-------
07-vector-data-in-python.md | 482 ++++++++++-----------
08-crop-raster-data.md | 289 +++++-------
09-raster-calculations.md | 352 +++++++--------
10-zonal-statistics.md | 166 +++----
11-parallel-raster-computations.md | 212 +++------
12-data-cube.md (new) | 195 +++++++++
fig/E05/STAC-s2-preview-after.jpg (new) | Bin 0 -> 70832 bytes
fig/E05/STAC-s2-preview-before.jpg (new) | Bin 0 -> 75077 bytes
fig/E06/rhodes_multiband_80.png (new) | Bin 0 -> 1033117 bytes
fig/E06/rhodes_multiband_80_equal_aspect.png (new) | Bin 0 -> 861267 bytes
fig/E06/rhodes_red_80_B04.png (new) | Bin 0 -> 590536 bytes
fig/E06/rhodes_red_80_B04_robust.png (new) | Bin 0 -> 946323 bytes
fig/E06/rhodes_red_80_B04_robust_nan.png (new) | Bin 0 -> 865948 bytes
.../rhodes_red_80_B04_vmin100_vmax2000.png (new) | Bin 0 -> 880764 bytes
fig/E06/rhodes_red_B04.png (new) | Bin 0 -> 801039 bytes
fig/E07/greece_administration_areas.png (new) | Bin 0 -> 64055 bytes
fig/E07/greece_highways.png (new) | Bin 0 -> 26479 bytes
fig/E07/rhodes_administration_areas.png (new) | Bin 0 -> 17351 bytes
fig/E07/rhodes_assets.png (new) | Bin 0 -> 45400 bytes
fig/E07/rhodes_builtup_buffer.png (new) | Bin 0 -> 18396 bytes
fig/E07/rhodes_highways.png (new) | Bin 0 -> 80495 bytes
fig/E07/rhodes_infra_highways.png (new) | Bin 0 -> 46913 bytes
fig/E08/dem.png (new) | Bin 0 -> 98203 bytes
fig/E08/dem_matched.png (new) | Bin 0 -> 122237 bytes
fig/E08/visual_clip.png (new) | Bin 0 -> 77146 bytes
fig/E08/visual_clip_box.png (new) | Bin 0 -> 374262 bytes
fig/E08/visual_large.png (new) | Bin 0 -> 197716 bytes
fig/E09/NDVI-hist.png | Bin 7916 -> 14496 bytes
fig/E09/NDVI-map.png | Bin 163222 -> 332276 bytes
fig/E09/NDWI.png (new) | Bin 0 -> 314396 bytes
fig/E09/NIR-band.png | Bin 167850 -> 276002 bytes
fig/E09/custom-index.png (new) | Bin 0 -> 429445 bytes
fig/E09/red-band.png | Bin 162461 -> 265509 bytes
fig/E09/visual-burned-index.png (new) | Bin 0 -> 357171 bytes
fig/E10/zones_rasterized_xarray.png (new) | Bin 0 -> 31334 bytes
fig/E11/dask-graph.png | Bin 2311171 -> 94585 bytes
fig/E12/NDVI-after.png (new) | Bin 0 -> 201397 bytes
fig/E12/NDVI-after_point.png (new) | Bin 0 -> 201432 bytes
fig/E12/NDVI-before.png (new) | Bin 0 -> 206500 bytes
fig/E12/NDVI-time-series.png (new) | Bin 0 -> 25906 bytes
index.md | 44 +-
md5sum.txt | 27 +-
setup.md | 27 +-
49 files changed, 1423 insertions(+), 1236 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.
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/esciencecenter-digital-skills/geospatial-python/compare/md-outputs..md-outputs-PR-121
The following changes were observed in the rendered markdown documents:
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 2024-06-25 11:19:24 +0000