yet another link

r-lidar · Oct 9, 2020 · a26353d · a26353d
1 parent 030d7c3
commit a26353d
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 5 deletions.
diff --git a/R/delineate_crowns.R b/R/delineate_crowns.R
@@ -32,8 +32,7 @@
 #' details and references).
 #'
 #' The concave hull method under the hood is described in Park & Oh (2012). The function relies on
-#' the \link[concaveman:concaveman]{concaveman} function which itself is a wrapper around
-#' \href{https://github.com/mapbox/concaveman}{Vladimir Agafonking's implementation}.
+#' the \link[concaveman:concaveman]{concaveman} function.
 #'
 #' @template param-las
 #' @param type character. Hull type. Can be 'convex', 'concave' or 'bbox'.

diff --git a/man/delineate_crowns.Rd b/man/delineate_crowns.Rd
diff --git a/vignettes/lidR-LAS-class.Rmd b/vignettes/lidR-LAS-class.Rmd
@@ -61,7 +61,7 @@ Here we can already see some deviations from the official las format specificati
 
 ### @header: the header
 
-A `LAS` object contains a slot `@header` that represents the header of the las file. The header is stored in a `LASheader`  object. A `LASheader` object contains two slots: `@PHB` for the public header block and `@VLR` for the variable length records. Both slots are lists labeled according to the las file format specification. See [public documentation of las file format](http://www.asprs.org/wp-content/uploads/2010/12/LAS_1_4_r13.pdf) for more information about las headers. Users should never normally have to worry about the header as long as they use functions from lidR. Everything is managed internally to ensure that objects are valid. However, users still need to know that the contents of the header are important, especially when writing `LAS` objects into las or laz files.
+A `LAS` object contains a slot `@header` that represents the header of the las file. The header is stored in a `LASheader`  object. A `LASheader` object contains two slots: `@PHB` for the public header block and `@VLR` for the variable length records. Both slots are lists labelled according to the las file format specification. See [public documentation of las file format](https://www.asprs.org/wp-content/uploads/2019/07/LAS_1_4_r15.pdf) for more information about las headers. Users should never normally have to worry about the header as long as they use functions from lidR. Everything is managed internally to ensure that objects are valid. However, users still need to know that the contents of the header are important, especially when writing `LAS` objects into las or laz files.
 
 ```{r}
 print(las@header)