Timeline for Sentinel2 : get JPEG200 bands only
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2019 at 14:34 | comment | added | Duarte Carreira | Also the path changed a bit since 2017, and now the band files are inside a folder indicating the resolution. So there are 3 folders R10m, R20m, R60m, after IMG_DATA. You need to change the last urljoin to account for that: /Nodes('IMG_DATA')/Nodes('R10m')/Nodes?$format=json | |
| Aug 22, 2019 at 14:31 | comment | added | Duarte Carreira | Very nice code. Also, aws transitioned to "requester pays" so it is really not that open any more. | |
| Apr 5, 2017 at 13:27 | comment | added | Kersten | If you want fast queries - query the AWS Sentinel-2 bucket. Dealing with multiple granules in a single product (i.e. the old product format) is possible as well - but you need to know which granules you are after. Apart from querying there is no way to convert the UUID to a product name. | |
| Apr 5, 2017 at 13:00 | comment | added | manatttta | The problem here is that a product can have multiple granules, etc. Also, each query to the odata API is painfully slow, at least in my system... If there were an expedite way of doing this a priori.. | |
| Apr 5, 2017 at 12:22 | history | answered | Kersten | CC BY-SA 3.0 |