xarray-schema

xarray-schema copied to clipboard

parsing method in xarray-schema

4

hi, thanks for the really great package. I was wondering if there is any plan to also provide methods for **parsing** array-like data following the pre-defined schemas. In particular, similar...

giovp

Minimal Dataset coords and dims validation

3

What would be the minimal implementation to be merged here? My use case is simply to check if a dataset has specific coords and dims. I could go one step...

ljstrnadiii

Specifying a schema in terms of a Protocol

2

Hello! Thanks for making `xarray-schema`! It would be great to be able to write a xarray schema in terms of a `typing.Protocol`. This would enable the schema to be used...

rsokl

This issues simply cross references the integration of xarray-schema within [Pandera](https://pandera.readthedocs.io/en/stable/). See https://github.com/pandera-dev/pandera/issues/705 for progress there. While we may continue to develop functionality here, long term goal to migrate to...

jhamman

We want to be able to compare/validate string type attributes in xarray objects such as _name_ and _dimensions_. The current implementation includes a direct string comparison but it would be...

jhamman

A key feature of `xarray.Dataset` is that all dimensions of the same name must have the same sizes across DataArrays. For this reason, a Dataset schema that requires different sizes...

paiforsyth

Serialize/ deserialize with cattrs

1

Cattrs (https://pypi.org/project/cattrs/) is a powerful library for automatic serialisation/ deserialisation of hierarchical data. It seems to me that it could be valuable to use it to implement the various `to_json`...

paiforsyth

One way users may want to generate schemas is from xarray objects directly. We could add a utility here that supports this workflow. This could be a function ```python schema...

jhamman

To return or not to return Dataset/DataArray during `validate`

1

Before the major reorg `validate` returned a DataArray or Dataset but now it doesn't. Was that intentional @jhamman ? Or should we add back in the return? I personally like...

orianac

[pre-commit.ci] pre-commit autoupdate

1

updates: - [github.com/pre-commit/pre-commit-hooks: v4.5.0 → v5.0.0](https://github.com/pre-commit/pre-commit-hooks/compare/v4.5.0...v5.0.0) - [github.com/psf/black: 23.10.1 → 24.10.0](https://github.com/psf/black/compare/23.10.1...24.10.0) - [github.com/PyCQA/flake8: 6.1.0 → 7.1.1](https://github.com/PyCQA/flake8/compare/6.1.0...7.1.1) - [github.com/PyCQA/isort: 5.12.0 → 5.13.2](https://github.com/PyCQA/isort/compare/5.12.0...5.13.2) - [github.com/pre-commit/mirrors-prettier: v3.0.3 → v4.0.0-alpha.8](https://github.com/pre-commit/mirrors-prettier/compare/v3.0.3...v4.0.0-alpha.8)

pre-commit-ci[bot]