Moon data, free to reuse

For journalists, researchers, and educators

Reproduce these figures, maps and screenshots freely, including commercially, with the credit "azmth.space" linked where possible. No permission needed. The underlying coordinates come from NASA, LROC and NSSDCA sources cited row by row; credit them too where you lean on a specific position. Everything is provided as-is, and the limitations below are worth two minutes of your time before you plot anything.

Endpoints

All endpoints allow cross-origin requests. In Google Sheets: =IMPORTDATA("https://azmth.space/data/moon-sites.csv"). From a terminal: curl https://azmth.space/data/moon-sites.json.

Columns

• slug: Stable identifier, also the URL path segment on azmth.space
• name: Mission or object name
• operator: Agency or company, as the catalog records it
• nation: Country grouping: United States, Soviet Union, China, India, Japan, Israel, Russia, South Korea, Europe (ESA), or Multinational
• type: flyby, impactor, orbiter, soft-lander, rover, sample-return, relay, crewed-flyby, crewed-orbiter, crewed-landing, program, or debris
• outcome: success, partial, failure, operating, in-development, planned, cancelled, or debris. "debris" sits outside the success scale: a discarded rocket stage is not a mission that went well or badly
• year: Identifying year: landing or impact year for arrivals, target year for future missions
• latitude: Selenographic latitude in degrees, positive north, -90 to 90
• longitude: Selenographic longitude in degrees, positive east, -180 to 180
• site_name: Named location or a note on the coordinate, including whether it is approximate or predicted
• arrived: true if hardware actually reached this point; false for announced future landing targets
• coordinate_source: URL of the source the coordinate came from, where one is recorded
• url: The mission page on azmth.space, with full sourcing

Limitations

• Coordinates are as published by the cited source, usually a NASA/LROC or NSSDCA solution. Precision varies by decades: an Apollo site is known to metres, an early Soviet impact to tens of kilometres.
• Where a position is approximate or predicted rather than measured, site_name says so. Read it before plotting.
• One catalog entry can cover several vehicles (a lander and its rover share a site).
• This is a curated landmark catalog, not a complete inventory of every object on the Moon. Deliberately impacted Apollo rocket stages and spent lunar orbiters are not all individually listed.

Why precision varies so much

An Apollo landing site is known to within metres, because the descent stages are still there and the Lunar Reconnaissance Orbiter has photographed them. A 1960s Soviet crash site can be uncertain by tens of kilometres, because the only record is a position the USSR announced at the time and later analyses disagree. One entry here is a predicted impact point rather than an observed one: the Falcon 9 upper stage that hit in August 2026 has no published measured position at all. The site_name field says which is which, in plain words, on every row where it matters. Do not average these together without reading it.

Stability promise

Fields and CSV columns are additive-only: names and meanings never change. Slugs are stable identifiers and double as URL paths. If a breaking change ever becomes unavoidable, the old shape keeps working for 12 months and this page documents the change with a date. Methodology changes bump methodology_version in the metadata sidecar. Coordinates get corrected when better sources appear, which is the point of publishing the source URL beside each one.