jupyterlab_thredds
JupyterLab dataset browser for THREDDS catalog
Can inject iris/xarray/leaflet code cells into a Python notebook of a selected dataset to further process/visualize the dataset.
Prerequisites
- JupyterLab,
pip install jupyterlab - ipywidgets,
jupyter labextension install @jupyter-widgets/jupyterlab-manager, requirement for ipyleaflet - ipyleaflet,
jupyter labextension install jupyter-leaflet, to load a WMS layer - iris,
conda install -c conda-forge iris
Installation
pip install jupyterlab_thredds
jupyter labextension install @ewatercycle/jupyterlab_thredds
Usage
- Start Jupyter lab with
jupyter lab - In Jupyter lab open a notebook
- Open the
THREDDStab on the left side. - Fill the catalog url
- Press search button
- Select how you would like to open the dataset, by default it uses iris Python package.
- Press a dataset to insert code into a notebook
Development
For a development install, do the following in the repository directory:
pip install -r requirements.txt
jlpm
jlpm build
jupyter labextension link .
jupyter serverextension enable --sys-prefix jupyterlab_thredds
(jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab.)
To rebuild the package and the JupyterLab app:
jlpm build
jupyter lab build
Watch mode
# shell 1
jlpm watch
# shell 2
jupyter lab --ip=0.0.0.0 --no-browser --watch
Release
To make a new release perform the following steps:
- Update version in
package.jsonandjupyterlab_thredds/version.py - Record changes in
CHANGELOG.md - Make sure tests pass by running
jlpm testandpytest - Commit and push all changes
- Publish lab extension to npmjs with
jlpm buildandjlpm publish --access=public - Publish server extension to pypi with
python setup.py sdist bdist_wheelandtwine upload dist/* - Create GitHub release
- Update DOI in
README.mdandCITATION.cff
Metadata
Release files for jupyterlab-thredds 0.5.0
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 |
|---|---|---|---|---|
| jupyterlab_thredds-0.5.0.tar.gz | 14.0 kB | Without provenance | Details for jupyterlab_thredds-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyterlab_thredds-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for jupyterlab_thredds-0.5.0-py3-none-any.whl |
Total release size: 26.7 kB
Release files / jupyterlab_thredds-0.5.0.tar.gz
| Download URL | jupyterlab_thredds-0.5.0.tar.gz |
|---|---|
| Size | 14.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6fa21d2a235210373c3d8413f645f39b24887557727ffe1cf56f43ea2c7d2ee4
|
|
BLAKE2b-256 checksum How to use checksums |
5a84318d3ec0d9346feb8b3ff45854c7b95feea670483260549b7a0d663a5308
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.9
|
Release files / jupyterlab_thredds-0.5.0-py3-none-any.whl
| Download URL | jupyterlab_thredds-0.5.0-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f64444003771cd4a3dc747796cd6c20a9feaae2720c7f2777cace4d59bf33af
|
|
BLAKE2b-256 checksum How to use checksums |
71c790edfee4ba2e5df489f824e62ecea2cd9c921bad0a00c0f1f043d6a62dd2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.24.0 setuptools/49.1.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.6.9
|
Security for jupyterlab-thredds 0.5.0
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.