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 Request: Additional parallel IO format support: ASDF, ph5, or similar #3035

Closed
k-a-mendoza opened this issue Jun 19, 2019 · 2 comments

Comments

@k-a-mendoza
Copy link

k-a-mendoza commented Jun 19, 2019

Problem description

Currently, Xarray supports reading/writing a variety of dataformats. Geoscience data in particular is a stated use-case domain. However, in the documentation, it seems as though geoscience mostly refers to hydrologic and atmospheric data.

It would be very useful to more domains of geoscience if xarray also supported read/writes to formats encountered regularly in geophysics, either something like ph5, ASDF, or the like. Already projects like obsplus deliver some xarray->seismic formats -> xarray functionality, but have yet to venture into the parallel read/write operations that make xarray so attractive.

I am not sure what the overhead would be in adapting xarray to use these existing packages, or in creating common interfaces for use with these packages.

@TomNicholas
Copy link
Member

TomNicholas commented Apr 7, 2020

It should be possible to implement a new backend in xarray now - we've already done it for multiple file formats.

However, I suspect that if we completed the project to provide a Flexible API for Storage Backends, then the path to this would become simpler. At the moment each new storage format has to be special-cased within xarray code itself (e.g. zarr), but we want to get to a position where that I/O responsibility is delegated out to other libraries, probably via an entrypoint. Then it would be much easier (and quicker) to develop the necessary interfaces for the formats you mention.

@dcherian
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants