[sverbesselt01]

add my markdown file, html files and data

Description

Related Issue

Task list

• My tutorial or article is placed in a subfolder of tutorials/content/
• The novel tutorial has a meaningful name, in relation to the content of the tutorial.
• The filename of my tutorial or article is index.md. In case of an Rmarkdown tutorial I have knitted my index.Rmd to index.md (both files are pushed to the repo).
• yaml header:
  • (recommended) I am included as author in the authors yaml tag, using [MY_AUTHOR_ID]. An author information file exists in <tutorials>/data/authors/<author>.toml.
  • I have added categories to the YAML header and my category tags are from the list of categories.
  • I have included meaningful and applicable tags (i.e. keywords) in the YAML header to improve the visibility of the new tutorial (see the tags listed in the tutorials website side bar).
  • The date is in format YYYY-MM-DD and adjusted.
• (recommended) I have previewed this PR locally (see steps below; ask previous contributors for help) and confirmed that the new content renders as expected.

Previewing the pull request

Thanks to GitHub Actions, an artifact (=zip file) of the rendered website is automatically created for each pull request.
This provides a way to preview how these updates will look on the website, useful to contributors and reviewers.

Instructions to preview the updated website

1. On the PR page, you can find a "details" link under "checks - On PR, build the site and ...". Go there, click on the top link in the left sidebar ("Summary"), and download the generated artifact at the bottom of the page.
2. Decompress it into a target directory, e.g. Downloads/tutorials_preview.
3. To preview the website, use a program which can serve http sites on your local machine. One such option is the servr package in R: & '\C:\Program Files\R\R-4.4.2\bin\Rscript.exe' -e "servr::httd('./tutorials_preview')" -p8887 (make sure to adjust the path to your Rscript.exe; on Linux, simply use Rscript -e [...]).
4. Point your browser to http://localhost:8887.
5. Review the updated website. As a contributor, you can push extra commits to update the PR. As a reviewer, you can accept/refuse/comment the PR.

Note: for step 3, you can use any other simple HTTP server to serve the current directory, e.g. Python http.server: python -m http.server 8887 --bind localhost --directory path/to/tutorials_preview

Alternative: Locally Building the Site

Alternatively, you can build the entire site locally (see the README for instructions); the Hugo preview server will update changes on the fly.
This requires Hugo to be installed on your computer.

[bserrien]

Is it worth printing the result of this command in the tutorial and explaining why you ignore certain warnings? When I apply it, I get warnings on duplicate and degenerate points. Later on in the tutorial, the function get_crown_attributes() also issues a warning that duplicate points have been removed.

  - Checking absence of NAs... ✓
  - Checking duplicated points...
    ⚠ 5829552 points are duplicated and share XYZ coordinates with other points
  - Checking degenerated ground points...
    ⚠ There were 3503496 degenerated ground points. Some X Y Z coordinates were repeated
    ⚠ There were 2273 degenerated ground points. Some X Y coordinates were repeated but with different Z coordinates

[sverbesselt01]

It is okay for me to print out the get_crown_attributes(). We have duplicates since the tiles of laz files overlap to a certain degree (flight paths of the plane with the lidar sensor onboard overlap). In these overlapping zones, you can have dubble the amount of points. You can remove them before analysis (for example, remove the overlapping zones), but most functions inside the package will detect them automatically and remove them (but for for statistical analysis/metrics, it is indeed better to remove duplicates). The degenerated ground points can be caused by small errors in the sensor, or by "moving" objects on the ground during lidar scanning (For example, if there is wind, tree crowns move slightly, causing different z-values for the same locations).

[sverbesselt01]

I agree to your changes and provided an answer to your question :)

[bserrien]

Thanks for your contribution to the INBO tutorials website!