-
Notifications
You must be signed in to change notification settings - Fork 43
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
Download only selected bands/files on cop_dataspace #1018
Comments
Hello @Rapsodia86 and thanks for this feature request and the associated inputs! Single assets download is already implemented on the You will be able to download individual assets from the new Not yet with |
For this feature, |
Walking through the node tree of the products to discover the assets requires a high number of HTTP request (~10 request per product), leading to a high execution time. As alternative solution, the manifest file can be used to get all the assets at once. The file name of the manifest is different among different Sentinel products:
A post on the Copernicus Data Space forum has been created to have a clarification on the different behaviors: https://forum.dataspace.copernicus.eu/t/location-of-the-manifest-of-sentinel-products/933/1 |
Hello,
I would like to ask if there is a chance at some point to extend some functionality for specific providers. Here, that would be Copernicus Dataspace.
Some datasets like e.g., Sentinel-1 or -2 can be pretty heavy, while a user may only need just a few bands (#910).
When querying thru oData e.g. "https://catalogue.dataspace.copernicus.eu/odata/v1" instead of downloading a whole zipped *.SAFE file, a user can download manifest XML only:
url = f"{catalogue_odata_url}/Products({product_identifier})/Nodes({product_name})/Nodes(MTD_MSIL1C.xml)/$value"
After taking band names from XML, a user can download files (bands) of interest. The whole approach is in https://github.com/eu-cdse/notebook-samples/blob/main/geo/odata_basics.ipynb (although there is a typo in the search (eu-cdse/notebook-samples#49).
Would that be something to consider?
Thanks!
The text was updated successfully, but these errors were encountered: