xncml
Documentation and Support |
|
Open Source |
|
Coding Standards |
|
Development Status |
Tools for opening and manipulating NcML (NetCDF Markup Language) files with/for xarray.
These tools allow you to modify NcML by:
Adding or removing global attributes
Adding or removing variable attributes
Removing variables and dimensions
and read NcML files into xarray.Dataset objects:
import xncml
ds = xncml.open_ncml("large_ensemble.ncml")
See doc for more information.
Installation
Stable release
To install xncml, run this command in your terminal:
python -m pip install xncml
This is the preferred method to install xncml, as it will always install the most recent stable release.
If you don’t have pip installed, this Python installation guide can guide you through the process.
From sources
The sources for xncml can be downloaded from the Github repo.
You can either clone the public repository:
git clone git@github.com:xarray-contrib/xncml/
Or download the tarball:
curl -OJL https://github.com/xarray-contrib/xncml/tarball/main
Once you have a copy of the source, you can install it with:
python -m pip install .
Metadata
Release files for xncml 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| xncml-0.5.1.tar.gz | 883.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| xncml-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 904.7 kB
Release files / xncml-0.5.1.tar.gz
| Download URL | xncml-0.5.1.tar.gz |
|---|---|
| Size | 883.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c5eacdcd91a253eb375d83561676d9f0456ecbf3f30d20bd208b3b82f5ffcd77
|
|
BLAKE2b-256 checksum How to use checksums |
0044201b1ae1c3674362e744a49802e7a546ad6eb4eb31050b6525e82e1833e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2025.
Transparency logRelease files / xncml-0.5.1-py3-none-any.whl
| Download URL | xncml-0.5.1-py3-none-any.whl |
|---|---|
| Size | 21.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1a66cda6dd335c5a86d3b03c3083f7467f0b0868abd040c344e39a234695dee
|
|
BLAKE2b-256 checksum How to use checksums |
4e7a80a033c7d6e5916246029a0f6c46bc8c3f519c5d71611de4ed5d6e950021
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2025.
Transparency logSecurity for xncml 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xncml-0.5.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 2, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.