// An Omni Ledger Exclusive — Water Proximity Data

Water Proximity Analysis

How close is every case file on this site to the nearest ocean, sea, lake, or river? We computed the real, GIS-based answer for every case's own real incident site against actual survey data — not estimates — and built it to update automatically as new cases are added.

Data Analysis

Core Thesis

Loading live figures from the site's own geographic dataset…

Origin & History

This analysis started as an offhand observation while browsing The Omni Ledger's own interactive map: nearly every marker seemed to sit close to a coastline, a lake, or a river. The first pass at answering it honestly was a set of hand-estimated distances from general geographic knowledge — useful for a quick gut check, explicitly labeled as approximate, and genuinely informative about the shape of the question. But an estimate is not a metric, and a metric that gets tracked permanently on a site built around verified sourcing needed a real answer, not a guess.

So this page does not report estimates. It reports a real, computed geodesic distance from every case file and location's actual recorded coordinates to the nearest large body of water, measured against Natural Earth's 1:10,000,000-scale physical vector data — the same class of survey data used in professional cartography and GIS software, not a language model's geography knowledge. The underlying calculation is re-run automatically alongside this site's other post-publish data updates (map markers, correlation network, knowledge base) every time a location is added or edited — which is what makes this a genuinely living page rather than a one-time snapshot.

ⓘ Methodology: Real point-to-feature geodesic distance against Natural Earth 1:10m coastline, lake, and named-river survey data. No estimation, no sampling.
Locations Analyzed
Avg. Distance
Median Distance
Within 10 mi
Within 50 mi
Over 150 mi

Methodology

Every distance on this page is computed, not looked up or guessed. The pipeline works in three real steps:

  1. Real coordinates. Every case file and location card on this site already carries a verified latitude/longitude, the same coordinates that place its marker on the interactive map.
  2. Real water-body survey data. Three datasets from Natural Earth (1:10,000,000 scale, the standard free public-domain cartographic dataset used across professional GIS work) — a global coastline vector, a global lake-polygon set, and a global named-river centerline set — plus an ocean polygon layer used specifically to detect points that are already at sea (a ship, an intercepted aircraft) rather than measuring their distance to shore.
  3. Real geometry. For each location, the script computes the minimum distance to the nearest point on any coastline segment, any lake boundary (or 0 if the point falls inside one), and any named river centerline, then reports whichever is closest.

Known limitations, stated honestly: the underlying distance calculation uses a locally-flat equirectangular approximation rather than true ellipsoidal geodesics — accurate to a small fraction of a percent at the scale this page measures (a few to a few hundred miles), but not survey-grade precision. The river dataset includes named rivers at 1:10m resolution, which is a large, real, and far more complete set than smaller-scale alternatives, but it does not include every minor creek or seasonal stream — a location's true nearest trickle of water may occasionally be closer than what this page reports. Distances are measured to the water feature itself, not adjusted for whether a case's coordinates represent an exact site or a city-level approximation.

The Findings

Finding I

The Pattern Is Real, But Less Extreme Than It First Looked

Computing…

Finding II

Where the Outliers Actually Are

Computing…

Finding III

Rivers Do Most of the Work

Computing…

Reading This Honestly

Most human settlement, most military installations, and most infrastructure of every kind cluster near water for entirely mundane reasons — drinking water, transport, agriculture, cooling systems, historical settlement patterns. A finding that "most UFO cases are near water" is, on its own, close to "most places are near water." The more interesting question this page is built to keep tracking over time is whether case locations cluster near water at a rate meaningfully different from a random sample of comparable populated places — a comparison this page does not yet make, and flags honestly as the natural next step rather than papering over.

The Complete, Live Data Table

Every location this site tracks, sorted by real computed distance to its nearest large body of water. This table re-reads data/water_proximity.json directly — the same file the statistics above are drawn from — so it reflects the current state of the site's location data on every page load, not a fixed snapshot.

Location Case File Nearest Water Distance ↓
Loading live data…

Is This a Known Idea?

Not in any formal, peer-reviewed sense — there is no published academic literature specifically testing UAP-report proximity to water bodies that this research turned up, and this page does not claim to be summarizing one. What does exist is informal, contemporary, and worth citing honestly rather than either overstating or ignoring: crowd-sourced UAP-tracking platforms including Enigma Labs have separately logged and mapped clusters of reports along U.S. coastlines and near major waterways, part of the long-running "USO" (unidentified submerged object) thread in UFO research that traces back at least to Ivan Sanderson's mid-20th-century writing on oceanic anomaly zones. None of that constitutes rigorous evidence of a real correlation — it is informal pattern-noticing by other researchers and platforms, offered here as honest context for where this observation sits in the wider field, not as validation of it.

Conventional Explanation Candidates

Settlement & Population Density

Plausible

Humans settle near water for drinking, agriculture, trade, and transport. More people near water means more potential witnesses near water, independent of anything about the phenomenon itself. This is likely the single largest driver of the pattern.

