Alan D. Snow

> I'm not too keen to drop coords-based .geobox though, as this is the most robust way we found so far for preserving geo-registration information through data transformations. I agree...

Should just be for the data vars.

Remembered this today with something else I was working on. Is this a change you would like to see?

Sounds great 👍.

Ping to leave open.

Thanks for the explanation. In that case, would it make sense to export as WKT2 on the spatial_ref attribute only since it is only used by GDAL?

> Why not just defining the CURL_CA_BUNDLE env var that must work with GDAL and PROJ now ? That is the current plan. However, if there are other programs using...

> cpl_set_curl_ca_bundle() That would be useful as well. It would be nice if it set the PROJ CA Bundle path as well if the method is available to set it.

> what's a sane scenario where you'd want to replace the CA bundle just for GDAL/PROJ but not anything else? As an application/library, automatically setting environment variables that might be...

`pyproj` is able to set the CA Bundle path using the PROJ C-API [here](https://github.com/pyproj4/pyproj/blob/eba17363053d8d7d3d869a206df2bcb8c8a604be/pyproj/network.py). It would be nice to be able to implement something similar for `rasterio`.