SWOT Data Product User Feedback

[colleen]

The Surface Water and Ocean Topography (SWOT) data products are publicly available through NASA’s Physical Oceanography Distributed Active Archive Center (PO.DAAC) .

Please refer to:

• “SWOT Dataset Information” for information on data products, along with product descriptions, algorithm theoretical basis documents, and sample data products where available.
• “Mission Events” for relevant information about spacecraft events that impact data quality and availability.
• “User RESOURCES” for resources for users of SWOT datasets distributed by the PO.DAAC
• “DATA Announcements” for latest PO.DAAC SWOT Data News and Announcements

All feedback and suggestions on the SWOT data products are welcomed and appreciated in this forum topic. Users are strongly encouraged to refer to the official release note for a comprehensive description of the known features and issues with the products before providing feedback.

Recent SWOT DATA Release Announcements:

• 2024/3/6: SWOT KaRIn Science Data Products

The public release of Surface Water and Ocean Topography (SWOT) Ka-band Radar Interferometer (KaRIn) Science Data Products. This release includes:

• KaRIn LR oceanography products from forward processing from November 23, 2023 (Cycle 7 from science phase) onward;
• KaRIn HR hydrology products from forward processing from January 25, 2024 (Cycle 10 from science phase) onward.

All forward-processed LR products from cycles 7-9 will be superseded by reprocessed LR products when they become available.

Reprocessing of science data products from March 30, 2023 to January 25, 2024 is ongoing. They will gradually be released as they become available over the next few weeks.

Please refer to the official release note for a more comprehensive description of the data coverage for each product in this release. Additionally, data users are encouraged to consult the Product Description Documents (PDDs) for detailed explanations of data product content and format. The PDDs can be accessed from the SWOT mission page on PODAAC web portal, and/or from the dataset landing pages for each product…. more>>

• 2024/2/28: SWOT Level 2 Nadir Altimeter and Advanced Microwave Radiometer Geophysical Data Record Release
• 2023/12/01: SWOT KaRIn Beta Pre-Validated Data Products
more>>

Resources for users of SWOT datasets distributed by the PO.DAAC
• PO.DAAC Cookbook - SWOT Chapter
• PO.DAAC Data Subscriber/Downloader
Video tutorial on using the podaac-data-subscriber
• Data search
Earthdata Search (GUI)
Earthdata Search tutorial
Earthaccess python library (using CMR API on backend)
• General information about Earthdata (AWS) cloud
Obtain Earthdata Login Account
Earthdata Cloud Primer documents
Earthdata Common Metadata Repository (CMR) API

The Surface Water and Ocean Topography (SWOT) mission aims to provide valuable data and information about the world's oceans and its terrestrial surface water such as lakes, rivers, and wetlands. SWOT is being developed jointly by NASA and Centre National D'Etudes Spatiales (CNES), with contributions from the Canadian Space Agency (CSA) and United Kingdom Space Agency (UKSA).

Earthdata user forums provide new workspaces for greater interaction between users, DAACs, and EOSDIS to address specific data, products, and concerns.

[cordmaur]

I'm using earthaccess to download PIXC and PIXCVec SWOT products.
For the same args (bbox and time range), the PIXCVec is returning several files that are not within the AOI.

Here is an example:

results = earthaccess.search_data(
short_name='SWOT_L2_HR_PIXC_2.0',
temporal=('2023-11-06', '2023-11-07'),
bounding_box=AOI.bounds
)
Granules found: 1

results = earthaccess.search_data(
short_name='SWOT_L2_HR_PIXCVec_2.0',
temporal=('2023-11-06', '2023-11-07'),
bounding_box=AOI.bounds
)

Granules found: 115
When we check for the results, we can see that several PIXVec files have Spatial Extent incorrectly (imho) set to -180, -90, 180, 90, and that's causing this discrepancy in the search (see attached image).

[PODAAC - celiaoued]

Hello,
Thank you for bringing this to our attention. The spatial extent for some files is indeed incorrectly set to a global bounding box, and we are working on a fix for this. I do not yet have an expected completion date for the fix, but I expect the problem will be corrected first for new incoming granules, and then afterwards for granules that had already been received before the fix (such as the example in your image).