Edzer Pebesma
Edzer Pebesma
```r st_make_valid(pol) %>% st_cast("MULTIPOLYGON" ) %>% st_cast("POLYGON") ``` works, `sf_remove_holes` is not an `sf` function.
> How to specify which unit is used? ```r units::set_units(0.1, degree) # 0.1 [°] ```
> Can it be told not to install in-tree? I don't know.
```r > times user.self sys.self elapsed user.child sys.child n logical 1 0.756 0.029 0.792 0 0 10000 FALSE 2 0.261 0.001 0.263 0 0 20000 FALSE 3 0.386 0.016 0.401...
```r > times user.self sys.self elapsed user.child sys.child n logical 1 0.703 0.030 0.733 0 0 10000 FALSE 2 0.226 0.000 0.226 0 0 20000 FALSE 3 0.340 0.000 0.340...
@kadyb thanks! @rhijmans `terra` doesn't write logical `NA`'s: ```r library("sf") # Linking to GEOS 3.11.1, GDAL 3.6.2, PROJ 9.1.1; sf_use_s2() is TRUE library("terra") # terra 1.7.3 n = 3 df...
To make any progress, we need data points and reprexes, not experience. I can only see this: ```r library(sf) # Linking to GEOS 3.11.1, GDAL 3.6.2, PROJ 9.1.1; sf_use_s2() is...
How and where would you suggest this to be documented?
Indeed, whereas with #2059 ```r require(sf) # Loading required package: sf # Linking to GEOS 3.11.1, GDAL 3.6.2, PROJ 9.1.1; sf_use_s2() is TRUE #> Loading required package: sf #> Linking...
I tried to improve the docs, and added support for area units to specify cellsize: ```r library(sf) # Linking to GEOS 3.11.1, GDAL 3.6.2, PROJ 9.1.1; sf_use_s2() is TRUE #...