-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gdalinfo on Sentinel-2 SAFE archive does not return all rasters matching SUBDATASET_4_NAME=SENTINEL2_L2A:...:TCI #9066
Comments
Do you mean that there should be different subdatasets for each resolution?
|
Yes, or every available resolution in one subset if possible. As it stands, the user does not receive information about the two existing rasters (TCI_20m and TCI_60m) at all. |
Have you tried to study the metadata xml files? I am trying but this is the first time ever with such files for me. I guess that TCI is defined somehow differently than for example bands Bands B2, B3, B4, B8 which are collected into a multiband layers sharing the same resolution. Do you know that the XML files are correct and some other software can read the 10m, 20m, and 60m TCI bands separately? |
I think that I will give up now. The main XML document refers to XML schema https://psd-14.sentinel2.eo.esa.int/PSD/User_Product_Level-2A.xsd but it is not there anymore. Probably the schema is now somewhere here https://sentinel.esa.int/web/sentinel/user-guides/sentinel-2-msi/data-formats/xsd but I believe that I would not really understand it anyway. |
From what I know, these are the official XML files provided by ESA. I am not familiar with other metadata tools that extracts S2L2A information. I was looking for a way to transmit S2 metadata to STAC, and that's how I came up this ticket. This is nice metadata tool, but it's necessary to write the rule for S2L2A. You can find more information here: https://github.com/dlr-eoc/EOmetadataTool/tree/main The content of MTD_MSIL2A.xml shows that the different resolutions TCI files are clearly listed here: From what I understand, the difference between TCIs and other rasters is that TCIs are 3-band rasters, while others are panchromatic-based. There is no difference between (for example) SLC and TCI from the xml definition perspective |
The TCI files are listed but in the same way for example B2 files are listed and I did not find what makes them grouped with bands B3, B4, and B8 into 10m resolution subdataset. There must be some additional information somewhere. |
For me it seems that the driver works as it is made to work. I think I will close this issue because there is no bug involved. Please write to gdal-dev mailing list and make a reasoned suggestion about how to improve the driver and open a discussion. |
Mostly documentation adjustments in #9067 . Sentinel2 is a bit messy due to the various levels L1B/L1C/L2A and the different "formulations" of it within the same level (original formuation, "safe_compact"...) |
Expected behavior and actual behavior.
After running
on Sentinel-2 product metadata file, among output a subset information is returned:
What is weird in my personal option is that the TCI (pre-processed true color composition) is defined as separate subset. After running gdalinfo on the TCI subset, only metadata for 10m resolution is returned, despite existence of 2 other resolution files.
Information about all available resolutions should be returned or the TCI composition metadata should be captured in corresponding resolution subset.
Steps to reproduce the problem.
sample data:
https://s3.waw3-2.cloudferro.com/swift/v1/Tomkralidis/
Operating system and GDAL version
The text was updated successfully, but these errors were encountered: