NASA Open Data Portal

One agency, thirty-six thousand catalog cards. NASA Open Data Portal is NASA's central catalog of its own published data, run by the OCIO Information, Data & Analytics Services program under the OPEN Government Data Act, and it indexes 36,250 dataset records as of August 2026. Every division and center publishes into it: asteroid studies from the small-bodies teams, satellite imagery archives from the earth-observation programs, aeronautics research series, mission operations tables and technology transfer listings, all sitting behind a single search box.

The structural fact that matters most: this is a discovery layer, not a file server. Most entries are metadata cards that point at the authoritative archive doing the actual hosting - the Planetary Data System for planetary science, EOSDIS Earthdata for earth observation, the Technical Reports Server for documents. That division of labor means the catalog's real product is uniform description: one field skeleton applied identically across six subject bands, which is what lets a harvester sweep all 36,250 records without writing six adapters.

Get a sample of this dataset to see the full field dictionary and the live rows behind it before you commit.

Two records captured verbatim during verification, exactly as the catalog describes them:

| TITLE                | SLUG                    | LICENSE TITLE     | CREATED    | RESOURCES |
|----------------------|-------------------------|-------------------|------------|-----------|
| ASTEROID DENSITIES   | asteroid-densities-021a7| US general public catalog  | 2025-03-31 | 0         |
| ASTEROID OCCULTATIONS| asteroid-occultations   | US general public catalog  | 2025-03-31 | (none)    |

Those two rows quietly make the whole argument. Both are US general public catalog, both carry recent creation timestamps, and both list zero attached resources - they are pure catalog cards pointing at the small-bodies archive that holds the actual tables. A zero in the resources column is not a defect; it is the catalog telling you where the hand-off happens. Every row ships with the same five columns you see here, plus the deeper fields below, so a sweep of 36,250 records lands in one predictable shape.

Thirteen fields ride along with every record, from the human-readable title down to tracking_summary, the view-and-download counter that shows which packages the public actually opens. The dictionary below is verified against live responses, not inferred from documentation.

Additional fields on request. Beyond the core skeleton, individual packages carry their own payload descriptions - resource-level file inventories with format labels, organization sub-records with center codes, tag vocabularies and per-package license identifiers whose values differ from band to band. Each gets pinned down against your sample before you commit, so the dictionary you build on is the dictionary you tested.

• Geography: Global earth observation on one end, solar system and deep space missions on the other. Earth-observing satellites see every continent; planetary holdings reach past Mars to the outer system.
• Temporal: Varies by holding - historical mission archives stretching back decades sit beside current satellite feeds. Per-record creation timestamps let you slice by when the entry entered the catalog rather than what period the data describes.
• Granularity: One catalog record per dataset package. Beneath each card, granularity belongs to the source archive - a planetary table might be per-asteroid, an earth-observation series per-pixel-per-day.

That breadth is the pitch against narrower catalogs: where a single-mission archive gives you depth in one domain, this index gives you the whole agency's publishing surface in one queryable frame.

API, files, or your warehouse. Daily, weekly, or hourly.

Pick the subject bands, pick the cadence, pick the landing zone - the same 13-field records arrive whichever way you take them. Every delivery ships the complete field dictionary above, the sample rows and the coverage profile, mapped before anything hits your pipeline. No integration archaeology: the link-out structure described above is already resolved, so a metadata card never dead-ends in your warehouse.

• Data scientists and ML engineers use the catalog as a training-set discovery engine: filter by band, pull the metadata uniformly, then route to the underlying archive only where a package earns it. See the data scientists use cases page for the workflow patterns.
• Developers and data-product builders normalize the whole corpus into one schema and ship search products over it - the uniform 13-field skeleton is what makes a single code path viable. The developers builders use cases page covers delivery-side detail.
• Competitive intelligence and product teams track which packages NASA's divisions publish and revise, reading the catalog as a map of where the agency's technical attention is going. The competitive intel product teams use cases page has the playbook.
• Journalists and academics cite primary mission and earth-science data with a clean provenance trail - every record names its owning organization and its license title. See the journalists academics use cases page.
• Investors and quant researchers screen earth-observation and satellite holdings as a demand signal before committing to commercial analytics subscriptions. The investors quants use cases page shows how.

Notes and adjacent reading:

• NASA Open APIs (api.nasa.gov) — the service layer sixteen documented REST endpoints deep: NEO orbits, space weather, EPIC imagery. This catalog finds the packages; the APIs serve live feeds.
• NASA Technical Reports Server (NTRS) — 646,659 citation records of reports and papers. Where this catalog describes data, NTRS holds the literature explaining it.
• Space-Track Space Catalog API — orbital state vectors and TLEs for tracked objects, the depth play where this catalog only gestures.
• Aerospace Datasets on Data.gov — the government-wide aerospace slice beyond NASA's own walls: Commerce, DoD components and state agencies.

Two glossary notes sharpen the vocabulary before you commit: what a CKAN metadata catalog actually is, and how general public catalog government data differs from licensed open data in practice.

Browse the whole vertical on the aerospace defense data hub, the ranked shortlist of best aerospace defense datasets, or the head-to-head vs FAA Aircraft Registry comparison.