MicaSense Altum panel reflectance calculation problem

tegeint

Dear Community,

I have ecountered a problem while adding MicaSense Altum multispectral imagery to ArcGIS Pro. When calculating panel reflectance values, the NearInfrared band would require a filename ending with _4.tif, while the NIR band images end with _5 (_4 is RedEdge).

Has anybody faced this problem? Is there any soultion or other approach to define panel reflectance values?

Thanks,
Márton

altum_bands.jpg

arcgispro_reflectance_band_mismatch.jpg

nir-rededge_altum.jpg

HenryUnderwood1_0-1743173418597.png

CaptureGIS.JPG

octopusEA8_.png

PatrickMaple

You're running into a band indexing mismatch between ArcGIS Pro expectations and the MicaSense Altum band order.

In Altum datasets, the bands are typically ordered as:

• Blue
• Green
• Red
• RedEdge (_4)
• NIR (_5)

However, some ArcGIS workflows (especially reflectance panel tools) may assume a different band mapping, where NIR is expected in position 4.

What you can do:

• First, verify how your raster is being interpreted in ArcGIS (check band order in layer properties).
• If the bands are misaligned, you can manually reorder them using the Composite Bands tool to match the expected input.
• Alternatively, rename or remap bands during preprocessing so that NIR aligns with the required index.
• Also, ensure your panel calibration images are correctly matched with the same band structure as your flight imagery.

In many UAV multispectral workflows, handling band order before importing into ArcGIS helps avoid issues with reflectance calculations.