perseo-perturbations
Python Ecosystem for Remote Sensing & Earth Observation (PERSEO) PERTURBATIONS package for computing geodynamics displacements (Plate Tectonics, Solid Earth Tides) and atmospheric delays (Ionospheric, Tropospheric) needed for SAR products analysis, together with a Geomagnetic Field model (IGRF-14).
Features
Atmospheric Delays
Correction of SAR signal propagation delays through the Earth's atmosphere.
- Tropospheric Delay: Vienna Mapping Function 3 (VMF3) model with precomputed Legendre coefficients
- Hydrostatic (dry) and wet components
- Station grid point coordinates (1°×1° and 5°×5° grids)
- Ionospheric Delay: Total Electron Content (TEC) based dispersive medium model
- Frequency-dependent phase advance
Geodynamics Displacements
Accounting for solid Earth deformations affecting SAR geolocation and phase interpretation.
- Earth Solid Tides: periodic crustal deformations from Moon and Sun gravitational attraction
- Python wrapper of the IERS Conventions (2003)
solid.forcode by Dennis Milbert - Vertical displacements up to ~40 cm, horizontal up to ~10 cm
- Python wrapper of the IERS Conventions (2003)
- Plate Tectonics (Secular Motion): ITRF2014 plate motion model
- Linear displacement over time, mm/year to cm/year velocities
Geomagnetic Field
- IGRF-14: 14th iteration of the International Geomagnetic Reference Field (released October 2024)
- Spherical harmonic model up to degree 13
- Valid from 1900 to 2030
- Geocentric and geodetic (WGS84) coordinate support
- Output components: radial, southward, eastward (geocentric) / east, north, up (geodetic)
- Derived magnetic inclination and declination
Installation
pip install perseo-perturbations
Note: This package uses a Fortran wrapper for solid tide computations and requires a working Fortran compiler for building from source. Pre-built wheels are available on PyPI.
License
This project is licensed under the MIT License. See the LICENSE.txt file for details.
Copyright © 2026-present Aresys S.r.L. info@aresys.it
4 maintainers
Metadata
4 maintainers
Release files for perseo-perturbations 1.0.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 |
|---|---|---|---|---|
| perseo_perturbations-1.0.0.tar.gz | 805.3 kB | With provenance | Details for perseo_perturbations-1.0.0.tar.gz |
Built distributions (wheels)
Total release size: 17.0 MB
Release files / perseo_perturbations-1.0.0.tar.gz
| Download URL | perseo_perturbations-1.0.0.tar.gz |
|---|---|
| Size | 805.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a9a2488ebad7df83af8b6cc6828c1a4c7cd6893e51d9ab5e5cd128e15796d4a8
|
|
BLAKE2b-256 checksum How to use checksums |
cb2d3b8c1fbc7caddad83780f2c0d86e2c45fa9867018bdb53d55e879f74a717
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp314-cp314-win_amd64.whl
| Download URL | perseo_perturbations-1.0.0-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
19815998209e68270a1f28ec9ccabe32c324b9b2fd53e4fbfd6b46e5e8bd54bc
|
|
BLAKE2b-256 checksum How to use checksums |
b7609ac9025088182770a215e19c0f10ef4fbe9420ec3dd664d47dcb22b48df5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | perseo_perturbations-1.0.0-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
7d91ff4ba600f3622ce29de3970326224a36978c15f66c2925aea34a48409918
|
|
BLAKE2b-256 checksum How to use checksums |
8ea314e19147971566b27bb727dcd23ff408f167acc56abbc6c80acaad154000
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp313-cp313-win_amd64.whl
| Download URL | perseo_perturbations-1.0.0-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
bdbf70a4e81b25e00caa323542c752953a7560ea056f554b8ee5a0657ed61172
|
|
BLAKE2b-256 checksum How to use checksums |
dd6aacfe7c5df1a19df829fc2a7ff9c451a3b7b22a92048218c6c26549d66c53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | perseo_perturbations-1.0.0-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
024ff74fc3c0573c5583a1828396170eb2835b87e953f76fcdd37eed77468f55
|
|
BLAKE2b-256 checksum How to use checksums |
43822e9480cd3efecbf0abf9ac409ae36a8804911624883cf3f5041faf7a18e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp312-cp312-win_amd64.whl
| Download URL | perseo_perturbations-1.0.0-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
dea5cc67b3d0d90abc1620cb2c87dddd998353ed04610520695fe2d2bb3405d2
|
|
BLAKE2b-256 checksum How to use checksums |
178ecc8f39db22e3999ab092a58243811bfed2771b076722a05b363da74bf3e3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | perseo_perturbations-1.0.0-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
106a98088893c295b680e0fa27ed5e2f2d9d7c24733cbe9bd9b21870c8e259b9
|
|
BLAKE2b-256 checksum How to use checksums |
6ceca8073d1216600aad40c7ff8fb99cdeffa2bcfbf0edfb1b295a3cd8744adf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp311-cp311-win_amd64.whl
| Download URL | perseo_perturbations-1.0.0-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7c56f1096f44176d56e7538730b0b5597db627c9b2f037fe601ab0a2d75baa57
|
|
BLAKE2b-256 checksum How to use checksums |
7ad236202f8d48a57e98332e95bc3185c73ed3c06010a5b9909f3cf5ac1bedbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logRelease files / perseo_perturbations-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | perseo_perturbations-1.0.0-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.8 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
9774dab7b6c3b776a687e2db2a7b1a6445160546ff9f979d6e6c5aeeaad7e0dd
|
|
BLAKE2b-256 checksum How to use checksums |
6ad368c07c427024c86e174ab36b5fa774ac47303e7378a8fed7262a9b7faec5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logSecurity for perseo-perturbations 1.0.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.
Full provenance
All 9 files in this release have been uploaded with provenance metadata.
Attestation for perseo_perturbations-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 19, 2026.
Transparency logA 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.
