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
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: