So you could not use the Image Analysis window, mosaic dataset or tool to process this? The workflow expects multiple bands and having the RPCs per band should not be a problem. I would try the image analysis window or mosaic dataset. You probably should not have had to process each band and if you did, then I think that Support would like to see the data to pass it to development.
The software should be able to recognized the scene normally and then apply the geometric function to the whole scene.
Jeff,
as you can see from the function chain pic attached, I was using the image analysis window.
As I see it, because you get an "rpc" file per band, you have to do the ortho rectify on each band first then pass that on the composite / pansharp function afterwards.
I have found that doing everything, all together in a mosaic is not always (well, lets be honest, never) the best way.
Generally I do all the messing about using the image analysis workflow. Then export out the final version into a fgdb, then mosaic the various scenes.
N
I see that pic now, I apologize, I am still sorting out the GeoNet-ness and missed it initially. I do not think you should have to do it that way. I think the design is to use a chain like Composite Bands > Geometric > Pansharpened (it would tier in the chain so you would only have to do it once rather than for each band) and only use it once. I would think that Development would like to know if you are having to jump through such hoops. After all this is just one scene, the if you applied the functions in a mosaic dataset, then this might be problematic unless you applied the chain during the import of the scenes to the mosaic dataset. To get to Development, a call to Support might be in order. However if you are fine with your workflow, then I suppose it is not necessary. I see this as a potential bug in the software, not simply a workaround given your data.
Thanks for sharing.