I am trying to install Sentinel Hub Playground downloaded from Git (Opensource). I need guidance to configure the datasets inside src/store/config.js. For example, in the below Landsat 8 entry, I am getting
REACT_APP_L8L1C_INSTANCE_ID from the configuration tool on the portal. Where should I go to get the REACT_APP_EVAL3_L8L1C_INSTANCE_ID for the urlProcessingApi entry?
Secondly, how do I configure the initial starting up map that is shown by default when opening Sentinel Hub Playground on the web browser? Thank you
Hi @jan.jezersek - Thank you - much appreciated. I have applied the suggested corrections and it seems we are improving.
I am now getting a ‘no dates found’ error and no map is shown. See the below screen:
Sadly I believe this is not the client id that is used in that case, the one you need should be generated manually by our backend team. Therefore, I assume it still won’t fully work after you upgrade to the latest version.
How are you planning to use the app? If it’s just for personal use, then you can replace the anonymous authentication with client id/client secret approach.
Specifically, generate the client id and client secret as you did before, and add them to .env.
And then replace the code in src/components/AuthWindow.js with:
Cool - thank you, let me work on this and will give you feedback. We are currently evaluating the capability of Sentinel Hub Playground with the idea of using it as a front-end to our ODC (Open Data Cube)'s OGC compliant datasets/products. This is to provide open access to our satellite data.
Thank you so much - how can we get the client-id created by the backend team so that I do not have to apply the above code changes? This is not for personal use, we are using this as part of a project for my employer - SANSA (SOuth African National Space Agency) and we have an Enterprise subscription with you.
I talked to the team and we realised there’s an addition problem, related to the fact that for authentication a recaptcha key has to be specified as well, and the verification is currently hardcoded and tied to our accounts.
Therefore, having your own client_id will work when running locally, but it won’t work if you will try to deploy it to some endpoint. Is that what you had planned? In that case, the mentioned issue will have to be fixed first.
Ok, I understand, our plan is to deploy to an endpoint - we are planning to containerize it and deploy into a Kubernetes cluster in a docker container.So, addressing the issue will definitely help us. Thank you