Edzer Pebesma
```r intersected_SF
Did you come to that expectation because of the documentation, or was it rather what you hoped for? Sometimes, setting a non-zero precision helps in getting rid of slivers in...
Wow. This is what is happening, afaict: ```r > cut(nc$SID74, pretty(nc$SID74), include.lowest=TRUE) [1] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [8] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [0,0.2] [15] [0,0.2] [0,0.2]...
A consequence of not setting a precision: ```r > st_overlaps(st_set_precision(st_no_overlap(st_sf(geometry = b)),1e8)) Sparse geometry binary predicate list of length 3, where the predicate was `overlaps' 1: (empty) 2: (empty) 3:...
> By the way, stars::read_stars("hd2011010000.scu") fails with the same error message. I see no errors, and ```r library(stars) # Loading required package: abind # Loading required package: sf # Linking...
So terra puts a raster without georeference on the unit square, where GDAL (and stars) put them on the rectangle from (0,0) to (rcol,nrow). Is that on purpose?
Yes, sorry, I forgot to say that I was looking at stars from github, `remotes::install_github("r-spatial/stars")`
We need to see the output of the error; could you pls follow the instructions here: https://github.com/r-spatial/sf/issues/1685#issuecomment-854889295 ?
> @edzer does debian bundle static libraries? Ubuntu 20.04 with ubuntugis-unstable PPA has both, static and dynamic proj libraries installed.
@rsbivand do you remember why `--static` was added, and by whom?