Earthdata Search
The collection links throughout this guide open the corresponding datasets directly in NASA Earthdata Search.
Use Earthdata Search to:
- Review collection metadata
- Select temporal and geographic ranges
- Discover available granules
- Access data
- Review related documentation and resources
Automated Discovery with CMR
If your scripts query CMR directly, migration often requires updating the collection short name. A useful approach is to query the collection record first, inspect the returned collection version and concept ID, and then use the selected collection concept ID for granule searches when you want to target that specific collection. This avoids unnecessarily hard-coding a collection version into the discovery workflow.
Example 1 — Suomi NPP VIIRS Chlorophyll → NOAA-20/21 VIIRS
Before:
https://cmr.earthdata.nasa.gov/search/collections.json?short_name=VIIRSN_L3m_CHL
NOAA-20:
https://cmr.earthdata.nasa.gov/search/collections.json?short_name=VIIRSJ1_L3m_CHL
NOAA-21:
https://cmr.earthdata.nasa.gov/search/collections.json?short_name=VIIRSJ2_L3m_CHL
Example 2 — Chlorophyll → PACE OCI
PACE OCI chlorophyll is distributed as chlor_a within the BGC product suite rather than in a separate chlorophyll collection.
First, locate the PACE OCI BGC collection:
https://cmr.earthdata.nasa.gov/search/collections.json?short_name=PACE_OCI_L3M_BGC
Then search for granules within the desired time range. For example:
https://cmr.earthdata.nasa.gov/search/granules.json?short_name=PACE_OCI_L3M_BGC&temporal=2026-03-05T00:00:00Z,2026-03-06T23:59:59Z
This query returns PACE OCI BGC granules whose temporal coverage overlaps the specified period. Because the collection includes multiple temporal composites and mapped resolutions, the results may include daily as well as longer-period composite granules.
For more explicit collection targeting in automated workflows, resolve the desired collection first and use its returned concept ID in the granule query:
.../search/granules.json?collection_concept_id=<collection_concept_id>&temporal=<start>,<end>
CMR supports both short_name and parent collection concept ID for granule searches; using the concept ID explicitly targets the selected collection. Add a version constraint only when the workflow intentionally needs a specific collection version.
Reference: NASA Common Metadata Repository (CMR) Search API documentation.
Related Help Hub Tutorials
These tutorials complement the migration guidance above with hands-on examples for data discovery, file structure, version changes, and, where relevant, optional Level-2 swath processing.
- Access Data from OCI — search and retrieve data with earthaccess/CMR; the same search pattern can be adapted to other Earthdata collections.
- Explore Level-3 MODIS Ocean Color Data — a practical baseline for MODIS Level-3 discovery, download, and analysis with earthaccess.
- Data Structure at Three Processing Levels for OCI — compare OCI NetCDF groups, dimensions, and variables across L1B, L2, and L3M.
- Science Data Reprocessing and Product Versions — understand processing-version, collection-name, and file-structure changes that can affect existing code.
- Projecting PACE Data onto a Predefined Grid — useful background for users who independently choose a Level-2 swath workflow and need to work with provided latitude/longitude information, quality masking, and re-gridding.
Product and Algorithm Documentation
The ATBD and algorithm links in the product crosswalk above provide documentation for the corresponding products and retrieval approaches.
A common product or variable name identifies the same geophysical product, although sensor-specific algorithm implementations or coefficients may differ. Review the linked ATBDs when those implementation details matter for the scientific application. Mission and instrument links are provided in the transition sections above.
Need Help?
For questions about selecting or transitioning ocean color datasets: