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'm just getting to grips with the STAC plugin and am loving how simple it is to use - will revolutionize how I download Sentinel imagery. One problem. When using the Advanced Filtering options to set maximum cloud cover using the query {"eo:cloud_cover":{"lt":50}} I get an error message saying "Problem in fetching content for https://planetarycomputer.microsoft.com/api/stac/v1.Error details, None". See image attached below:
Doesn't matter what I set the cloud cover threshold to or whether I use "gte" and "lte" to specify ranges of cloud cover. It works fine without the filter, and the same filter string seems to work fine in online tutorials I have watched. I am running the current long term stable release of QGIS (Firenze) and version 1.1.1 of the plugin from the Plugin Manager. Not sure if there is a version compatibility issue or some error on my side? Any help appreciated as this is the last thing holding me back from fully using the plugin.
Thanks
Sam
The text was updated successfully, but these errors were encountered:
Hi,
I'm just getting to grips with the STAC plugin and am loving how simple it is to use - will revolutionize how I download Sentinel imagery. One problem. When using the Advanced Filtering options to set maximum cloud cover using the query
{"eo:cloud_cover":{"lt":50}}
I get an error message saying "Problem in fetching content for https://planetarycomputer.microsoft.com/api/stac/v1.Error details, None". See image attached below:Doesn't matter what I set the cloud cover threshold to or whether I use "gte" and "lte" to specify ranges of cloud cover. It works fine without the filter, and the same filter string seems to work fine in online tutorials I have watched. I am running the current long term stable release of QGIS (Firenze) and version 1.1.1 of the plugin from the Plugin Manager. Not sure if there is a version compatibility issue or some error on my side? Any help appreciated as this is the last thing holding me back from fully using the plugin.
Thanks
Sam
The text was updated successfully, but these errors were encountered: