Different processing baseline between Sentinel Hub API and Copernicus Browser

Apps / Services
1

Hello,

When I hit the Sentinel Hub API for historic imagery I get a tile ID that is different from the tile ID in Copernicus Browser. The Product Discriminator id is older when from the Sentinel Hub API and the processing baseline number is different. For example:
Sentinel Hub: S2B_MSIL2A_20190815T174919_N0213_R141_T14ULB_20190815T223249
Copernicus:
S2B_MSIL2A_20190815T174919_N0500_R141_T14ULB_20230724T002706.SAFE

It seems like the newer processed version of the tile is not available through the Sentinel Hub API, is this true? I believe this issue is related to Differences between data downloaded from Sentinel Hub and data obtained from the Copernicus Data Space ecosystem using Sentinel Hub APIs - #6 by gabogef161
Is there a timeline for when the newest processed imagery will be available in the Sentinel Hub infrastructure? Thanks!

2

Sentinel-2 data were recently massively reprocessed. Sentinel Hub does not yet have a full archive. We are working on this, but timeline is not yet set.
Please note that you can use Sentinel Hub also as a part of Copernicus Data Space Ecosystem.

3

Thank you for letting me know.
Can you elaborate on using Sentinel Hub in the CDS Ecosystem?

4

Sentinel Hub is operating within CDSE, with same feature set:
https://documentation.dataspace.copernicus.eu/APIs/SentinelHub.html

You will need to create a new account there, but this takes less than a minute. Account gives permanently free access, up to fair use limits.
In case you have a commercial Sentinel Hub subscription, you can use it wither with sentinel-hub.com or CDSE.

5

Thank you for the information