A while ago we announced here that we are migrating data processing at Sentinel hub (SH) to evalscripts V3. We have prepared a converter and added support for evalscripts V3 to the EO Browser and to the Playground. We are now taking further steps towards the migration:
- For each of the data products which used evalscripts V1 or V2 we added their corresponding V3 version. When creating new layers you can now select only data products which use either evalscripts V3 or simple script.
- We converted all V1 and V2 evalscripts in our configuration templates.
- We converted all V1 and V2 evalscripts in the custom scripts repository and in our documentation.
- In the Dashboard:
- layers which use evalscript V1 or V2 (or data products V1 or V2) are now underlined with red color and marked with a small icon (up arrow)
- you can convert V1 and V2 evalscripts (and data products) with a click of the button
- you can convert and revert the conversion of the data products if needed
- We prepared a detailed tutorial for you to help you migrate to V3
All these changes have had no effect on your existing SH settings and configurations. Your SH requests still work as they have so far. This will remain so until the November 1st. This transition period is meant to give you enough time to fully migrate your SH configurations to V3.
Once the transition period is over we will disable support for evalscripts V1 and V2. At that point we will automatically:
- convert all non-converted evalscripts to V3 using the converter API and
- swap old data products (V1 and V2) with the corresponding V3 ones.
Depending on how you request the data from SH, this automatic conversion might result in obtaining different values from SH with existing SH requests as explained in impacts on OGC services chapter here. We thus encourage you to take full control over the conversion and convert your scripts and data products before the end of the transition period.
In case of any further questions, feel free to contact us on our forum.