Skip to main content
v2026.11,986 entries · CC-BY 4.0

Copernicus Open Access Hub: Sentinel Data and Migration Guide

The Copernicus Open Access Hub provided access to Sentinel satellite data before ESA replaced it with the modern Copernicus Data Space Ecosystem.

Written and maintained by CASRAI Editorial Board

Published

On this page

The Copernicus Open Access Hub (formerly known as the Sentinels Scientific Data Hub or SciHub) was the official open-access data dissemination portal operated by the European Space Agency (ESA) on behalf of the European Union’s Copernicus Programme, providing free, full, and open access to Earth observation imagery captured by the Sentinel satellite constellation from 2014 until its formal decommissioning in October 2023. Following its retirement, all operational data access, programmatic application programming interfaces (APIs), and interactive catalog exploration migrated entirely to the Copernicus Data Space Ecosystem (CDSE), which now serves as the unified European cloud platform for discovering, processing, and downloading Copernicus Earth observation assets.

What the Copernicus Open Access Hub Was and Its Role in Earth Observation

Launched by the European Space Agency in late 2014 alongside the deployment of the Sentinel-1A radar satellite, the Copernicus Open Access Hub served for nearly a decade as the central gateway through which researchers, environmental agencies, and commercial developers retrieved raw and processed satellite data. Built on the open-source Data Hub Software (DHuS) framework developed by ESA and GAEL Systems, the hub provided an OpenSearch interface alongside an OData service, enabling users to query spatial footprints, acquisition dates, mission parameters, and cloud coverage across millions of Earth observation granules.

Before the Sentinel missions and the Open Access Hub, European satellite data often required specialized scientific project proposals, geographic quotas, or commercial fees. Under the Copernicus Regulation adopted by the European Union, the Open Access Hub instituted a full, free, and open data access policy for scientific research, public administration, education, and commercial exploitation worldwide. This policy established parity with the USGS Landsat archive, transforming remote sensing research across climatology, oceanography, forestry, and disaster response.

As the Sentinel satellite fleet expanded to include Sentinel-2 optical imaging, Sentinel-3 ocean and land monitoring payloads, and Sentinel-5P atmospheric instruments, the hub handled unprecedented dissemination volumes. By the time of its retirement in late 2023, the platform had registered more than 600,000 user accounts and distributed tens of petabytes of Earth observation products. Researchers relied on automated Python workflows, most notably the widely adopted sentinelsat utility library, which systematically queried the hub’s OpenSearch API and queued product downloads to local servers.

The infrastructure adhered to international spatial data standards, aligning with the European INSPIRE Directive and facilitating interoperability with global repositories. By maintaining persistent metadata catalogs and open endpoints, the platform enabled research data stewards to fulfill FAIR data principles by citing exact granule identifiers and acquisition orbits in published scientific literature.

Who Operated the Hub and the Scope of Sentinel Mission Data

The Copernicus Open Access Hub was funded by the European Union under the Copernicus Programme and operated directly by the European Space Agency from its ESRIN facility in Frascati, Italy, in partnership with industrial consortia including Serco, GAEL Systems, and CloudFerro. ESA managed ground segment operations, catalog ingestion pipelines, archive storage, and user authentication infrastructure.

