These are two separate deployments of Sentinel Hub.
First one is stand-alone, second one is part of Copernicus Data Space Ecosystem. From the feature point of view they are almost the same, the biggest difference probably being that Copernicus Data Space Ecosystem does not support Landsat Collection 2 yet.
Copernicus Data Space Ecosystem also has a permanently free tier available, within specified quotas.
You can use either of these two, just make sure you use it consistently, i.e. the service end-points should be either:
Hi @ah.nikfal can you confirm that when you create your profile specific to Copernicus Data Space Ecosystem you are inputting all of the below parameters?
It’s important to set the token url and base url parameters as the default parameters for sentinelhub-py won’t work with Copernicus Data Space Ecosystem.
For some up to date examples on using sentinelhub-py with Copernicus Data Space Ecosystem I would recommend going through this notebook.
Hi @william.ray. Problem solved. Thanks for mentioning those critical points.
I had not set config.sh_token_url and config.sh_base_url in my config.toml (no need to config.save("cdse") for my case). So they had some other addresses (https://services.sentinel-hub.com/oauth/token and https://services.sentinel-hub.com).
I wonder if it was necessary to establish two separate services (services.sentinel-hub.com and sh.dataspace.copernicus.eu)? It was a bit confusing for me as the user.
Thank you for your feedback @ah.nikfal , indeed we are working on improving the documentation so that it is clearer for users such as yourself on how to configure your credentials if you are using the Copernicus Data Space Ecosystem.
I also started getting this auth error today (worked until yesterday) “oauthlib.oauth2.rfc6749.errors.UnauthorizedClientError: (unauthorized_client) Invalid client or Invalid client credentials”