The NASA Planetary Data System (PDS) is NASA’s official long-term archive for digital science data from planetary missions, ground-based telescope campaigns, and laboratory experiments related to Solar System science. Unlike a generalist repository, PDS is a domain repository (also called a discipline-specific repository): every dataset it accepts is peer-reviewed by planetary scientists for completeness and usability before it is archived, and access to both data and tools is free. For research administrators and data stewards supporting planetary science investigators, PDS is the mandatory deposit point for NASA-funded mission data and a useful reference case for how a mature, federated domain archive operationalizes FAIR data practice at scale.
What the Planetary Data System Covers
PDS holds imaging, spectral, radar, plasma, ring, atmospheric, geologic, and navigation data returned by NASA planetary missions across the Solar System, along with supporting ground-based and laboratory datasets used to calibrate or interpret mission results. It was established by NASA in 1989, following recommendations from the Committee on Data Management and Computation (CODMAC), convened by the National Academy of Sciences in 1982 to address how the agency should manage the growing volume of data returned by planetary missions. PDS predates, and is organizationally distinct from, discipline archives that cover other parts of NASA’s astrophysics and heliophysics portfolio, such as the NASA Exoplanet Archive (confirmed and candidate exoplanet data) or MAST (general astrophysics mission data) — a distinction covered in more detail below.
The Federated Node Structure
PDS is not a single centralized database. It operates as a federation of discipline-specific nodes, each hosted by a different institution and staffed by scientists with domain expertise in that data type. As listed on pds.nasa.gov, the current discipline nodes are:
- Atmospheres (ATM) — atmospheric science data from planetary and satellite atmospheres
- Cartography and Imaging Sciences (IMG) — imaging and cartographic products
- Geosciences (GEO) — surface and interior geologic/geophysical data
- Navigation and Ancillary Information Facility (NAIF) — spacecraft position, pointing, and timing (SPICE) data
- Planetary Plasma Interactions (PPI) — space plasma and fields data
- Ring-Moon Systems (RMS) — planetary ring and small-satellite data
- Small Bodies (SBN) — asteroid, comet, and other small-body data
This federated model means a researcher’s first stop depends on data type as much as mission: imaging data from a Mars mission and spacecraft navigation data from the same mission may be archived and curated by two different nodes. A central PDS search and catalog layer sits above the nodes so researchers do not need to know the node structure in advance to find data, but understanding it helps when a dataset’s documentation, calibration notes, or long-term point of contact are node-specific.
PDS4: The Data Standard Behind the Archive
Data submitted to PDS must conform to a formal archiving standard so that products remain interpretable independent of the software that produced them. The current standard, PDS4, has been required for data from NASA-funded planetary missions and research activities since 2011, following a multi-year redesign effort that began around 2010 — described by the PDS program itself as the largest standards and software overhaul in the system’s history. PDS4 replaced the earlier PDS3 standard’s flat, largely ASCII-label approach with an XML-based label format built on a formal information model, allowing labels to be validated programmatically and enabling more granular metadata than PDS3’s fixed structure supported. PDS4 governance and format development involves the international coordination of the International Planetary Data Alliance (IPDA), and the standard is updated on a roughly six-month release cadence. Missions still governed by legacy holdings (data delivered before the PDS4 transition) remain documented under PDS3; PDS’s own data-standards documentation directs users working on older projects to the separate PDS3 standards rather than treating PDS4 as universally retroactive.
For a research data steward, the practical takeaway is the same one that applies to any domain repository with its own submission standard: a mission or investigator team planning to deposit with PDS needs to build PDS4-compliant labels and bundle structures into their data management plan well before end-of-mission delivery, not retrofit them afterward.
How Researchers Discover and Access PDS Data
PDS provides a central data search interface and per-node catalogs organized by planetary discipline, letting researchers search across missions, instruments, targets, and data types rather than needing to know in advance which node holds a given dataset. Because PDS is organized around discipline and mission rather than a single flat catalog, cross-node and cross-mission searches (for example, comparing spectral and imaging data for the same target body) typically mean consulting more than one node’s tools, which is a genuine usability trade-off of the federated model compared with a single generalist repository — though it is also what allows each node to maintain deeper, discipline-specific curation than a generalist archive typically provides.
All PDS holdings are freely accessible with no cost for data or the tools used to browse and download it, consistent with the open-access norms most NASA data policies now require.
Citing PDS Data
Because PDS4 bundles and collections include structured citation metadata as part of the label itself (author, date, title, and related identifying information at the bundle or collection level), datasets can be cited with the same rigor as a journal article rather than as an undifferentiated “NASA data” reference. PDS publishes its own citation guidance (“Citing PDS4 Data”) describing the expected format; researchers and data stewards writing a data management plan that names PDS as the deposit repository should follow that guidance directly rather than inventing an ad hoc citation format, and should treat the bundle or collection (not the individual product file) as the usual citable unit, mirroring the general practice covered in CASRAI’s guide to citing research data and the Joint Declaration of Data Citation Principles.
PDS and FAIR / Open-Science Compliance
PDS is a useful worked example of the FAIR Data Principles (Findable, Accessible, Interoperable, Reusable) in a mature domain-archive context:
- Findable — a central search layer plus discipline-node catalogs, with persistent, structured metadata attached to every bundle.
- Accessible — free, unrestricted access to data and tools, with no registration paywall.
- Interoperable — the PDS4 standard’s XML labels and formal information model are designed to be machine-readable and validated against a shared schema, not just human-readable documentation.
- Reusable — mandatory peer review before archiving, structured citation metadata, and long-term institutional stewardship (rather than a single grant-funded project) support reuse well beyond the original mission team.
For institutions writing funder-mandated data management plans that involve planetary mission data, naming PDS as the repository of record generally satisfies both NASA’s own data policy expectations and the broader FAIR-compliance language increasingly required by funders and journals — a pattern also true of the other domain repositories in CASRAI’s coverage of how to choose an open data repository.
How PDS Relates to Other NASA and Domain-Science Repositories
PDS is one of several domain-specific NASA archives, each scoped to a different part of the agency’s science portfolio. It is worth distinguishing PDS from:
- The NASA Exoplanet Archive, which curates confirmed and candidate exoplanet parameters and host-star data rather than raw planetary-mission instrument data, and which itself points to MAST or PDS for the underlying raw observations behind its compiled tables.
- MAST (the Mikulski Archive for Space Telescopes), which archives general astrophysics mission data (space telescopes) rather than Solar System planetary-mission data.
- Earth-observation domain repositories such as NOAA’s archives, which are scoped to Earth’s atmosphere, oceans, and climate rather than other Solar System bodies, even though the underlying stewardship and FAIR-compliance logic is similar.
For a research administrator supporting a multi-instrument planetary mission, it is common for different data products from the same mission to ultimately be deposited across more than one of these systems depending on data type — another reason to plan repository selection, by data type, early in the project’s data management plan rather than at the point of delivery.
Frequently Asked Questions
Is NASA Planetary Data System data free to access?
Yes. PDS provides free access to its archived data and to the tools used to search, browse, and download it; there is no subscription, paywall, or registration fee.
What is the difference between PDS3 and PDS4?
PDS3 used a largely flat, ASCII-based label format. PDS4, required for NASA-funded planetary missions and research since 2011, replaced this with an XML-based label format built on a formal information model, enabling machine-validated, more granular metadata. Legacy holdings delivered before the PDS4 transition remain documented under the PDS3 standard rather than being retroactively converted.
Do I need to use a specific PDS node, or can I search across all of them?
PDS provides a central search interface that spans the federation, so a first-time user does not need to know the node structure to start searching. Understanding which discipline node curates a given data type still helps for documentation, calibration notes, and long-term point-of-contact questions.
How do I cite a PDS dataset?
Cite the bundle or collection (not an individual file) using the citation metadata included in its PDS4 label, following PDS’s own published “Citing PDS4 Data” guidance rather than an ad hoc format. See CASRAI’s guide to citing research data for the general data-citation principles this follows.
Is PDS the right repository for all NASA planetary mission data?
It is the required deposit point for NASA-funded planetary science mission and research data, but related data types from the same mission (compiled exoplanet parameters, general astrophysics observations, Earth-observation data) may belong in a different domain repository, such as the NASA Exoplanet Archive or MAST. Confirm repository scope against the specific mission’s data management plan and NASA’s data policy requirements.
