Summary
- A new openEO endpoint is now available: https://openeo.terrascope.be/openeo/1.2/
- CDSE authentication is now required to access the new endpoint
- The current environment will be decommissioned on June 15, 2026
- Users should test workflows and migrate important data before that date
Upcoming Migration
Terrascope is preparing an important update to its openEO platform infrastructure to improve the user experience. This update includes a migration to a new Hadoop cluster and a transition to a unified user and credit management system, powered by the Copernicus Data Space Ecosystem (CDSE) openEO federation. This means you get the best of both worlds: a dedicated, familiar entry point for processing Terrascope datasets directly, combined with the full capabilities of the federation, including access to global Sentinel archives and a broad range of Copernicus Services products with one login!
As part of this transition, a new openEO endpoint is now available: https://openeo.terrascope.be/openeo/1.2/
The new endpoint is fully integrated with CDSE, enabling unified account and credit management as part of the CDSE openEO federation. This is aligned with the other openEO endpoints, and especially with the openEO federation endpoint (https://openeofed.dataspace.copernicus.eu). When deciding which endpoint to use, ask yourself if you will work on Terrascope datasets only. If so, use https://openeo.terrascope.be. If you will also need data sets that are hosted by CDSE, then use https://openeofed.dataspace.copernicus.eu.
This update also brings a unified credit and account management system with CDSE, eliminating the need to manage credits separately for Terrascope and CDSE. CDSE will now be your central location to handle accounts and credits, streamlining the process and enhancing user experience.
The current Terrascope openEO environment will remain available until June 15, 2026. After that date, the old environment will be decommissioned, and the existing endpoint (https://openeo.vito.be) will redirect to the new one.
This migration affects all users of the Terrascope openEO platform and requires action before June 15, 2026.
A separate communication about the broader transition of user credits and accounting towards the CDSE ecosystem will follow later. All assigned credits from user accounts will remain applicable in the renewed setup.
What you need to do
Before June 15, 2026, we strongly recommend that all users:
- Create a CDSE account and start using it to access Terrascope openEO
- Start testing workflows on the new endpoint
- If needed, download important batch job results from the old environment
- If needed, re-upload User-Defined Processes (UDPs)
Although the new openEO environment is designed to be functionally equivalent to the current one, we recommend validating your workflows early and reporting any unexpected behavior.
Step 1 — Set Up CDSE Authentication
The new environment requires authentication through the Copernicus Data Space Ecosystem (CDSE). Please ensure you have created an account on CDSE, as described in the online documentation.
Linking your account and testing access to the new Terrascope openEO endpoint
- Open the Terrascope page: https://terrascope.be
- Click the sign-in button in the top right corner
- Click the Copernicus Data Space Ecosystem button to link your CDSE account with your existing Terrascope account
- Open the openEO Web Editor: https://editor.openeo.org/?server=https%3A%2F%2Fopeneo.terrascope.be%2F
- Select Copernicus Data Space Ecosystem
- Click Login with Copernicus Data Space Ecosystem
- Use your CDSE account to log in
Step 2 — Migrate Your Workflows
To migrate your workflows, please update the connection endpoint in your openEO script to the new endpoint as shown in the example below:
import openeo
openeo.connect("https://openeo.terrascope.be")
What changes?
For most users, workflows should continue to operate without modification.
The openEO software stack and batch processing environment remain functionally equivalent to the current platform. We nevertheless recommend testing your workflows as early as possible and contacting us (see below) if you encounter unexpected behavior.
Step 3 — Download existing Batch Jobs and Results
Batch jobs and their results from the old cluster will not be migrated automatically.
If you want to keep existing results, you must download them before June 15, 2026.
Results can be downloaded through the openEO Web Editor or via the openEO client libraries.
Documentation:
- Python client batch job downloads: https://open-eo.github.io/openeo-python-client/batch_jobs.html#download-batch-job-results
- openEO Web Editor: https://docs.terrascope.be/Tools/openEOWebEditor/openEOWebEditor.html
Step 4 — Re-upload your User-Defined Processes (UDPs)
User-Defined Processes are not migrated automatically to the new environment.
If you use UDPs, you will need to upload them again manually after migrating.
A migration example notebook is available on GitHub here.
Collection Availability Changes
A limited number of legacy Sentinel Hub–based collections will no longer be available on the new cluster.
The following collections will be removed:
- MODIS (planned for future availability through CDSE)
- MAPZEN_DEM
- PLANETSCOPE
- POPULATION_DENSITY
- SENTINEL1_GAMMA0_SENTINELHUB
- SENTINEL2_L1C_INCD
- SENTINEL2_L2A_MOSAIC_120
Some of these collections have already been deprecated in the previous environment.
If one of them is important for your workflows, please contact us (see below).
Access to the Full Copernicus openEO Federation
The new endpoint will also be available in the CDSE federation:
https://openeofed.dataspace.copernicus.eu
The CDSE federation provides seamless access to both Terrascope and CDSE datasets, making it the recommended way to enjoy backend-independent processing.
Python 3.8 Deprecation Reminder
The Python 3.8 environment will be frozen on June 15, 2026 and will no longer receive updates.
Users are encouraged to migrate UDFs and custom workflows to Python 3.11 if they have not already done so.
More information:
https://terrascope.be/en/news-events/upcoming-migration-python-311-openeo-udfs
Need Help?
If you have questions or encounter migration issues, please contact us:
info@terrascope.be
We strongly recommend starting your migration as early as possible to ensure a smooth transition before June 15, 2026.
