Sentinel-2 georeference error/offset

Bugs & Features
1

Hello,
in downloading Sentinel-2 images from Sentinel Hub I’ve found many cases of coordinates offset in between different images. The issue is present also from images belonging to the same track and satellite.
Do you have any ideas about the source and any possible action to solve it?
Thanks.

These are two SH queries providing such kind of data:

product:
type: SENTINEL2_L1C

query:
start_date: 2019-06-03
end_date: 2019-09-22
cloud_cover: 100
resolution: 10
area:
zone: UTM_32N
x_min: 678000
x_max: 685000
y_min: 4870000
y_max: 4876000

evalscript: evalscripts/many_bands.js

output:
dir: /mnt/backup/sat_store/
prefix: Bilancino
encoding:
SENTINEL2_L1C:
dtype: uint16
scale_factor: 0.001
CLP:
dtype: uint8
scale_factor:

–

product:
type: SENTINEL2_L1C

query:
start_date: 2021-02-15
end_date: 2021-04-29
cloud_cover: 100
resolution: 10
area:
zone: UTM_32N
x_min: 649000
x_max: 651000
y_min: 5062000
y_max: 5063500

evalscript: evalscripts/many_bands.js

output:
dir: /mnt/backup/sat_store/
prefix: Adige
encoding:
SENTINEL2_L1C:
dtype: uint16
scale_factor: 0.001
CLP:
dtype: uint8
scale_factor: 1

2

Note that Sentinel-2 (as well as other satellite missions) does not have perfect geolocation accuracy.
I suggest to check this blog-post from Cesbio, which nicely describes the problem:
https://labo.obs-mip.fr/multitemp/a-bit-of-bad-news-regarding-sentinel-2-multi-temporal-registration/

You can use coregistration methods, e.g. one from our eo-learn:

3

Hi Grega,
thank you for your quick reply.
I’ll check your coregistration tool.

4

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.