Unavailable 'height_cor_xover' in HR Pixel cloud

[nushrat_yeasmin]

I am working with SWOT both LR and HR products in the coastal region. My region of interest includes SWOT track 348 and tiles 073L and 074L of the HR PIXC product. Unfortunately, for a few cycles (cycles 6, 9, 12, 13), the value of 'height_cor_xover' in these tiles is reported as 'nan'. However, if I access the same variable from the L2 LR Expert product, there are valid values.

The following files have 'height_cor_xover' reported as 'nan':

SWOT_L2_HR_PIXC_006_348_073L_20231114T230319_20231114T230331_PGC0_01
SWOT_L2_HR_PIXC_006_348_074L_20231114T230329_20231114T230341_PGC0_01
SWOT_L2_HR_PIXC_009_348_073L_20240116T131835_20240116T131846_PGC0_01
SWOT_L2_HR_PIXC_009_348_074L_20240116T131845_20240116T131856_PGC0_01
SWOT_L2_HR_PIXC_012_348_073L_20240319T033348_20240319T033400_PIC0_01
SWOT_L2_HR_PIXC_012_348_074L_20240319T033358_20240319T033410_PIC0_01
SWOT_L2_HR_PIXC_013_348_073L_20240409T001853_20240409T001904_PIC0_01
SWOT_L2_HR_PIXC_013_348_074L_20240409T001903_20240409T001914_PIC0_01

My question is, will 'height_cor_xover' in these files be updated in version C processing, or will they be corrected in the next reprocessing cycle?

During the SWOT Science Team Meeting in 2024, I was advised to report this issue in this forum.

Thanks in advance.

[PODAAC - celiaoued]

Hello,
I have not heard of any concrete plans for when 'height_cor_xover' will be available in the HR Pixel cloud. In the HR files you mention of track 348, the quality flag indicates that the crossover correction is unavailable or nonsensical. In the equivalent LR SSH files (example SWOT_L2_LR_SSH_Expert_012_348_20240319T032247_20240319T041315_PIC0_01.nc), the values for crossover correction are present, as you mention, but they are also accompanied by 'heigh_cor_xover_qual' indicating they are all suspect values. So the LR SSH and HR Pixel cloud crossover correction quality are consistently unavailable for these cases.

[nushrat_yeasmin]

Hello,
Thank you very much for the reply.
In this kind of cases, where 'height_cor_xover' correction is not available or of 'suspect' level quality, what would be the best practice to follow? Is there any other way around to have a better estimation of this correction?

Thanks in advance