Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature parity with xarray #169

Open
2 of 4 tasks
rafaqz opened this issue May 15, 2021 · 1 comment
Open
2 of 4 tasks

Feature parity with xarray #169

rafaqz opened this issue May 15, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@rafaqz
Copy link
Owner

rafaqz commented May 15, 2021

With #168 this is surprisingly close, besides all the things that GeoData does that xarray can't do.

But clearly missing are:

  • Dask-like processing for larger-than-memory files. This should already work in a simple way by broadcasting from one open file to another - the file can be larger than ram. But its not parallel or distributed. I am unlikely to write this unless someone specifically needs it, as I never work with single files larger than ram. But maybe Dagger.jl can help here?
  • netcdf layer-specific compression settings.
  • easily adding new layers to an existing stack
  • split apply combine
    ?

Also surprisingly, most of the "technical vision" for xarray is already possible in GeoData.jl due to composability of julia packages.

Battle hardening is probably one of the main things missing 😆

@felixcremer
Copy link
Contributor

For the first point we can use YAXArrays.jl or later on DiskArrayEngine.jl . Especially, after we finished JuliaDataCubes/YAXArrays.jl#249 so that these two packages are playing more nicely together.

@rafaqz rafaqz added the enhancement New feature or request label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants