Welcome to the repository of ecubevis
ecubevis: Earth CUBE VISualization with Python. Intended for the interactive exploration of n-dimensional (2D, 3D, 4D or 5D spatio-temporal) arrays on Jupyterlab. Supports both xarray.Dataset/DataArray (with metadata) or numpy.ndarray objects.
How to install
Install ecubevis from pypi:
pip install ecubevis
If installing cartopy with pip is not working, use conda:
conda install cartopy
If cartopy kills your Jupyter notebook kernel try this:
pip install shapely --upgrade --force-reinstall --no-binary shapely
How to use
Import the library:
import ecubevis as ecv
The main function in ecubevis is ecv.plot(). In interactive mode, the plot comes with sliders (thanks to hvplot/holoviews) allowing easy exploration of multi-dimensional data as 2D arrays across the time and additional dimensions. Under the hood, ecv.plot() calls one of the following functions depending on the data type:
-
ecv.plot_ndarray(): For plotting an in-memorynumpy.ndarrayobject with 2, 3, 4 or 5 dimensions (ndarrays do not carry metadata so the dimensions are given with thedimensionsargument). The function can take a tuple of 2D ndarrays, even with different grid/image size. -
ecv.plot_dataset(): For plotting an in-memoryxr.Datasetorxr.DataArrayobjects with 2, 3, or 4 dimensions. The dimensions expected are [lat, lon] for 2D arrays, [time, lat, lon] for 3D arrays or [time, level, lat, lon] for 4D arrays.
Examples
ecubevis will allow you to create:
| Interactive | Static |
|---|---|
plots of in-memory 2D, 3D and 4D xr.Dataset or xr.DataArray objects: |
mosaics of in-memory 3D and 4D xr.Dataset or xr.DataArray objects: |
plots of in-memory 2D, 3D and 4D numpy.ndarray objects (composition thanks to holoviews): |
plots of in-memory 2D, 3D and 4D numpy.ndarray objects: |
plots of in-memory xr.Dataset or xr.DataArray while sub-setting across dimensions: |
plots of a tuple of in-memory 2D numpy.ndarray objects: |
Metadata
Release files for ecubevis 1.0.2
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 | Actions |
|---|---|---|---|---|
| ecubevis-1.0.2.tar.gz | 20.8 kB | Without provenance | Details for ecubevis-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ecubevis-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for ecubevis-1.0.2-py3-none-any.whl |
Total release size: 41.8 kB
Release files / ecubevis-1.0.2.tar.gz
| Download URL | ecubevis-1.0.2.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88770cea2c6d574bdbfece571fb66ff93e9f1cf558675ce956064a069e33034a
|
|
BLAKE2b-256 checksum How to use checksums |
b590091ae97a5eeb91c4981a0958e2d911a4a59d77032c1b31bed04f71c9b254
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.13
|
Release files / ecubevis-1.0.2-py3-none-any.whl
| Download URL | ecubevis-1.0.2-py3-none-any.whl |
|---|---|
| Size | 21.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f5b0d536f06d20ed9f3a7dd553d6f9f8f344880d8c76af3adf8bdba4b592a5a3
|
|
BLAKE2b-256 checksum How to use checksums |
0771428b8817161cfc1793934d22aa65d45568ba581c44516fddff889d1618e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.13
|
Security for ecubevis 1.0.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.