issues: 1832117967

This data as json

id node_id number title user state locked assignee milestone comments created_at updated_at closed_at author_association active_lock_reason draft pull_request body reactions performed_via_github_app state_reason repo type
1832117967 I_kwDOAMm_X85tM-bP 8040 New Xarray accessor for DEMs through xDEM 28896516 open 0     3 2023-08-01T22:30:45Z 2023-09-28T21:03:07Z   NONE      

Hi all,

(Co-opening in rioxarray due to the raster nature of the accessor: https://github.com/corteva/rioxarray/issues/687)

Following what is asked in the doc, I'm letting you know that we intend to write an xarray accessor to enable functions specific to digital elevation models in our package xDEM! :slightly_smiling_face:

The accessor would mirror all the functionalities we have (and future ones): - Vertical CRS transformation (not yet supported by rasterio so built on top of pyproj directly, would build on top of rioxarray in the accessor), - Terrain attributes (I see a bit of overlap with xarray-spatial in "Surface": https://xarray-spatial.org/user_guide/surface.html for some of these; we have more published versions which can be parametrized, so I guess that's OK? I could start a discussion there to coordinate future development), - 3D registration, - Terrain corrections, - Error estimation and propagation (may be moved to GeoUtils as not specific to DEMs but all rasters, see https://github.com/pydata/xarray/issues/8041; eventually using ObsArray).

I was thinking of using the accessor name dem, e.g.: ds.dem.to_vcrs(), ds.dem.profile_curvature() or ds.dem.coregister(). I didn't catch any overlap with other efforts. Would that work fine?

Thanks! (and for the great work on xarray!)

 
{
    "url": "https://api.github.com/repos/pydata/xarray/issues/8040/reactions",
    "total_count": 0,
    "+1": 0,
    "-1": 0,
    "laugh": 0,
    "hooray": 0,
    "confused": 0,
    "heart": 0,
    "rocket": 0,
    "eyes": 0
}
     13221727 issue

Links from other tables