Every number in Four Lights starts as open NASA data.

This page lists each dataset: what it is, who made it, what the app uses it for, what we did to it, how we checked it, and how to cite it. Nothing in the app is simulated or invented. Where a figure is our own definition or an illustrative value, the app says so beside it.

At a glance

Dataset From Used for Where you see it
LOLA elevation models NASA Goddard, PDS The terrain horizon at every site The skyline in the Sun-Path Chart; every light; the map's polar shading
LRO WAC imagery and LOLA colour-shaded elevation NASA, via Moon Trek The picture of the Moon in the 3D map The Map tab's Imagery and Elevation layers
JPL Horizons NASA JPL Where the Sun and Earth are, each hour The gold and blue tracks; every light
NAIF SPICE kernels NASA JPL An independent check; Deep Space Network station positions The Comms light's station ("link via Canberra")
Artemis candidate regions USGS, for NASA The centres of six of the twelve sites The site list and the map
NASA Image Library NASA Nine pictures Beside the power systems in Survive the Night; in the guide panel

LOLA elevation models of the south pole

NASA Lunar Reconnaissance Orbiter, Lunar Orbiter Laser Altimeter (LOLA). NASA Goddard Planetary Geodesy Data Archive and the Planetary Data System.

What it is
The shape of the Moon's surface, measured by timing laser pulses from orbit since 2009. We use six elevation models, from 5 m per pixel at the sites to 240 m per pixel across the whole polar region.
Products used
Six 5 m site models (PGDA product 78: Sites 01, 04, 07, 11, 20 and 23); the 87°S 5 m mosaic (PGDA product 81); and the polar gridded models LDEM_875S_20M, LDEM_85S_20M, LDEM_75S_60M and LDEM_75S_240M (PDS). About 5 GB in all.
What the app uses it for
The skyline. For each site we find the highest ground in each of 720 half-degree directions, using the finest model that covers each point: 5 m terrain near the site, then 20 m to 60 km, 60 m to 150 km, and 240 m out to about 650 km. That skyline decides every Sun, Earth, Power and Comms light. The map's shading is also made from LDEM_75S_240M.
What we did to it
Converted every pixel to a 3D position on the Moon's 1737.4 km sphere and measured its direction and height from the site in a local east-north-up frame, so that "north" is true north and the Moon's curvature is exact. Within about 400 m of the site the terrain is resampled to 0.5 m so nearby ground is not missed.
How we checked it
A second calculation written with different mathematics gives identical horizons on eight directions across all six models. Where neighbouring models overlap near Shackleton rim, their heights agree to a median of 0.06 m or better. GRASS GIS finds the same peaks within about 0.1°. Tests with known answers cover true north at the pole, the horizon of a bare sphere, a single-pixel spike, and a smooth dome.
Limits
About 90% of 5 m pixels are interpolated between laser tracks. Three sites (Nobile Rim 1, Nobile Rim 2 and Peak near Cabeus B) have no 5 m terrain beneath them and are marked approximate.
Licence
NASA open data.
Cite as
Barker, M. K., et al. (2021), Improved LOLA elevation maps for south pole landing sites, Planetary and Space Science 203, 105119. Site numbering from Mazarico, E., et al. (2011), Icarus 211, 1066–1081. LOLA PDS archive (Smith et al.).
Links
5 m site models · 87°S mosaic · polar gridded models · about the mission

LRO WAC imagery and LOLA colour-shaded elevation (NASA Moon Trek)

NASA Lunar Reconnaissance Orbiter: the Wide Angle Camera mosaic (NASA/GSFC/Arizona State University) and the Lunar Orbiter Laser Altimeter colour-shaded elevation (NASA/GSFC/MIT), published as map tiles by NASA Moon Trek.

