pangaeapy - a Python module to access and analyse PANGAEA data
Background
PANGAEA (https://www.pangaea.de) is one of the world's largest archives of this kind offering essential data services such as data curation, long-term data archiving and data publication. PANGAEA hosts about 400,000 datasets comprising around 17.5 billion individual measurements (Aug. 2020) and observations which have been collected during more than 240 international research projects. The system is open to any project, institution or individual scientist using, archiving or publishing research data.
Since the programming languages Python and R have become increasingly important for scientific data analysis in recent years, we have developed 'pangaeapy' a new, custom Python module that considerably simplifies typical data science tasks.
Given a DOI, pangaeapy uses PANGAEA’s web services to automatically load PANGAEA metadata into a dedicated python object and tabular data into a Python Data Analysis Library (pandas) DataFrame with a mere call of a specialized function. This makes it possible to integrate PANGAEA data with data from a large number of sources and formats (Excel, NetCDF, etc.) and to carry out data analyses within a suitable computational environment such as Jupyter notebooks in a uniform manner.
Installation
- Source code from GitHub
pip install git+https://github.com/pangaea-data-publisher/pangaeapy.git
- Wheels for Python from PyPI
pip install pangaeapy
Usage
from pangaeapy import PanDataSet
ds = PanDataSet(787140)
print(ds.title)
print(ds.data.head())
Examples
Please take a look at the example Jupyter Notebooks in the examples folder.
Documentation
https://pangaea-data-publisher.github.io/pangaeapy/
Running the tests
The tests are located in the test directory. You can run them by executing pytest or tox in the root directory.
Cite as
Robert Huber, Egor Gordeev, Markus Stocker, Aarthi Balamurugan, & Uwe Schindler (2020). pangaeapy - a Python module to access and analyse PANGAEA data. Zenodo. http://doi.org/10.5281/zenodo.4013940.
Metadata
Release files for pangaeapy 1.1.3
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 |
|---|---|---|---|---|
| pangaeapy-1.1.3.tar.gz | 843.1 kB | Without provenance | Details for pangaeapy-1.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pangaeapy-1.1.3-py3-none-any.whl | Python 3 | none | any | Details for pangaeapy-1.1.3-py3-none-any.whl |
Total release size: 914.2 kB
Release files / pangaeapy-1.1.3.tar.gz
| Download URL | pangaeapy-1.1.3.tar.gz |
|---|---|
| Size | 843.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
613c87b5720299a0d94655247b000efa40deaac8451d8c856a84c65c727dd6b5
|
|
BLAKE2b-256 checksum How to use checksums |
0995369842c0b578c7315c8bc34e0193aedebf61519e8f763bde0c82cf46e90f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Release files / pangaeapy-1.1.3-py3-none-any.whl
| Download URL | pangaeapy-1.1.3-py3-none-any.whl |
|---|---|
| Size | 71.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9e4e9a0d44b00e8face85afd90d1db4c66892a8bf78e385795cac3b50e51286c
|
|
BLAKE2b-256 checksum How to use checksums |
119274ba39747fcd30feb46a610569b4c6a907686deb2be40e4342ecd130da30
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.7
|
Security for pangaeapy 1.1.3
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.