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
I would suggest here changing the title of the notebook. User doesn't need to know this is the PRR since we talk everywhere about ESA cloud storage. I updated the text here.
I would suggest adding this notebook as the second one (2.2) since first clearly states we need to have STAC Items in any scenario. Then we request the storage on the PRR. Having the data + Items.
A pre-requisite to upload the data is to have descriptions of each file using STAC items. For examples how to do this see section 3.
This above should maybe point to the second notebook 2.2 self-stored files (which should be renamed to something else.
change the reference to example to data transformation example not creation of STAC Items from any data format, but actual data transformation process.
maybe even we can consider if that notebook is really necessary since what we need at the end is the location of the data, STAC Collection and STAC Items. And the PRR could be done anyway by the EarthCODE DS team.
What if there is more than one item to be added to the product collection? I think this is not addressed..
Suggestions to think about (at the stage of the implementation of semi-automatic collection creation to the PRR:
I would suggest here changing the title of the notebook. User doesn't need to know this is the PRR since we talk everywhere about ESA cloud storage. I updated the text here.
I would suggest adding this notebook as the second one (2.2) since first clearly states we need to have STAC Items in any scenario. Then we request the storage on the PRR. Having the data + Items.
A pre-requisite to upload the data is to have descriptions of each file using STAC items. For examples how to do this see section 3.
This above should maybe point to the second notebook 2.2 self-stored files (which should be renamed to something else.
change the reference to example to data transformation example not creation of STAC Items from any data format, but actual data transformation process.
maybe even we can consider if that notebook is really necessary since what we need at the end is the location of the data, STAC Collection and STAC Items. And the PRR could be done anyway by the EarthCODE DS team.
What if there is more than one item to be added to the product collection? I think this is not addressed..
Suggestions to think about (at the stage of the implementation of semi-automatic collection creation to the PRR:
This would replace following:
"The upload process to the PRR is manual at the moment, therefore you will have to email us with information about your: