Skip to content
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

Detecting and Labeling Bands in High-Resolution Sentinel-2 Spectral Extension Output #210

Open
click2cloud-tejas opened this issue Nov 28, 2024 · 0 comments
Labels
question Information requested from user triage Issues still not triaged by team workflows Issues encountered when running workflows

Comments

@click2cloud-tejas
Copy link

Topic

Workflow

Ask away!

After successfully running a spectral extension workflow, I obtained the following outputs:

1.s2_rasters: The original Sentinel-2 product used in the workflow.
2.matched_raster: The Sentinel-2 product resampled to match the grid of the UAV image.
3.extended_raster: A GeoTIFF file containing 8 Sentinel-2 bands at high resolution.

Upon accessing the extended_raster, I confirmed it contains 8 bands, which represent certain values. However, the metadata in the GeoTIFF file does not provide names for the bands, making it unclear which band corresponds to which Sentinel-2 spectral band (e.g., B1, B2, B3, etc.).

Questions:
1)Do the values in the extended_raster represent reflectance values for each band?
2)How can I detect which values correspond to specific Sentinel-2 bands, given the lack of metadata?

The Metadata extracted from the extended_raster file
Image

The values at all Latitude Longitude from the extended_raster geotiff file
Image

@click2cloud-tejas click2cloud-tejas added the question Information requested from user label Nov 28, 2024
@github-actions github-actions bot added triage Issues still not triaged by team workflows Issues encountered when running workflows labels Nov 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Information requested from user triage Issues still not triaged by team workflows Issues encountered when running workflows
Projects
None yet
Development

No branches or pull requests

1 participant