Mark Keller

- [x] We should test that stores/arrays/groups written by zarr-python are read-able by pizzarr. - [ ] We should test that stores/arrays/groups written by pizzarr are read-able by zarr-python.

See https://zarr.readthedocs.io/en/stable/_modules/zarr/attrs.html#Attributes

See https://zarr.readthedocs.io/en/stable/api/convenience.html

Fail in CI if NAMESPACE or Roxygen docs are out of date

1

**User story** Even though these are a bit redundant to commit to the repo, I think they are needed for installation from github or from source to work properly. **Preferred...

**User story** Currently, the conversion to R `integer` is not ideal. https://cran.r-project.org/web/packages/bit64/index.html **Preferred solution** **Possible alternatives**

Nice summary of the main changes: https://developmentseed.org/cloud-optimized-geospatial-formats-guide/zarr/intro.html#zarr-version-2-and-version-3 Also see https://github.com/zarr-developers/zarr-python/issues/1777

Add indexing/slicing docs

1

Currently, arrays can be indexed using a list of `slice` and `"..."`. We should document this on the pkgdown site better.