<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic MicaSense Altum panel reflectance calculation problem in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/micasense-altum-panel-reflectance-calculation/m-p/1676274#M101063</link>
    <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;Has anybody faced this problem? Is there any soultion or other approach to define panel reflectance values?&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Márton&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jan 2026 10:13:54 GMT</pubDate>
    <dc:creator>tegeint</dc:creator>
    <dc:date>2026-01-07T10:13:54Z</dc:date>
    <item>
      <title>MicaSense Altum panel reflectance calculation problem</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/micasense-altum-panel-reflectance-calculation/m-p/1676274#M101063</link>
      <description>&lt;P&gt;Dear Community,&lt;/P&gt;&lt;P&gt;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).&lt;/P&gt;&lt;P&gt;Has anybody faced this problem? Is there any soultion or other approach to define panel reflectance values?&lt;/P&gt;&lt;P&gt;Thanks,&lt;BR /&gt;Márton&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 10:13:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/micasense-altum-panel-reflectance-calculation/m-p/1676274#M101063</guid>
      <dc:creator>tegeint</dc:creator>
      <dc:date>2026-01-07T10:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: MicaSense Altum panel reflectance calculation problem</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/micasense-altum-panel-reflectance-calculation/m-p/1696126#M102773</link>
      <description>&lt;P&gt;You're running into a band indexing mismatch between ArcGIS Pro expectations and the MicaSense Altum band order.&lt;/P&gt;&lt;P&gt;In Altum datasets, the bands are typically ordered as:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Blue&lt;/LI&gt;&lt;LI&gt;Green&lt;/LI&gt;&lt;LI&gt;Red&lt;/LI&gt;&lt;LI&gt;RedEdge (_4)&lt;/LI&gt;&lt;LI&gt;NIR (_5)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;However, some ArcGIS workflows (especially reflectance panel tools) may assume a different band mapping, where NIR is expected in position 4.&lt;/P&gt;&lt;P&gt;What you can do:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;First, verify how your raster is being interpreted in ArcGIS (check band order in layer properties).&lt;/LI&gt;&lt;LI&gt;If the bands are misaligned, you can manually reorder them using the &lt;STRONG&gt;Composite Bands&lt;/STRONG&gt; tool to match the expected input.&lt;/LI&gt;&lt;LI&gt;Alternatively, rename or remap bands during preprocessing so that NIR aligns with the required index.&lt;/LI&gt;&lt;LI&gt;Also, ensure your panel calibration images are correctly matched with the same band structure as your flight imagery.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In many UAV multispectral workflows, handling band order before importing into ArcGIS helps avoid issues with reflectance calculations.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Apr 2026 14:37:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/micasense-altum-panel-reflectance-calculation/m-p/1696126#M102773</guid>
      <dc:creator>PatrickMaple</dc:creator>
      <dc:date>2026-04-14T14:37:35Z</dc:date>
    </item>
  </channel>
</rss>

