Primary sources and related tools#
These sources document upstream data or implementation primitives. They do not endorse LunarTrace, establish the correctness of every R2 implementation detail, or replace exact source receipts.
NASA/PDS Lunar ODE#
ODE supplies planetary product discovery and associated source metadata. LunarTrace’s initial profile is restricted to Moon/LRO/LROC/CDRNAC4. The server’s exact request and returned bytes are retained where the Lab capture supports them; a citation to an API manual is not a substitute for a particular query receipt.
Lunar contextual imagery#
The R2 baseline uses the retained CGI Moon Kit texture as visualization context. NASA explicitly describes the texture as optimized for aesthetics rather than scientific use. The existence of higher-resolution map products or tile services does not mean they have been incorporated or spatially qualified in this release.
Browser rendering#
The authored R2 adapter uses the version-pinned 1.145 browser build and a lunar sphere. Rendering APIs are presentation mechanisms; they do not establish the scientific basis of a displayed coordinate or image relationship.
Documentation system#
Sphinx provides the scientific/manual surface and API reference. The manual should remain linked to actual source interfaces and independently qualified build output.
Methods and implementation provenance#
The exact current partition, metric, and screening definitions are documented in Event-conditioned comparison methodology and implemented in the Python source. The historical Chang’e 6 quantities derive from the repository’s retained, hash-locked historical basis—not from a new empirical result asserted by this manual.
For work requiring calibrated planetary geometry, registration, photometry, or scientific change analysis, interoperate with appropriate specialist tools and source products. LunarTrace does not claim to replace the entire planetary-science software ecosystem.