GSV interface
A tool for accessing the GSV data from FDB and converting it into xarray.
Core idea
The current approach can be summarized in three steps:
-
Use
pyfdbto request data from theFDB. This will return apyfdb.Dataretrieverfile-like object from which you can read all GRIB messages matching a given request. -
Use
eccodes-pythonto decode the necessary information of each GRIB message (data, coordinates, attributes...). A custom iterator (MessageIterator) is used to iterate over each message in thepyfdb.DataRetrieverobject. -
If requested by the user, interpolate the result to a regular LonLat grid of choice.
All requested messages are packed in a single xarray.Dataset object and returned to the user.
Installation instructionss
The gsv-interface package is available to install through pip. It can be installed with the folloeing command:
pip install gsv-interface
Checking installation
Top check the installation was succesfull run Python and try to import gsv.
>>> import gsv
>>> gsv.__version__
This should print the version number of the chosen release.
Dependencies
The followin non-Python libraries are required:
- ecCodes: https://github.com/ecmwf/eccodes
- fdb: https://github.com/ecmwf/fdb
This tool depends on the following Python modules, which are automatically installed though pip.
- "pyfdb==0.1.2",
- "numpy",
- "xarray",
- "eccodes",
- "astropy-healpix",
- "dask",
- "netcdf4",
- "cfgrib",
- "sparse",
- "cdo",
- "smmregrid==0.1.1",
- "polytope-client",
- "pyyaml",
- "jinja2",
- "packaging"
Documentation
Docs based on sphinx can be found in the docs/ directory of the repository.
Build dependencies for the docs can be installed with the following command (it's recommended to run it in a clean environment):
pip install -r requirements.txt
Then the docs can be built with:
make html
The resulting html docs can be then found in:
docs/build/html/index.html
Metadata
Release files for gsv-interface 2.18.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 |
|---|---|---|---|---|
| gsv_interface-2.18.0.tar.gz | 106.3 kB | Without provenance | Details for gsv_interface-2.18.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gsv_interface-2.18.0-py3-none-any.whl | Python 3 | none | any | Details for gsv_interface-2.18.0-py3-none-any.whl |
Total release size: 261.7 kB
Release files / gsv_interface-2.18.0.tar.gz
| Download URL | gsv_interface-2.18.0.tar.gz |
|---|---|
| Size | 106.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9941748125311193ca5034f86f95cd1e739cdb0429b2ec60e086acfd87237099
|
|
BLAKE2b-256 checksum How to use checksums |
733a47a7d7cad93d1958b87a48318afd93a96c44becd720f47c68b68fd95cdbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Release files / gsv_interface-2.18.0-py3-none-any.whl
| Download URL | gsv_interface-2.18.0-py3-none-any.whl |
|---|---|
| Size | 155.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
88e4b9e3cb337b55a044bf9497da19f97e8bbe31ddee61c064043f03507c5e0e
|
|
BLAKE2b-256 checksum How to use checksums |
e21484f6175bdd38d6d9806e0685ba52fc7fe53ba7cd5ddf0427c8bd18e33086
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.16
|
Security for gsv-interface 2.18.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.