Edzer Pebesma
Does it help if you set the `GDAL_CACHEMAX` environment variable before loading any package that uses GDAL? See [here](https://gdal.org/en/stable/user/configoptions.html) - it seems to take 5% of the available memory by...
I would suggest to figure out which projection you want to use, and project your data to that; this could be specified in some way that `st_transform()` understands. What is...
> As a package developer I often want to grab the geometry column from an sf object. For that, `sf` provides the generic `st_geometry()`.
> There are a good handful of folks I count three, and pretty different ones.
`s2_is_full()` would be great to have!
Is this not an issue that could/would be solved at the level of PROJ?
See https://github.com/r-spatial/sf/issues/2415 ```r > st_bbox(st_as_stars()) |> st_transform("+proj=eck4") xmin ymin xmax ymax -16921203 -8460601 16921203 8460601 ... > st_bbox(vect(out)) xmin ymin xmax ymax -16921203 -8424632 16908719 8460601 ``` Or the longer...
```r st_bbox(st_as_stars()) |> st_as_sfc() |> st_set_crs(NA) |> st_segmentize(1) |> st_set_crs("OGC:CRS84") |> st_transform("+proj=eck4") |> plot(axes = TRUE) ``` 
An attempt to cut out the visible part for orthographic projections is found [here](https://r-spatial.org/book/08-Plotting.html#sec-transform), but I'd admit it's pretty ugly.
Looks like you've visited the warning earlier: https://github.com/r-spatial/s2/blob/main/src/s2/util/coding/coder.h#L465