Open rhugonnet opened 11 months ago
Thank you for sharing, that looks useful.
And so I am wondering: where do you think those functionalities should live if we build an xarray accessor?
I think it depends on the scope of what you would like to support. There is likely room to migrate some of the functionality into existing libraries if that is your goal.
For example:
reproject
logic makes sense to merge with rio.reproject
.polygonize
logic makes sense to merge with geocube
ref.Then, for the things that don't fit in other libraries, you could make geo-utils an expansion pack on existing libraries.
Hi all,
We are planning to build on top of
rioxarray
for end-users focusing on analysis of EO data by building accessor in our packages GeoUtils and xDEM for raster/vector and DEM analysis, respectively, which are currently built on top ofrasterio
andgeopandas
. See: https://github.com/pydata/xarray/issues/8040 and https://github.com/pydata/xarray/issues/8041I don't see much overlap for xDEM, except that we could use vertical CRS reprojection through
rioxarray
if one day we implement it inrasterio
, for now not possible (see https://github.com/rasterio/rasterio/issues/2433).For GeoUtils, part of the package's functionalities are closely linked to georeferencing and aim to simplify the interaction raster/raster or raster/vector, like the
reproject_match
function ofrioxarray
. Those did not exist inrasterio
, but they have been more of a focus inrioxarray
andgeocube
. In theRaster
andVector
classes of GeoUtils, we tried to implement these "convenience" ops for all type of operations and the two objects.And so I am wondering: where do you think those functionalities should live if we build an
xarray
accessor? Should we keep them in GeoUtils like is done on top ofrasterio
(e.g.,Raster.reproject(ref)
,Raster.polygonize(ref)
) and implementds.geo.reproject(ref)
andds.geo.polygonize(ref)
) by simply wrapping what is done, or should we try to make those available directly inrioxarray
andgeocube
(but then the functioning ofrioxarray
would stray quite a bit from that ofrasterio
)?More details in our doc for match-reference ops: https://geoutils.readthedocs.io/en/stable/core_match_ref.html
Thanks for all the great work! :smile: