You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've observed significant differences in pixel values between Element84's Sentinel-2 L2A Cloud-Optimized GeoTIFFs and other distributions of the same scenes, specifically:
Microsoft Planetary Computer's Sentinel-2 L2A
Original JP2K files from AWS Sentinel-2 registry (s3://sentinel-s2-l2a)
Observation Details:
The cloud masks and general scene geometries match perfectly at pixel level, confirming the source data is identical
However, raster histogram analysis in QGIS shows different pixel value distributions
Notably, the original JP2K files in AWS (eu-central-1) match with Microsoft Planetary Computer's distribution
The discrepancy appears to be specific to the COG versions
Verification Steps:
Compared identical scenes across all three sources
Used QGIS raster histogram analysis to verify pixel value distributions
Confirmed that cloud geometries match at pixel level
Verified that original JP2K assets show consistent values with Microsoft PC
Questions:
Are there any known processing steps during COG conversion that might explain these differences?
Could there be any parameters in the COG conversion pipeline that might be affecting the pixel values?
Is this a known issue or expected behavior?
We want to ensure we're not missing anything in our analysis before proceeding with using these datasets.
Description:
We've observed significant differences in pixel values between Element84's Sentinel-2 L2A Cloud-Optimized GeoTIFFs and other distributions of the same scenes, specifically:
Observation Details:
Verification Steps:
Questions:
We want to ensure we're not missing anything in our analysis before proceeding with using these datasets.
Technical Details:
The text was updated successfully, but these errors were encountered: