WEkEO

___________________________________________________________

As we explained <a href="https://help.wekeo.eu/en/articles/15012839-accessing-clms-data-on-wekeo">in this article</a>, the Copernicus Land Monitoring Service (CLMS) is progressively migrating its data to the Copernicus Data Space Ecosystem (CDSE).

From 30 June 2026, some HRL datasets previously provided through their legacy source will be available from the CDSE only.

If you access any of the following datasets from WEkEO, you may need to update your queries depending on the product type, resolution and year:

<code>EO:EEA:DAT:HRL:CRL</code> - High Resolution Layer Croplands products

<code>EO:EEA:DAT:HRL:GRA</code> - High Resolution Layer Grasslands products

<code>EO:EEA:DAT:HRL:TCF</code> - High Resolution Layer Tree Cover and Forests products

- <code>EO:EEA:DAT:HRL:CRL</code> - High Resolution Layer Croplands products
- <code>EO:EEA:DAT:HRL:GRA</code> - High Resolution Layer Grasslands products
- <code>EO:EEA:DAT:HRL:TCF</code> - High Resolution Layer Tree Cover and Forests products

For specific combinations of <code>dataset_id</code>, <code>productType</code>, <code>resolution</code> and <code>year</code>, you must now:

update the value of <code>dataset_id</code> to reflect the transition to the new collection on CDSE: <code>EO:JRC:DAT:CLMS</code>

discard the <code>productType</code> and <code>resolution</code> fields which are not used anymore

add the <code>datasetIdentifier</code> corresponding to your dataset of interest. Please refer to the table below to identify which <code>datasetIdentifier</code> is relevant for your query. Combinations for which no <code>datasetIdentifier</code> is provided will continue to remain available with the existing queries for the time being. These combinations correspond to 2012 and 2015 for the datasets delivered for a specific year, and to the periods 2012-2015 and 2015-2018 for the datasets describing changes over a specific time interval.

specify the time interval using appropriate <code>startdate</code> and <code>enddate</code> values:

- For datasets delivered on a yearly basis, if you are interested in the year YYYY, your time interval must include January 1, YYYY
- For changed datasets, if you are interested in the period YYYY-ZZZZ, the time interval must also include January 1, YYYY

- update the value of <code>dataset_id</code> to reflect the transition to the new collection on CDSE: <code>EO:JRC:DAT:CLMS</code>
- discard the <code>productType</code> and <code>resolution</code> fields which are not used anymore
- add the <code>datasetIdentifier</code> corresponding to your dataset of interest. Please refer to the table below to identify which <code>datasetIdentifier</code> is relevant for your query. Combinations for which no <code>datasetIdentifier</code> is provided will continue to remain available with the existing queries for the time being. These combinations correspond to 2012 and 2015 for the datasets delivered for a specific year, and to the periods 2012-2015 and 2015-2018 for the datasets describing changes over a specific time interval.
- specify the time interval using appropriate <code>startdate</code> and <code>enddate</code> values:
 - For datasets delivered on a yearly basis, if you are interested in the year YYYY, your time interval must include January 1, YYYY
 - For changed datasets, if you are interested in the period YYYY-ZZZZ, the time interval must also include January 1, YYYY

📌 Note: these changes will remain valid for a limited period of time as we are working on the implementation of a more user-friendly approach based on the definition of « virtual » dataset layers.

⚠️ If your combination is not listed, no change is required for now.

Here you can download the table in <code>.xlsx</code> format to check the HRL datasets changes:

Additional resources can be found in our<a href="https://help.wekeo.eu/en/"> Help Center</a>. Should you require further assistance or wish to provide feedback, feel free to contact us through a chat session available in the bottom right corner of the page.

From 30 June 2026, some CLMS HRL datasets will be available from CDSE only. Learn which datasets are affected and how to update your WEkEO queries using the new provided parameters.

Action required: changes to data access for CLMS HRL datasets

Create a custom design with text, images, and links

Home

Data

Sign Up

Data Status

System Status

Go to WEkEO

Data Catalogue

Jupyter Catalogue

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

Try using different keywords or checking for typos.

No conversations found

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Track the progress of all tickets and conversations related to your company.

Customer Portal.

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

Action required: changes to data access for CLMS HRL datasets

Context

What you need to do

Summary table

What's next?