Military & Infrastructure Siting

Plausible

Airbases, radar installations, and naval facilities are disproportionately sited on coastlines and major waterways for genuine logistical and strategic reasons — a real confound for any dataset skewed toward military-witnessed cases, independent of this site's own category breakdown (military/government-linked locations here actually average slightly farther from water than sighting-site locations, which cuts against this being the dominant driver).

Atmospheric Optics Near Large Water Bodies

Inconclusive

Large bodies of water can produce temperature inversions and unusual light refraction (a real, documented contributor to misidentified lights and mirage-like effects). This could inflate reports specifically near coastlines and large lakes without implying anything about smaller rivers, which this analysis treats as equally "close to water" — a real tension the current methodology doesn't resolve.

Genuine Phenomenon-Level Pattern

Inconclusive

The open, unproven possibility motivating this page in the first place. Nothing in this dataset rules it out, and nothing in it confirms it either — distinguishing this from the mundane explanations above requires the baseline comparison flagged in Finding I's callout, which has not yet been done.

Theoretical Alignment

This page does not argue for or against any theory of UAP origin — it tracks one geographic metric across the site's own data and reports it honestly, including the reasons it might mean nothing at all. Where it connects to other theory pages is as a background variable: if a genuine phenomenon-level water association exists, it would be most relevant to craft-propulsion and atmospheric-organism theory pages that already engage with performance characteristics observed in over-water cases; if it's fully explained by the mundane candidates above, it has no bearing on any of them.

Key Proponents

This is an original Omni Ledger data page, not a summary of an established theory — it has no formal academic proponents to cite, and this page does not invent any. The observation originates from a user of this site noticing the pattern while browsing the interactive map; the computation pipeline was then built to test it rigorously rather than take the first impression at face value. The closest real-world parallel is the informal, non-peer-reviewed pattern-tracking done by crowd-sourced platforms like Enigma Labs, described honestly above.

Related Cases

Sources

This is a computed data page, not a narrative case file — its numeric findings come from the real survey datasets named throughout the text above, not from secondary reporting. The list below cites those datasets formally, plus the real, independently-published sources behind the specific historical and platform claims made in the "Is This a Known Idea?" section.

  • Natural Earth. 1:10m Physical Vectors — Coastline. Free vector and raster map data at 1:10m scale. naturalearthdata.com
  • Natural Earth. 1:10m Physical Vectors — Lakes & Reservoirs. naturalearthdata.com
  • Natural Earth. 1:10m Physical Vectors — Rivers & Lake Centerlines. naturalearthdata.com
  • Natural Earth. 1:10m Physical Vectors — Ocean. naturalearthdata.com
  • U.S. Geological Survey (USGS). National Hydrography Dataset (NHD) — the government hydrography survey referenced throughout the Methodology section. usgs.gov
  • Enigma Labs. UAP Sighting Map & Database — the crowd-sourced platform cited in "Is This a Known Idea?" for its own informal coastal/waterway report-clustering observations. enigmalabs.io
  • Sanderson, Ivan T. Investigating the Unexplained: Disquieting Mysteries of the Natural World. Englewood Cliffs, NJ: Prentice-Hall, 1972. archive.org
  • Sanderson, Ivan T. "The Twelve Devil's Graveyards Around the World." Saga magazine, 1972 — the origin of Sanderson's oceanic "anomaly zone" concept referenced in the Context section. archive.org
  • The Omni Ledger. Case Files Index — the live case list whose real incident coordinates populate this page's dataset. /case-files/
  • The Omni Ledger. Locations Archive — the registered location records with the real coordinates this analysis measures against. /locations/
  • The Omni Ledger. Interactive UAP Map — the map project whose markers first surfaced the pattern this page was built to test, per Origin & History. /map/
  • The Omni Ledger. data/water_proximity.json — the live, generated dataset this page renders in full, built by scripts/build_water_proximity.js against the Natural Earth and USGS survey data cited above. /data/water_proximity.json
  • The Omni Ledger. Pascagoula Abduction case file, one of the on-the-water cases in Related Cases above. /case-files/pascagoula-abduction.html
  • The Omni Ledger. Falcon Lake Incident case file. /case-files/falcon-lake.html
  • The Omni Ledger. Kinross Incident case file. /case-files/kinross-incident-1953.html
  • The Omni Ledger. Frederick Valentich Disappearance case file. /case-files/frederick-valentich.html
  • The Omni Ledger. Extraterrestrial Hypothesis theory page, cross-linked under Theoretical Alignment above. /theories/extraterrestrial-hypothesis/
  • The Omni Ledger. Seasonal Sightings Analysis ("The July Phenomenon") — the sibling data exclusive linked in the sidebar. /theories/seasonal-sightings-analysis/
View the USGS National Hydrography Dataset (real government water-survey data) →

Have corrections, additional research, or peer-reviewed sources? Help improve this entry.

Suggest an Edit