Methodology & Astronomical Engine

How the simulator
works under the hood.

Choose the 2026 total, 2027 total, or 2028 annular eclipse, then compare a real observing point using local contacts, terrain, nearby buildings, weather data, and an interactive timeline.

01

Eclipse Astronomy Engine

The selected event and observer coordinates are evaluated with NASA/GSFC Besselian elements. The planner calculates C1–C4, local total/annular/partial status, maximum obscuration, solar altitude and azimuth, and central-phase timing.

02

Global DEM Horizon Model

The terrain service samples Mapzen Global Terrain Terrarium tiles from AWS Open Data across a 400 km profile. A denser, higher-resolution ray follows the Sun’s exact azimuth; the view span is bounded and reported in the planner. This is planning-grade terrain, not a land survey, and the UI says when reliable terrain is unavailable.

03

Terrain, Solar Ray, and Buildings

The planner compares the solar line of sight with terrain and then checks nearby Overture building footprints separately, using measured or floor-derived heights where available and conservative estimates otherwise. Trees, temporary structures, and unusual atmospheric refraction are not modelled.

04

A Decision Readout, Not a Score

The current planner reports the selected event, contacts, obscuration, Sun position, terrain horizon, solar obstruction, building status, and data provenance. It deliberately does not turn uncertain inputs into a single 0–100 promise.

05

Interactive Sky and Timeline

The map, sky view, horizon profile, and C1–C4 timeline use the same selected event and location. Scrub or play the event to see the Sun move relative to the sampled horizon and inspect the exact readouts at each phase.

06

Optional Street View Context

When Google Maps Street View is configured and coverage exists, the immersive panel can show the real scene with the eclipse trajectory overlaid. If the panorama cannot load, the planner keeps the exact Google Maps location link and reports the limitation.

From Map to Street View

Three views for
better decisions.

Start with the event path on the map, inspect the exact-coordinate horizon and solar ray, then use the optional Street View context when it is available. The map, horizon, and timeline are driven by the same selected event and observer location.

Macro Heatmap

Compare event paths, map coverage, and named viewing points at a glance.

Micro Horizon Profile

Inspect terrain source, sampling range, solar-ray result, building status, and stated limitations.

Live Street View

Frame the real scene when Google coverage and the configured Maps key allow it; otherwise use the external location link.

SIMULATOR DUAL VIEW
VISIBILITY MAP
42° 36' N · 4° 12' W
DEM TERRAIN LINE-OF-SIGHT
Spot Selection & Field Prep

Test any observer spot in detail

Choose a preset, a bundled public viewing point, or—when Pro is active—an exact searched or map-selected coordinate. Then inspect contacts, terrain, nearby buildings, and the weather state for the selected eclipse date.

  • Three supported events: 2026 total, 2027 total, and 2028 annular
  • Fifty official 2026 Castilla y León points plus exact-coordinate planning tools
  • Forecast when available; historical averages and unavailable data are labelled clearly
Open Simulator
Current Planner Readouts

What the planner reports

These are separate, inspectable signals rather than a synthetic certainty score. Check the provenance and limitations before making a travel decision.

Event Geometry

Shows the selected event type, local C1–C4 contacts, maximum obscuration, central phase, solar altitude, and azimuth.

Terrain Line of Sight

Uses a broad terrain profile and a denser ray toward the Sun to show whether sampled relief may affect the view.

Buildings and Limits

Checks nearby Overture building footprints when data loads, distinguishes measured and estimated heights, and keeps unknowns visible.

Weather and Provenance

Shows an Open-Meteo forecast when available, otherwise a clearly labelled historical average or unavailable state, alongside model details.

Sources & Data Standards

Eclipse circumstances use NASA/GSFC Besselian elements. Terrain elevations come from Mapzen Global Terrain Terrarium tiles hosted as AWS Open Data; source resolution and vertical datum vary by region. Nearby building checks use the versioned Overture Maps Buildings release and may use conservative estimates. Weather uses Open-Meteo forecast or archive data. Street View depends on Google coverage and configuration. The model includes Earth curvature, a standard 0.13 terrestrial-refraction coefficient, and a 1.7 m eye height; it does not include trees, temporary structures, snow depth, or unusual atmospheric refraction. Verify marginal views on site.

The sky won't wait.
Make your plan.

Select an event and location, inspect every readout, and share a secure exact-location link when Pro allows it. SunEclipses is a planning tool, not a land survey: verify marginal sightlines, current weather, road access, and local safety rules before travelling.