The core coverage of the hub spanned the primary Sentinel operational constellations, each engineered to address specific environmental observation domains:

  • Sentinel-1 Constellation (C-Band Radar): Delivering continuous all-weather synthetic aperture radar (SAR) imagery at 5.405 GHz. The hub distributed Level-0 raw data, Level-1 Single Look Complex (SLC) products preserving phase information for interferometric SAR, Level-1 Ground Range Detected (GRD) products for surface roughness and flood mapping, and Level-2 Ocean (OCN) products for surface wind fields and ocean waves.
  • Sentinel-2 Constellation (Multispectral Optical): Providing systematic optical imagery across 13 spectral bands spanning visible, near-infrared, and shortwave-infrared wavelengths. Products included Level-1C Top-Of-Atmosphere (TOA) reflectance in cartographic geometry (UTM/WGS84 tiles of 100 km by 100 km) and Level-2A Bottom-Of-Atmosphere (BOA) surface reflectance processed through atmospheric correction algorithms, with spatial resolutions from 10 to 60 meters.
  • Sentinel-3 Constellation (Ocean and Land Monitoring): Hosting multi-instrument payloads including the Ocean and Land Colour Instrument (OLCI), the Sea and Land Surface Temperature Radiometer (SLSTR), and the Synthetic Aperture Radar Altimeter (SRAL). Products covered sea surface temperature, ocean color, vegetation index climatology, and topography.
  • Sentinel-5 Precursor (Atmospheric Chemistry): Featuring the Tropospheric Monitoring Instrument (TROPOMI), measuring column densities of atmospheric trace gases including nitrogen dioxide, ozone, sulfur dioxide, carbon monoxide, methane, and aerosol optical depth for air quality and greenhouse gas tracking.

In addition to core Sentinel missions, the hub occasionally offered specialized access points for Copernicus Contributing Missions and global elevation models, functioning as a primary scientific data repository for Earth observation scientists across the European Union and international research institutions.

Why ESA Decommissioned the Hub in Favor of the Copernicus Data Space Ecosystem

Despite its historic success, the architecture of the Copernicus Open Access Hub faced severe scalability bottlenecks as daily data generation expanded exponentially. Built during an era when Earth observation research relied primarily on downloading entire raw scene packages (compressed .SAFE archives often exceeding 1 gigabyte per granule) to local workstations, the platform’s storage and bandwidth model became unsustainable under petabyte-scale data flows.

Key architectural and operational drivers for decommissioning the Open Access Hub included:

  • Storage and Retrieval Latency (Rolling Archives): As archives expanded beyond near-line disk storage, ESA instituted a rolling archive policy on the hub. Products older than 6 to 12 months were moved from online disks to offline tape storage. Historical requests returned an HTTP 202 Accepted status and queued an asynchronous tape retrieval taking up to 24 hours to fulfill, delaying long-term time-series studies.
  • Egress Bandwidth Bottlenecks: Distributing millions of multi-gigabyte raw files across public internet connections placed heavy strain on European network backbones. Institutional research groups with modest internet connections struggled to download multi-terabyte data batches required for continental-scale mapping.
  • Absence of Server-Side Processing: The legacy hub functioned strictly as a file warehouse without native server-side compute resources. Researchers had to download complete multispectral tiles merely to analyze a 10-hectare agricultural field or extract a single normalized difference vegetation index (NDVI) time-series curve.
  • Adoption of Cloud-Native Geospatial Formats: Contemporary geospatial science has pivoted toward Cloud-Optimized GeoTIFFs (COGs), SpatioTemporal Asset Catalogs (STAC), and raster streaming APIs, allowing users to query individual pixel subsets or spectral bands directly over HTTP without downloading unnecessary data channels.

In November 2022, the European Commission and ESA awarded a major service contract to an industrial consortium led by T-Systems, alongside CloudFerro, Sinergise, VITO, DLR, and CGI, to construct the next-generation infrastructure: the Copernicus Data Space Ecosystem (CDSE). Officially launched in January 2023, CDSE established an immediate online archive of all Sentinel data alongside integrated cloud analytics and modernized APIs. ESA permanently closed user registrations and data downloads on the legacy Copernicus Open Access Hub on October 31, 2023, completing the migration.

How to Search and Access Sentinel Data via the Copernicus Data Space Ecosystem