What the app uses it for
The 3D Moon in the Map tab: Imagery (WAC), layer LRO_WAC_Mosaic_Global_303ppd_v02 (zoom 0 to 8), and Elevation (LOLA), layer LRO_LOLA_ClrShade_Global_128ppd_v04 (zoom 0 to 5). Pictures only: no light, threshold or horizon in the app is computed from them.
What we did to it
Nothing to the pixels. The browser asks our own server for the tiles in view; our server fetches each from Moon Trek once, keeps it in a cache and passes it on. The tiles are draped on a sphere without reprojecting them.
Limits
The tiles are an equirectangular grid, so they are stretched and streaky within a few degrees of the pole, where all twelve sites are. For that reason the Map tab also has Polar shading, our own hillshade from LOLA (see above), and shows it when you fly to a site. The elevation colours are NASA's own scale.
Licence
NASA imagery and data, open; credit NASA/GSFC/ASU (WAC) and NASA/GSFC/MIT (LOLA).
Link
trek.nasa.gov/moon

JPL Horizons ephemerides

NASA Jet Propulsion Laboratory, Solar System Dynamics.

What it is
NASA's service for the positions of Solar System bodies, as seen from any observer, including a point on the Moon's surface.
What the app uses it for
The direction of the Sun and of Earth from each site (azimuth and elevation of the body's centre) for every hour of 2028 and 2029: 17,544 steps per site. These are the gold and blue tracks in the Sun-Path Chart, and half of every light.
What we did to it
One request per site and body, with the observer placed at the site's longitude, latitude and height on the 1737.4 km sphere (ephemeris DE441, the Moon's mean-Earth frame, the same frame family as the terrain). Also pulled: 2024 to 2026 for Connecting Ridge, to compare with published results.
How we checked it
The same directions computed with NAIF SPICE agree to about a millionth of a degree. Earth's average direction at every site matches that site's longitude to within 0.2°, which would catch north and south being swapped.
Limits
Positions are for the centre of each body. The app treats the Sun as a 0.53° disc using the terrain height at the Sun's direction; Earth is taken at its centre.
Licence
NASA open data.
Cite as
JPL Horizons On-Line Ephemeris System, NASA/JPL Solar System Dynamics.
Link
ssd.jpl.nasa.gov/horizons

NAIF SPICE kernels

NASA JPL, Navigation and Ancillary Information Facility.

What it is
The data files that space missions use for geometry: the planetary ephemeris DE440s, the Moon's orientation and reference frames, Earth's orientation, and the surveyed positions of the Deep Space Network antennas.
What the app uses it for
Two things. An independent check on Horizons for every site. And Canberra Link: the Moon's elevation from the 70 m antennas at Goldstone (DSS-14), Canberra (DSS-43) and Madrid (DSS-63) for every hour, so the Comms light can require a station with the Moon at least 10° up, and name it.
How we checked it
The Moon's elevation from all three stations matches JPL Horizons to better than 0.001°. At least one station qualifies 98.6% of the time, with gaps of an hour at most.
Limits
The Moon's centre stands in for the landing site (at most 0.26° apart from Earth). The 10° limit is the network's transmit limit from its handbook; real passes also depend on scheduling, which we do not model. Earth orientation for 2028 and 2029 is NAIF's long-term prediction.
Licence
NASA open data.
Cite as
Acton, C. H. (1996), Ancillary data services of NASA's Navigation and Ancillary Information Facility, Planetary and Space Science 44, 65–70. Elevation limits: DSN Telecommunications Link Design Handbook 810-005, module 301.
Links
NAIF · the Deep Space Network · handbook module 301

Artemis candidate landing regions

USGS Astrogeology Science Center, for NASA.

What it is
Navigational grids (the Lunar Grid Reference System) for the candidate landing regions NASA named near the south pole in October 2024.
What the app uses it for
The centres of six of the twelve sites: de Gerlache Rim 2, Haworth, Nobile Rim 1, Nobile Rim 2, Peak near Cabeus B and Slater Plain. Two more regions, Malapert Massif and Mons Mouton, coincide with NASA Goddard's 5 m site models. The other four sites come from those site models.
What we did to it
Took the centre of each region's 1 km grid and converted it from the grid's own map projection to ours. Each region is about 20 km across, so the site is then placed on the highest summit within 8 km of that centre, where a summit is a point with nothing higher within 1 km.
Limits
A region is not a landing point. Our site within it is a reasonable high point, not where a mission would necessarily land. One region, Mons Mouton Plateau, is left out because its file was not openly downloadable.
Licence
US Government public domain.
Cite as
USGS Astrogeology (2024), Lunar Grid Reference System navigational grids for the Artemis III candidate landing regions, doi:10.5066/P1MEQ6UK.
Link
doi.org/10.5066/P1MEQ6UK

