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

Support multi-band "from" images in map2cam #5501

Open
rvwagner opened this issue May 17, 2024 · 2 comments
Open

Support multi-band "from" images in map2cam #5501

rvwagner opened this issue May 17, 2024 · 2 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@rvwagner
Copy link

Description
When using map2cam, currently if you specify a multiband image as the "from" image, only band 1 gets reprojected to match the "match" image. I have a couple of projects where it would be useful if all of the "from" image bands were reprojected, creating a multi-band output image (currently I'm looping over all bands of the "from" image, running map2cam for each, and then cubeiting them together again, but making sure I keep the band ordering the same is a hassle). I have the same need to get proper areal statistics in camera space as in #3856.

A potential complication I could see is that if the from and match images both have the same >1 number of bands, the user expectation might be that map2cam would pair them up, projecting from+1 to match+1, from+2 to match+2, etc. Currently, it appears that if you provide two multi-band images, map2cam only projects from.cub+1 to match match.cub+1, and all other bands in both files are ignored, so any multiband support would be brand new behavior with no existing usage to support.

@rvwagner rvwagner added the enhancement New feature or request label May 17, 2024
@chkim-usgs chkim-usgs added the good first issue Good for newcomers label Jul 8, 2024
Copy link

github-actions bot commented Jan 5, 2025

Thank you for your contribution!

Unfortunately, this issue hasn't received much attention lately, so it is labeled as 'stale.'

If no additional action is taken, this issue will be automatically closed in 180 days.

If you want to participate in our support prioritization meetings or be notified when support sprints are happening, you can sign up the support sprint notification emails here.

Read more about our support processs here

@github-actions github-actions bot added the inactive Issue that has been inactive for at least 6 months label Jan 5, 2025
@Kelvinrr
Copy link
Collaborator

Kelvinrr commented Jan 6, 2025

Gonna bump this, I think in the past it hasn't been worked on because it has a workaround but seems like a good feature to have.

@github-actions github-actions bot removed the inactive Issue that has been inactive for at least 6 months label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
Status: No status
Development

No branches or pull requests

3 participants