Earth observation researchers seeking Copernicus Sentinel imagery must now utilize the official tools and endpoints provided by the Copernicus Data Space Ecosystem. For visual discovery, exploratory inspection, and ad-hoc granule downloads, the primary interface is the Copernicus Browser (replacing the legacy Open Access Hub web interface). Official documentation outlines the exact multi-step workflow for discovering and retrieving data:

  1. Navigate to the Official Portal: Open the official interface at dataspace.copernicus.eu and access the Copernicus Browser application. To download data or configure automated processing, sign in using your free Copernicus Data Space credentials via the integrated authentication portal.
  2. Define the Geographic Area of Interest (AOI): Use the interactive map viewport to locate your study area, or employ the spatial geometry tools in the sidebar to draw a custom polygon, define a rectangular bounding box, or upload an existing vector boundary file in GeoJSON, KML, or ESRI Shapefile format.
  3. Select Satellite Constellation and Sensor Configuration: In the search parameters panel, check the target mission collection—such as Sentinel-1 SAR, Sentinel-2 MSI, Sentinel-3, or Sentinel-5P. For optical missions such as Sentinel-2, specify the desired processing level (e.g., Level-1C Top-Of-Atmosphere reflectance or Level-2A atmospherically corrected surface reflectance).
  4. Configure Temporal and Atmospheric Filters: Set the calendar date range for your acquisition window. For optical missions, set the maximum acceptable cloud cover threshold (e.g., cloud cover below 20 percent) to eliminate cloud-obscured scenes from your candidate list.
  5. Execute Search and Inspect Candidate Acquisitions: Click the Search button to view matching acquisition footprints on the interactive map and browse the chronological results list. Use the visual preview tools to inspect false-color composites, examine spectral bands, and verify atmospheric clarity across individual scenes.
  6. Download Products or Stream Data: Select an individual product to inspect its metadata, granule identifier, and file manifest. Click the Download Product button to retrieve the complete standard archive package, or utilize the analytical tools to download targeted analytical GeoTIFFs, spectral indices, or analytical image crops directly.

For users analyzing Sentinel-2 satellite imagery, the browser also provides real-time visualization overlays, allowing researchers to evaluate vegetation health indices, moisture stress, and false-color infrared composites before initiating full product downloads.

Programmatic Migration: Transitioning from DHuS and sentinelsat to Modern OData and STAC APIs

The retirement of the Open Access Hub significantly impacted automated research scripts and ingestion pipelines that relied on legacy DHuS OpenSearch endpoints and static HTTP Basic Authentication credentials. The Copernicus Data Space Ecosystem replaced these protocols with modern RESTful APIs adhering to OData v4 and STAC specifications, secured through Keycloak OpenID Connect (OIDC) token management.

