You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, the CSLC-S1 workflow can generate independently CSLC-S1 products and CSLC-S1 static layers products.
For the generation of the CSLC-S1 products, we are able to assign product_version and product_specification_version from the runconfiguration file. Those two values get written inside the CSLC-S1 products.
Instead, for the CSLC-S1 static layers, the SAS is only able to write in the product_version while the product_specification_version is hard-coded within the SAS
What did you expect?
I expected that the CSLC-S1 would take the product_specification_version value from the runconfiguration file and assign it to the identification/product_specification_version field of the CSLC-S1 static layers product
Reproducible steps
Run the SAS to generate static layers
Environment
COMPASS v0.4.0
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
Describe the bug
At the moment, the CSLC-S1 workflow can generate independently CSLC-S1 products and CSLC-S1 static layers products.
For the generation of the CSLC-S1 products, we are able to assign
product_version
andproduct_specification_version
from the runconfiguration file. Those two values get written inside the CSLC-S1 products.Instead, for the CSLC-S1 static layers, the SAS is only able to write in the
product_version
while theproduct_specification_version
is hard-coded within the SASWhat did you expect?
I expected that the CSLC-S1 would take the product_specification_version value from the runconfiguration file and assign it to the identification/product_specification_version field of the CSLC-S1 static layers product
Reproducible steps
Environment
The text was updated successfully, but these errors were encountered: