-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
source product version and slicing checks #233
Comments
The situation is even more complicated. The reprocessed NRT product is the one that was processed last:
So, ASF just keeps the products that were processed last. In this case this might not suffice. I have opened an issue at ASF about this. |
@avalentino may I ask for your opinion? |
#236 is only a temporary fix for GRD neighbor selection. the scene search functionality still does not differentiate between different versions. |
Currently the processor does not do anything to filter duplicate source products. It often happens that source products (GRD/SLC) are reprocessed and, if the data archive is not optimally curated, multiple versions of the same acquisition may exist. In some cases the reprocessed products are also resliced so that both versions may not easily be compared by the acquisition times.
Consider the following case. A data take of products was first acquired in NRT slicing mode (manifest.safe metadata attribute
sliceNumber=0
), reprocessed in NRT slicing mode using a different slicing, and later reprocessed again, this time in regular slicing mode (sliceNumber>0
) and using the same slicing as first reprocessed version. Hence, three versions of the same data take may exist. At the time of writing, ASF only offers the older NRT version and CDSE offers all three versions. In case CDSE is used as reference archive,s1ard
has no way of determining which are the right products to use.The text was updated successfully, but these errors were encountered: