Python library designed to easily manipulate CloudSat and GOES-R and generate labeled images containing cloud types.
Motivation:
Remote sensors aboard artificial satellites generate a lot of information every day. This information acquires spatial value when it can be transformed into something understandable to humans, such as the classification of satellite images. In this case, we focus on the classification of clouds in satellite images since knowing the type of cloud we can know its main characteristics and thus contribute to improve climate models and weather predictions. We use images from the ABI radiometer on board the GOES-16 geostationary satellite and develop two methods to classify the clouds observed in them: 1- We implement the Day Microphysics algorithm (\citar geocast ) which approximately shows each cloud type in a different color. 2- We developed methods that allow to co-locate data from the CloudSat heliosynchronous satellite with GOES-16 images, being able to obtain a Pandas dATAFRAME with two columns, one is the pixels of the GOES images and the other gives a label to those pixels (provided by CloudSat) about the type of cloud that exists in those pixels.
As for the second method (co-location of GOES and CloudSat), although there is literature on the subject we did not find any released code showing the procedure. Perhaps it could be done with other software that are usually paid. That is why we developed Stratopy, so that in a free and simple way it can be used and generate a data structure ready to be used for example as input in supervised machine learning algorithms.
Requirements:
You need Python 3.9+ to run Stratopy. The following libraries will be installed:
Installation:
With pip:
pip install stratopy
Via git
pip install git+https://github.com/paula-rj/StratoPy.git
Warning: If you install [Stratopy] in a Colab Notebook, you must also upgrade Numpy
!pip install numpy --upgrade
and then restart sesion. After that, you can work as usuall. This is due to a conflict between Numpy and Pyorbital that afects only Colab Notebooks.
Quick information and references:
CloudSat is an artificial satellite, with a sun-synchronous orbit which has a revisit period of 16 days. Its most important instrument is the Cloud Profiling Radar (CPR), which returns verftical profiles of clouds in particular. The satellite was launched in 2006 and since 2011 its battery suffers a failure. Given that the radar needs energy to work, only daytime products are usefull since that year on. In Stratopy, we developed a pipeline that includes the 2B-CLDCLASS product, a product of level 2 of processing that contains the type of cloud that the radar found along the satellite's track around the Earth.
The following web pages are usefull references:
GOES-16 is an artificial satellite launched in 2016. It contains the Advances Baseline Radiometer (ABI) on board, a multiespectral sensor that can take images in 16 different bands or channels. It is a geostationary satellite, located in a central longitud of -75° which allows ABI to take images of nearly the whole American continet in a mode called "Full Disk". The pipelines developed in Stratopy includes the Cloud and Moisture (CMI) products of level 2 of processing its two presentations: single band and Multi-band (MCMIPF). We also included the algorithm needed to create a Day Microphysics RGB (based on Souza's code), which shows (aproximately) different types of clouds in different colors. The GOES-16 team provides a Day Microphysics Quickguide in order to have some reference for the interpretation of this RGB image. The following webpages contain usefull information about the satellite and its products:
Authors
- Paula Romero <paula.romero@mi.unc.edu.ar> (IATE-OAC-CONICET, FaMAF-UNC).
- Julián Villa <jvilla@iafe.uba.ar> (IAFE-UBA-CONICET).
Metadata
Release files for StratoPy 0.1.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 | Actions |
|---|---|---|---|---|
| StratoPy-0.1.1.tar.gz | 69.9 MB | Without provenance | Details for StratoPy-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| StratoPy-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for StratoPy-0.1.1-py3-none-any.whl |
Total release size: 69.9 MB
Release files / StratoPy-0.1.1.tar.gz
| Download URL | StratoPy-0.1.1.tar.gz |
|---|---|
| Size | 69.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f20033584e64fdde463c9e377169275611cf8c17c54b022941c1acaec3e3d32f
|
|
BLAKE2b-256 checksum How to use checksums |
80f00657f28f80561bf6edd693fc3c02a195ccdda46e5cbb68ab92e62efb1a76
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Release files / StratoPy-0.1.1-py3-none-any.whl
| Download URL | StratoPy-0.1.1-py3-none-any.whl |
|---|---|
| Size | 16.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fbd1dcebafd862ab2dc195817b3bab7489a2a61fec0b8a540eece77dad193d3d
|
|
BLAKE2b-256 checksum How to use checksums |
78ba89c888f2d0c023b706e940b921513fd8fbb4c0ca71b9efc17cb1503dc6f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for StratoPy 0.1.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.
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.