Dear Guido,
As previously written, the anomaly impacting R079_V20160403T095406_20160403T095406 (T33UXP) and more generally the whole orbit A4080, R079, is still under investigation. Note that another orbit is impacted by a similar behaviour that is A3218, R075.
The associated products should have been removed from SciHub.
Regards
Olivier
Dear bnnd,
Do you observe the same shift in both versions of the same product reprocessed with 2 versions of the instrument processing facility?
Thank you for having spotted that.
Regards
Olivier
Sorry, I did not pay attention to your comment:“Another image, like the more recent
S2A_OPER_MSI_L1C_TL_SGS__20160205T174515_A003251_T31TGL_B04, is
correctly georeferenced (sorry, being new, I cannot insert more than 1
image).”
It means that there is still an older version of the same product available somewhere, should be removed to my opinion… From where did you get them? SciHub? Another portal?
Please let me know.
Thanks and regards
Olivier
Hi
Acquisition 2015-08-12
S2A_OPER_PRD_MSIL1C_PDMC_20160414T041739_R008_V20150812T104021_20150812T104021.SAFE was downloaded by a colleague a few month ago (2016-04-22 ?), I think it was from Scihub and it is shifted.
This former version is not available on scihub anymore : the file available is now S2A_OPER_PRD_MSIL1C_PDMC_20160514T102847_R008_V20150812T104021_20150812T104021 (from https://scihub.copernicus.eu/s2/odata/v1/Products(‘2e5d14c5-0e66-4847-9e17-838698f2c967’)/$value) and is fine.
The bands of the same new version (the metadata say the name is also S2A_OPER_PRD_MSIL1C_PDMC_20160514T102847_R008_V20150812T104021_20150812T104021) at http://sentinel-s2-l1c.s3-website.eu-central-1.amazonaws.com/#tiles/31/T/GL/2015/8/12/1/ seem to be correctly georeferenced (I didn’t try all of them).
Acquisition 2016-02-05
S2A_OPER_PRD_MSIL1C_PDMC_20160210T111540_R108_V20160205T103556_20160205T103556.SAFE downloaded from scihub (on 2016-05-11) was correctly georeferenced.
Cordially
Dear bnnd,
Thanks a lot for these elements.
Regards,
Olivier
Dear Rea,
Sorry to reply so late to your post.
I can see that the products you wanted to mosaic were not from the same relative orbit (50 and 93), which means that the geometric conditions are not similar.
Moreover, a slight yaw drift existed within the swath that as been corrected end of May.
You can find a list of known anomalies in the Data Quality Report with the following link:
https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-2/data-quality-report
Regards,
Olivier
Hi
If it helps to someone: tile 33SVC from 2016-04-03 affected by the shift. I guess included in orbit A4080, R079 as Olivier explains.
Single version, not fixed version:
http://sentinel-s2-l1c.s3-website.eu-central-1.amazonaws.com/#tiles/33/S/VC/2016/4/3/
The shift is light enough to align images and use the overlap between tiles to avoid the problem.
Thanks to provide this data and resources to use it.
Thanks and regards,
Tomàs A.