Joe Hamman
Joe Hamman
We should either remove the CSV formatted raw FIA data or rename it to use the lower case naming convention. Then update this section in the catalog: https://github.com/carbonplan/data/blob/b8b67881e1e0a00889aedfad518f2eed59b7d878/catalogs/fia.yaml#L13-L25
We should develop a set of canonical grid files and definitions. We currently have our project grids defined in terms of a CRS and extent, e.g. https://github.com/carbonplan/data/blob/933782082e3a788bed64ecb5541af36919acdef8/carbonplan_data/utils.py#L27-L49 These should remain...
The Rust crate this project is based on provides an async interface. However, this project provides a synchronous interface. Would it be possible to expose an async interface here (perhaps...
In Zarr-Python 2, we had the ZipStore. This hasn't been implemented yet in v3 but will need to be before the 3.0 release. Fsspec has a ZipStore but I don't...
We've landed some important fixes to the v3 branch in the past two weeks. I'd like us to make another alpha release soon (perhaps on Monday July 8th?). The following...
This PR adds tests to insure that our store/array/group classes are serializable w/ using pickle and can be reliably roundtripped. This is important for Dask and other libraries that need...
In addition to the top-level API compatibility layer, we are also seeing that some applications are interacting with the `Array` class constructor directly. For example, see this from [Dask](https://github.com/dask/dask/blob/a291fd2c36ccad4b644b9ac25d4bf41c7f649e63/dask/array/core.py#L3595-L3597). ```python...
We are getting close to releasing zarr-python 3. Based on the imports in Kerchunk, you should pin to `
This is a working draft of the v3 ZIP file store specification. xref: - https://github.com/zarr-developers/zarr-python/pull/2078 - https://github.com/zarr-developers/zarr-specs/issues/103
closes #307