Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

AirborneGeo

Tools for processing airborne geophysical survey data.

This package allows for a range of processing steps necessary for airborne geophysical data. Some of the functions are generic for many types of airborne surveys, such as splitting flights into segments, calculating quantities such as distance along lines, velocities, bearings, and cross-over errors, etc. However, there are many functions specifically focused on gravity and magnetic data. These include field reductions, 1D equivalent source inversion, and levelling of flight lines.

Levelling

We offer a range of ways to perform levelling of your flight line data.

Levelling to a grid

Supply a grid, for example satellite gravity data, and sample the grid values along each line. Then compare the grid values to the observed values to get a misfit at each point. Then level each line individually to minimize the misfit. This levelling can be a vertical shift (trend order 0), tilting the line (trend or 1), or fitting a higher-order trend to the misfit.

Levelling on cross-over errors

Instead of levelling your data to match a grid, if you have sets of orthogonal flight lines, you can calculated the cross-over errors and level lines to minimize them. This can be of any order, from a simple vertical shift to fitting a higher order trend to the misties.

Iterative levelling

If you have specific flight lines and tie lines, can also iteratively level the lines to the ties, and then the ties to the lines.

Weighted levelling

Instead of relying on all cross-over points to an equal amount, you can weight them individually. Calculated levelling correction values will depends strongly on cross-over points with high weights, and weakly on cross-over points with low weights. These weights can be decided based on a range of factors, such as distance to the nearest observation point, altitude difference between the crossing lines, the 1st or 2nd derivatives of either lines data or elevation, which might indicate the portion of the flight had turbulence.

Upward continued cross-overs

If your crossing lines have drastically different altitudes at a cross-over point, the mistie value may reflect that your observation of your field are at different points in 3D space (same horizontal coordinates but different elevations) and therefore you would expect them to have different values. To account for this, when calculating the cross-over misties, you can choose to do it at the same point in 3D space. We do this by fitting equivalent sources individually to each line (in 1D), and predicting the field values at the same point in 3D space. This is just to determine the mistie, but leaves the data at its original observation locations.

Actions Status Documentation Status

PyPI version Conda-Forge PyPI platforms Zenodo

GitHub Discussion

SPEC 0 — Minimum Supported Dependencies

Metadata

Release files for airbornegeo 0.0.1a1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for airbornegeo 0.0.1a1
File Size Uploaded
airbornegeo-0.0.1a1.tar.gz 42.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for airbornegeo 0.0.1a1
File Interpreter ABI Platform
airbornegeo-0.0.1a1-py3-none-any.whl Python 3 none any Details

Total release size: 88.0 kB

Release files / airbornegeo-0.0.1a1.tar.gz

Download URL airbornegeo-0.0.1a1.tar.gz
Size 42.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b4cb4205538e8d174c6f2412a5af81d75606ae1f03ca6103e4f7993be58c1ff3
BLAKE2b-256 checksum
How to use checksums
ba72bf050f275509e4ce5e69c50e7d750912e6e08d23fad600722398c98f6b92
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 24, 2026.

Transparency log

Release files / airbornegeo-0.0.1a1-py3-none-any.whl

Download URL airbornegeo-0.0.1a1-py3-none-any.whl
Size 45.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a9e020ad603339fc2dd68b1f1122466540ce5b41bea2191892cb612f9e105551
BLAKE2b-256 checksum
How to use checksums
79c6d68571f180bedc7e40b5725bdef7db60724ba47b494f76e52083e4dcc5ac
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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 Mar 24, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.1a1 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page