Alan D. Snow

For reference, here is how CRS information is handled in rioxarray: [CRS management docs](https://corteva.github.io/rioxarray/stable/examples/crs_management.html).

> I'm wondering if an xarray accessor could work around some of the current limitations you're seeing. I think this sounds like a good idea.

This is by design. The reason this is the case is to prevent using the PROJ_DIR for a different PROJ installation that is incompatible. The PROJ database must be the...

> I'm not sure why pyproj.datadir.set_data_dir would have precedence over pyproj internal data but PROJ_DATA doesn't The reason `set_data_dir` exists is to set the data directory if it cannot be...

Related: - https://github.com/pyproj4/pyproj/discussions/1421 - https://github.com/pyproj4/pyproj/issues/705

https://github.com/OSGeo/PROJ/pull/4302

It would be good to update pyproject.toml as well.

> It would be good to update pyproject.toml as well. https://github.com/rasterio/rasterio/issues/2994#issuecomment-1877147915

The change I suggest is for this line: https://github.com/rasterio/rasterio/blob/24d0845e576158217f6541c3c81b163d873a994d/pyproject.toml#L6 It is for the build requirements as compiling with numpy 2 allows compatibility with numpy 1 & 2.

Want to hear @sgillies opinion on the syntax.