Forum

Thanks for reporting your observation. Yes July 10 product for this specific frame has known issue and will be reprocessed in future. Due to an edge case in raw data processor, the raw data may be shifted when there is a discarded/missing pulse and that impacts the downstream products. The issue wil...

Thanks for posting the plot of connected components. Yes I agree that the connected component in this case is affected by invalid region at the boundary of the swath and is not immediately useful for identifying/correcting unwrapping errors. It looks to me that the unwrapper has not respected the su...

Thank you for sharing your analysis. Yes users should be aware that there is no easy way to connect possible disconnected islands in an operational system. The provided connected components should help users to identify the separated components and adjust as they wish if they have auxiliary informat...

P05023 provisional products, do not include masks and metrics to help users discard such data. We are indeed adding these metrics in the next delivery. We understand the importance of such metrics for users and will update as they become available.

The cause of this issue is same as the post here : https://forum.earthdata.nasa.gov/viewtopic.php?t=8118 The root cause is an edge case in raw data processor which does not correctly time-tag the raw data in presence of discarded rangeline. I confirm that the ghost image disappears after using a new...

Thanks for reporting this issue. The problem originates from corrupted input raw data. Looking at the reference RSLC shows that the image is fully defocused and therefore the interferometry fails to produce any useful product. For example see this RSLC product: NISAR_L1_PR_RSLC_010_077_A_024_4005_DH...

Thank you for reporting this edge case. We were able to reproduce the issue. The source of the issue is the DEM at higher latitudes which seems to have a small discontinuity between tiles. We are investigating a possible solution and will update when we have more information.

Thank you for reporting this issue. This is a known issue due to missing rangelines or discarded rangelines in raw data and an edge case in raw data processor that does not properly update the time tag of remaining pulses after discarding some (in this case probably only one pulse out of 100s of tho...

Thanks for your post. Your approach to convert the GSLC backscatter to sigma-0 is not correct. The RSLC and subsequently GSLC are provided as Beta-0 with respect to an ellipsoid. If you want to convert to sigma-0 you must use the sigma-0 correction factor which is included in theGSLC products at the...