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
Definition of the workflow at the beginning of the notebook according to the Architecture Document (D..6.1)
what DATA the workflow takes as input and output, i.e. GeoTIFF, Netcdf . Here I see it confusing to be honest because sometimes we may take as an input .SAFE (Sentinel product) and have as an output zarr file or nc? How to deal with that? What the user should insert if the output and input formats do not correspond?
Property: workflow_contracts_info should be "contacts info" not contracts
Again here I'm not sure about format in which we ask for the email. Shoulf it be mandatory? If yes how do we deal with that personal information?
I would update the codeurl variable with the workflow_url to create less confusion. Where this url should point a user to? Maybe some guidance here would be useful?
Why do we need to have workflow start and end date? Maybe we should only relate to the creation datetime? Or latest version datetime property instead of time_range – which I don't see much useful for workflow, rather for products? Or should we keep both? How this translates in the properties of the metadata record.json?
geometry property, should be possible to add multiple regions (as separate polygons, not only unique bbox)
markdown cell added before the start of the last cell
Definition of the workflow at the beginning of the notebook according to the Architecture Document (D..6.1)
what DATA the workflow takes as input and output, i.e. GeoTIFF, Netcdf . Here I see it confusing to be honest because sometimes we may take as an input .SAFE (Sentinel product) and have as an output zarr file or nc? How to deal with that? What the user should insert if the output and input formats do not correspond?
Property: workflow_contracts_info should be "contacts info" not contracts
Again here I'm not sure about format in which we ask for the email. Shoulf it be mandatory? If yes how do we deal with that personal information?
I would update the codeurl variable with the workflow_url to create less confusion. Where this url should point a user to? Maybe some guidance here would be useful?
Why do we need to have workflow start and end date? Maybe we should only relate to the creation datetime? Or latest version datetime property instead of time_range – which I don't see much useful for workflow, rather for products? Or should we keep both? How this translates in the properties of the metadata record.json?
geometry property, should be possible to add multiple regions (as separate polygons, not only unique bbox)
markdown cell added before the start of the last cell