Understanding how the architectural layers map from the legacy system to the modern platform is essential for software engineers and data scientists maintaining research pipelines:

  • Authentication Architecture: Legacy scripts passed cleartext usernames and passwords directly via HTTP Basic Auth headers to scihub.copernicus.eu. The Copernicus Data Space Ecosystem mandates OAuth 2.0 / OIDC authentication. Scripts send an HTTP POST request containing credentials to the Keycloak token endpoint at identity.dataspace.copernicus.eu, obtain a JSON Web Token Bearer access token, and pass that token in the HTTP Authorization header for subsequent requests.
  • Catalog Discovery Protocol: The legacy OpenSearch endpoint used proprietary Solr-style syntax. CDSE provides two modernized discovery interfaces: an OData v4 catalog endpoint (https://catalogue.dataspace.copernicus.eu/odata/v1/Products) supporting URL filter expressions, and a SpatioTemporal Asset Catalog (STAC) v1 endpoint (https://stac.dataspace.copernicus.eu/v1/) supporting standard GeoJSON spatial geometry payloads and property filtering.
  • Direct Product Download Endpoints: Rather than querying legacy archive URLs, full product packages in the CDSE catalog are downloaded via the OData value endpoint: https://catalogue.dataspace.copernicus.eu/odata/v1/Products(UUID)/$value, passing the active Bearer token.
  • Software Client Upgrades: The legacy sentinelsat Python package has been largely superseded. Developers now rely on modernized libraries such as pystac-client, the official CDSE Python SDK, or direct integration with cloud-native raster tools like rioxarray and rasterio.

Beyond basic catalog querying, CDSE integrates the Sentinel Hub API suite (including Process and Statistical APIs), enabling algorithms to request on-the-fly atmospheric correction, band math, and statistical aggregations without manually parsing multi-gigabyte zip files. This cloud-native paradigm aligns with modern platforms such as the Copernicus Climate Data Store (C3S), which similarly emphasizes server-side data processing and standardized API queries.

Strengths, Technical Boundaries, and Architectural Evolution

The transition from the Copernicus Open Access Hub to the Copernicus Data Space Ecosystem represents a generational leap in Earth observation data distribution, although specific operational boundaries remain relevant for large-scale institutional computing facilities.

The principal operational strengths of the modern ecosystem include:

  • Elimination of Tape Retrieval Latencies: The entirety of the multi-petabyte Sentinel archive is retained in immediate online object storage. Researchers no longer experience 24-hour waiting periods when requesting historical granules from early mission phases.
  • Integrated Cloud Processing and Virtual Labs: CDSE incorporates managed JupyterLab environments, openEO processing engines, and direct S3-compatible object storage access (eodata) within European cloud infrastructure, allowing researchers to run batch machine learning algorithms adjacent to the data archive.
  • Multi-Mission Integration: Alongside Sentinel data, the ecosystem consolidates Copernicus Digital Elevation Models (COP-DEM), Copernicus Land Monitoring Service (CLMS) high-resolution layers, and data from contributing third-party missions into a single coherent catalog.
  • Adoption of Open Geospatial Standards: By implementing STAC and OData v4 standards, CDSE integrates natively with open-source GIS platforms (such as QGIS), cloud data catalogs, and modern spatial data science ecosystems.

Despite these extensive improvements, researchers and laboratory managers must navigate specific technical boundaries:

  • Download and Concurrency Quotas: While data remains free, anonymous access is prohibited. Self-registered free user accounts are subject to rate limiting and maximum concurrent download limits (typically two to four parallel data streams). High-throughput research projects requiring hundreds of parallel downloads must apply for research project compute grants or sponsor commercial cloud compute credits.
  • Token Expiration and Session Management: Automated batch pipelines running over days must implement robust token renewal mechanisms, as Keycloak access tokens expire after a standard duration (typically 10 to 60 minutes) and require refresh token exchanges.
  • Storage Architecture Differences: Granules stored in CDSE S3 object storage are organized as directories rather than single zipped archives in certain cloud tiers, requiring adjustments in legacy automated unzipping routines.

Alternatives for Accessing Sentinel Satellite Imagery

While the Copernicus Data Space Ecosystem is the primary European reference archive, Earth observation researchers have multiple viable alternative repositories and cloud platforms for accessing Sentinel mission data, each offering distinct advantages depending on compute resources, geographic location, and institutional infrastructure:

Platform / Repository Operating Entity Access Model and Pricing Primary Access Protocol Core Strengths and Best Use Cases
Copernicus Data Space Ecosystem (CDSE) ESA / European Commission / T-Systems Consortium Free open access; tiered API processing units OData v4, STAC v1, Sentinel Hub APIs, Copernicus Browser Authoritative primary archive; immediate access to complete historical Sentinel catalog and European cloud compute
NASA Earthdata (ASF DAAC / LP DAAC) NASA / USGS / Alaska Satellite Facility Free open access for registered NASA Earthdata users HTTPS REST, Vertex GUI, STAC API, Python SDK Global SAR processing specialization; exceptional Sentinel-1 archive and interferometric SAR tools at Alaska Satellite Facility
AWS Registry of Open Data (Sentinel Collections) Amazon Web Services / Sinergise / Element 84 Free public buckets; standard AWS compute charges S3 object storage, Earth Search STAC API, Cloud-Optimized GeoTIFFs High-throughput cloud computing; ideal for deploying scalable containerized workflows on AWS EC2 without data egress costs
Google Earth Engine (GEE) Google / Alphabet Free for verified academic research; commercial licensing for enterprise JavaScript Code Editor, Python API, REST catalog Rapid multi-temporal analysis and planetary-scale cloud processing; pre-processed surface reflectance and cloud-masked mosaics
Microsoft Planetary Computer Microsoft Corporation Free open access; Azure compute sponsorship available STAC API, Azure Blob Storage, Planetary Computer Hub (Jupyter) Cloud-native geospatial analytics; seamless integration with Python Xarray, Dask, and Pangeo scientific stacks on Azure

Researchers conducting transatlantic cross-sensor studies frequently combine Sentinel observations with Landsat and MODIS data hosted on the NASA Earthdata system, utilizing standardized STAC metadata models to execute harmonized multi-satellite time-series analysis.

For detailed mission specifications, payload configurations, and catalog collection identifiers across all Sentinel constellations, consult the structured data table below.

Frequently asked questions

Is the Copernicus Open Access Hub still active?

No. The Copernicus Open Access Hub officially ceased all operational services and was permanently shut down on October 31, 2023. User registration, legacy GUI browsing, and direct API endpoints hosted on scihub.copernicus.eu have been completely deactivated by the European Space Agency.

What replaced the Copernicus Open Access Hub?

The Copernicus Open Access Hub was superseded by the Copernicus Data Space Ecosystem (CDSE), accessible at dataspace.copernicus.eu. CDSE serves as the unified European cloud platform for searching, visualizing, and downloading Copernicus Sentinel data, offering modernized OData and STAC APIs alongside integrated cloud computing environments.

How do researchers migrate legacy sentinelsat and SciHub scripts?

Researchers must update their programmatic workflows to use CDSE endpoints. This involves replacing HTTP Basic Authentication with Keycloak OAuth 2.0 / OpenID Connect Bearer tokens from identity.dataspace.copernicus.eu, migrating OpenSearch queries to OData v4 or STAC v1 catalog search APIs, and utilizing modern client libraries such as the CDSE Python SDK or pystac-client.

Is Copernicus satellite data still free for academic research?

Yes. In accordance with the European Union’s open data policy, all Copernicus Sentinel satellite observations remain free, full, and open to researchers, commercial developers, and the global public. Users must create a free account on the Copernicus Data Space Ecosystem to access data downloads and API endpoints.

What happened to the rolling archive delays for older Sentinel data?

Under the legacy Open Access Hub, historical Sentinel granules older than 6 to 12 months were relegated to offline tape storage, requiring asynchronous retrieval requests that took hours to complete. The Copernicus Data Space Ecosystem resolved this limitation by storing the entire historical Sentinel archive online in cloud object storage, enabling immediate, un-delayed access to all acquisitions since 2014.

Sources

Data: Copernicus Sentinel Missions and Data Specifications

Technical specifications, sensor payloads, spatial resolutions, temporal revisit cycles, standard data products, and catalog collection identifiers for Copernicus Sentinel satellite missions available through the Copernicus Data Space Ecosystem, compiled from European Space Agency and Copernicus Programme documentation.

Period covered: 2014-2026. Coverage: Global.

Copernicus Sentinel Missions and Data Specifications
Mission and ConstellationSensor PayloadObservation TypeSpatial Resolution (meters)Revisit Time (days)Standard Data ProductsCDSE Collection ID
Sentinel-1 (1A, 1C)C-SAR (Synthetic Aperture Radar)Radar active microwave (C-band, 5.405 GHz)56Level-1 GRD, Level-1 SLC, Level-2 OCNSENTINEL-1
Sentinel-2 (2A, 2B, 2C)MSI (MultiSpectral Instrument)Optical passive multispectral (13 spectral bands)105Level-1C TOA reflectance, Level-2A BOA reflectanceSENTINEL-2
Sentinel-3 (3A, 3B)OLCI, SLSTR, SRAL, MWROptical ocean/land colour, surface temperature, altimetry3002Level-1B radiance, Level-2 land/marine water qualitySENTINEL-3
Sentinel-5PTROPOMI (Tropospheric Monitoring Instrument)Atmospheric spectrometer (UV-VIS-NIR-SWIR)35001Level-2 trace gases (NO2, O3, SO2, CH4, CO, aerosols)SENTINEL-5P

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · full access

Ask about Copernicus Open Access Hub: Sentinel Data and Migration Guide

Full access: large monthly usage, up to 10 source passages behind each answer, and MCP and API access for Claude Code, Codex and other CLIs. Cancel any time.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →