Independent by design · no pay-to-rank placements  · How we evaluate tools →
Anclum Submit
A

AlanBacker/audio-flyover-geolocation

Locate where a recording was made from the Doppler curves of aircraft in its background, matched against…

Before you install: no copy-paste command · license MIT · link reachable

First step: git clone https://github.com/AlanBacker/audio-flyover-geolocation

View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
Install & config
Install command from the repository
pip install numpy

Parsed from the README we fetched on 2026-11-03; we have not executed it.

This is the install method the repository states, not an MCP client config, so no JSON is generated.
Key names differ by client: Clients & CLI
Star count
38 ★ · AlanBacker/audio-flyover-geolocation · read from the GitHub search API · (checked 2026-11-13 20:00:50)
Source
read directly from its GitHub page · type: open-source project
Harvest history
first seen 2026-11-04 · last seen 2026-11-14 · seen 11× · listed by 1 sources
Score
score 103 · 38 ★ · 1 sources · repo
Install
pip install numpy
FAQ (answers come from our records)
How do I install it?
The repository provides this install command: pip install numpy. It comes from the repository itself; we cannot guarantee it runs as-is in your client.
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository AlanBacker/audio-flyover-geolocation;first catalogued 2026-11-04;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.

# Audio Fly-over Geolocation

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

English | 简体中文
An agent skill that works out where an audio or video recording was made from the faint propeller aircraft in
its background. It ships a complete, tested Python pipeline and comes in English and Simplified Chinese.
Small aircraft give off a steady tone. As one flies past, the Doppler effect bends that tone into a falling
curve, and the shape of the curve gives the aircraft's speed, its closest distance to the microphone and the
second it was closest. Public ADS-B archives record where every transponder-equipped aircraft was at every
second. If you search those tracks for the place where the predicted curve matches what was recorded, you find
the microphone. Two fly-overs in one recording are enough, even when the recording time is unknown, because
their time difference is fixed by the recording itself.
The method comes from colsto's video
I discovered a sound that leaks your exact location
(2026-11-02). colsto did not release code; this repository is an independent implementation with no affiliation.
Synthetic blind test (seed 23): each fly-over alone gives a strip of possible locations. Scored together on one
shared clock, they give a point 46 m from the true recording location, inside the 0.9-score region the pipeline
reports (radius 182 m).
## Contents
How it works
Accuracy on synthetic blind tests
Install
Use
Check your own videos
Limitations
Responsible use
Repository layout and development
Credits and sources
## How it works
mermaid
flowchart LR
A[Audio or video] --> B[Whitened spectrogram]
B --> C[Trace each Doppler ridge]
C --> D["Fit v, d, f0, tCPA k = v²/d"]
E[Historical ADS-B tracks] --> F
D --> F["Search funnel corridor → CPA match → ΔT → silence"]
F --> G["Exact emission-time scoring both events on one clock"]
G --> H["Location + error region + recording start time"]
1. Read the curve. The heard frequency is f = f0 / (1 + Ṙ/c), where Ṙ is the aircraft's range rate at
the moment the sound was emitted. The two flat ends of the curve give the speed
(v = c·(fhi − flo)/(fhi + flo)). The steepness at closest approach gives the distance
(d = f0·v²/(c·|slope|)).
2. Trace it out of the noise. The spectrogram is whitened against a running median background, and
frames with speech or knocks are gated out. A monotone Viterbi path is then accepted only if it beats a null
path computed on time-shuffled frames, so the tracer does not hallucinate curves in pure noise. When the flat
ends are faint, v and d trade off against each other, but k = v²/d stays well determined. The search
therefore checks every candidate aircraft against k computed from its own ADS-B ground speed.
3. Search the ADS-B archive. The search runs on a 200 m grid with 3D slant distances in ECEF and DEM
ground elevation, and narrows the candidates in stages:
1. corridors around tracks that fit the aircraft class and speed;
2. a closest-point-of-approach match that includes the sound's travel time;
3. the time offset between the two fly-overs;
4. a silence check: no other aircraft may have passed close while the recording was quiet.
4. Score against the exact physics. For each surviving candidate, the curve is predicted from the
aircraft's real track by emission time, and the spectrogram is sampled along it. Both events share one clock
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[![Listed on Anclum](https://anclum.com/badge/listed.svg)](https://anclum.com/en/s/alanbacker-audio-flyover-geolocation/)
Source
github · https://github.com/AlanBacker/audio-flyover-geolocation
Browse by field
Open source
Traction
38 ★
added
today

More like this

All 1,671 →

Filed under

Every tag opens the full list for that filter. Counts are the live catalogue figures.

Browse all fields →

← Back to index