NASA Image and Video Library

NASA.

What the app uses it for
Three photographs, shown beside the power systems in Survive the Night as examples of each class of vehicle: Surveyor 3 on the Moon (AS12-48-7121, 1969), a prototype of the VIPER polar rover (GRC-2021-C-00493, NASA/GRC/Bridget Caswell, 2021) and the Apollo 11 lunar module (AS11-40-5927, 1969). And six in the guide panel: the south polar region from above (Clementine mosaic PIA00001, NASA/JPL/USGS), Earth over the lunar horizon from Apollo 8 (AS08-14-2383, 1968), Deep Space Station 43 near Canberra (PIA23797, NASA/JPL-Caltech), the south pole from the Lunar Reconnaissance Orbiter's Wide Angle Camera (PIA13523, NASA/GSFC/Arizona State University), an artist's rendering of the orbiter (PIA18163, NASA/GSFC) and Alan Bean fuelling Apollo 12's nuclear generator (AS12-46-6790, 1969).
Limits
Illustration only. The power figures beside them are round illustrative values of our own, not those vehicles' specifications.
Licence
NASA imagery, public domain; credit NASA.
Link
images.nasa.gov

What we compare our results against

Published NASA results we did not use as inputs, only as a check on our own numbers.

Barker et al. (2021)
NASA Goddard's illumination study of the same 5 m sites. For Connecting Ridge, 2024 to 2026, our longest night falls within their published range at 1 m and at 5 m above the ground. Our average illumination is a few points higher than theirs, which is the expected direction: they report a deliberately cautious figure, and at 1 m the result varies by 9 points between spots 20 m apart. We do not claim the illumination matches. doi:10.1016/j.pss.2020.105119
Mazarico et al. (2011)
The earlier LOLA illumination study that the site numbering comes from. doi:10.1016/j.icarus.2010.10.030

What we computed, and what is our own choice

Computed from the data above
Each site's skyline at observer heights of 1, 2 and 5 m; whether the Sun and Earth clear it each hour; the share of the Sun's disc in view; which Deep Space Network station can see the Moon.
Our own definitions
Power (the Sun in view at least 70% of the mission window on average, and never fully hidden for more than 48 hours), the 1° margin for Comms, usable days, and the green, amber and red rules in the planner. These are planning aids of ours, not NASA requirements.
Illustrative values
The three power systems in Survive the Night: round numbers, not real vehicles.
Written by an AI model
Only the short "site review" paragraph for each site, from our computed figures, with every number checked; and the translation of a typed question into planner settings. No AI model computes any result.
Not used
No simulated, synthetic or generated data, images, video or audio.

Open-source software in the app

Not data, but other people's work that the pages you see are built with.

three.js
Draws the 3D Moon in the Map tab. MIT licence. threejs.org
Phosphor Icons
The icons on the lights, buttons and tabs. MIT licence. phosphoricons.com
IBM Plex Sans and IBM Plex Mono
The typefaces, served by Google Fonts. SIL Open Font License 1.1. ibm.com/plex
Hono
The web framework inside the Worker. MIT licence. hono.dev
Mermaid
Draws the diagrams on How we built it. MIT licence. mermaid.js.org

The tools that made the data (Python, GDAL, QGIS and others) are listed on How we built it.

Download our data

The files the app runs on are open, under CC BY 4.0. NASA's source data stays NASA's. Angles are in degrees, azimuth clockwise from true north at the site, times in UTC.

The code that turns NASA's files into these, and the steps to rerun it, are in the project's repository.