Fix CRAN check

r-lidar · Apr 20, 2020 · 0b59d85 · 0b59d85
1 parent a58ae82
commit 0b59d85
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 6 deletions.
diff --git a/DESCRIPTION b/DESCRIPTION
@@ -3,7 +3,7 @@ Type: Package
 Title: Airborne LiDAR Data Manipulation and Visualization for Forestry
     Applications
 Version: 2.2.4
-Date: 2020-03-04
+Date: 2020-04-20
 Authors@R: c(
     person("Jean-Romain", "Roussel", email = "jean-romain.roussel.1@ulaval.ca", role = c("aut", "cre", "cph")),
     person("David", "Auty", email = "", role = c("aut", "ctb"), comment = "Reviews the documentation"),

diff --git a/NEWS.md b/NEWS.md
@@ -24,11 +24,9 @@
 
 5. `grid_metrics()` returns a raster full of NAs instead of failing if a `RasterLayer` is given as a layout but this layer does not encompase the point cloud
 
-6. `opt_output_file()` now normalizes the path.
+6. `opt_output_file()` now applies tilde-expansion to the path.
 
-7. When processing by file with an raster output, uutomatic chunk extension to match with a raster resolution now perform a tighter extension.
-
-## lidR v2.2.3 (Release date: 2020-03-02)
+7. When processing by file with an raster output, automatic chunk extension to match with a raster resolution now perform a tighter extension.
 
 #### FIXES
 

diff --git a/R/utils_catalog_options.r b/R/utils_catalog_options.r
@@ -215,7 +215,7 @@ opt_output_files = function(ctg)
   if (usefilename & opt_chunk_size(ctg) > 0)
     message("ORIGINALFILENAME template has been used but the chunk size is not 0. This template makes sense only when processing by file.")
 
-  value <- normalizePath(value, mustWork = FALSE)
+  value <- path.expand(value)
   ctg@output_options$output_files <- value
   return(ctg)
 }