henge

Geometry and alignments

Surveyed geometry — Established

The figures the app computes with, as encoded in HengeGeometry/Monument.swift (Cleal et al. 1995; Petrie’s and later surveys):

Feature Figure
Monument axis azimuth 49.9° (NE, to the midsummer sunrise quarter)
Sarsen circle 33.0 m diameter, 30 uprights
Aubrey ring 87.0 m diameter, 56 holes
Enclosure earthwork ~110 m across (ditch centreline)
Heel Stone 77 m out along the axis, 4.7 m tall
Avenue 22 m wide, straight for ~500 m before turning
Station Stones four, on the Aubrey circle, forming a rectangle

The stonehengeology.com constructions — Speculative

Source: stonehengeology.com/stonehenge-geometry (fetched 2026-07-31, at the owner’s direction). One author’s geometric reconstruction in the tradition of Alexander Thom’s “Megalithic Yard” (MY); enthusiast work citing real surveys (John Wood 1740, Petrie 1880, Gowland 1901, Hawley and Atkinson) but presenting derived constructions as demonstrated fact, without peer review. Every claim below is Speculative and must be badged wherever the app shows it.

Claims, as made:

What survives contact with the established register: the axis azimuth (50° against the surveyed 49.9°), the stone count, the 56, and the station rectangle’s lunar bearing — all of which the app already carries from better sources. The Megalithic Yard itself is rejected by mainstream archaeometry (Thom’s unit does not survive statistical re-analysis); the ovals and triangle constructions are the author’s own.

In the app: the geometry overlay draws the established table above with labels and ground-mapped measurements; the speculative constructions, if shown, ride the same hypothesis badging as the Hoyle markers.

The lunar hypotheses — Debated

See research/lunar-markers.md: Hawkins (1963/1965) and Hoyle (1966) on the Aubrey ring as an eclipse predictor. The app’s gold-marker mode acts out Hoyle’s machine and says so on screen, every time, with the honest scorecard (42 caught, 0 missed, 9 false alarms over a test decade). Hawkins’s specific mechanics still need primary-source pinning before any in-app prose uses them.