<?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 Re: Multidimensional Trend: Time unit used in nedcdf files in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/multidimensional-trend-time-unit-used-in-nedcdf/m-p/1134704#M50150</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Solved using "trend" in CDO&lt;/STRONG&gt; (&lt;A href="https://code.mpimet.mpg.de/projects/cdo)" target="_blank" rel="noopener"&gt;https://code.mpimet.mpg.de/projects/cdo)&lt;/A&gt;. Gives reasonable value in line with "manual" calculations. Even if multidimensional tools are nice and very computational effective (which CDO is as well) I find it tricky to keep track of time settings etc. And why can't TREND take normal multiband rasters files as input? The ARCMAP tool Curvefit (&lt;A href="https://www.umesc.usgs.gov/management/dss/curve_fit.html)" target="_blank"&gt;https://www.umesc.usgs.gov/management/dss/curve_fit.html)&lt;/A&gt; is excellent but slow for big data sets, the data set below ( &lt;FONT face="courier new,courier"&gt;SUBDATASET_1_DESC=[20x19070x18091] Npp_500m (16-bit integer)&lt;/FONT&gt; ) took a about 3 minutes to calculate the trend (gain, offset) with either CDO&amp;nbsp; "Trend" or ARCGIS Pro "Multidimensional Trend", using the *.nc file as direct input. Interesting pattern in east Congo?&lt;/P&gt;&lt;P&gt;/Jonas Ardö&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Trend.png" style="width: 583px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/31736i15FCF88A962EFAD2/image-dimensions/583x821?v=v2" width="583" height="821" role="button" title="Trend.png" alt="Trend.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jan 2022 19:23:19 GMT</pubDate>
    <dc:creator>jonasardo</dc:creator>
    <dc:date>2022-01-18T19:23:19Z</dc:date>
    <item>
      <title>Multidimensional Trend: Time unit used in nedcdf files</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/multidimensional-trend-time-unit-used-in-nedcdf/m-p/1134435#M50112</link>
      <description>&lt;P&gt;Using ArcGIS Pro 2.9.1 on windows 10 I imported a netcdf file to a Multidimensional Raster Layer. The data is a time series with one data set per year for 20 years (2001-2020). The original time dimension in the netcdf file is days&amp;nbsp; When I calculate the trend using ArcGIS Pro (Multidimensional Trend) I get very small values and I suspect that Multidimensional Trend uses days instead of year as time unit. How can I correct that?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Details in attached PDF, data attached.&lt;/P&gt;&lt;P&gt;Any suggestion appreciated&lt;/P&gt;&lt;P&gt;/Jonas Ardö&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 07:00:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/multidimensional-trend-time-unit-used-in-nedcdf/m-p/1134435#M50112</guid>
      <dc:creator>jonasardo</dc:creator>
      <dc:date>2022-01-18T07:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: Multidimensional Trend: Time unit used in nedcdf files</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/multidimensional-trend-time-unit-used-in-nedcdf/m-p/1134704#M50150</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Solved using "trend" in CDO&lt;/STRONG&gt; (&lt;A href="https://code.mpimet.mpg.de/projects/cdo)" target="_blank" rel="noopener"&gt;https://code.mpimet.mpg.de/projects/cdo)&lt;/A&gt;. Gives reasonable value in line with "manual" calculations. Even if multidimensional tools are nice and very computational effective (which CDO is as well) I find it tricky to keep track of time settings etc. And why can't TREND take normal multiband rasters files as input? The ARCMAP tool Curvefit (&lt;A href="https://www.umesc.usgs.gov/management/dss/curve_fit.html)" target="_blank"&gt;https://www.umesc.usgs.gov/management/dss/curve_fit.html)&lt;/A&gt; is excellent but slow for big data sets, the data set below ( &lt;FONT face="courier new,courier"&gt;SUBDATASET_1_DESC=[20x19070x18091] Npp_500m (16-bit integer)&lt;/FONT&gt; ) took a about 3 minutes to calculate the trend (gain, offset) with either CDO&amp;nbsp; "Trend" or ARCGIS Pro "Multidimensional Trend", using the *.nc file as direct input. Interesting pattern in east Congo?&lt;/P&gt;&lt;P&gt;/Jonas Ardö&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Trend.png" style="width: 583px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/31736i15FCF88A962EFAD2/image-dimensions/583x821?v=v2" width="583" height="821" role="button" title="Trend.png" alt="Trend.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jan 2022 19:23:19 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/multidimensional-trend-time-unit-used-in-nedcdf/m-p/1134704#M50150</guid>
      <dc:creator>jonasardo</dc:creator>
      <dc:date>2022-01-18T19:23:19Z</dc:date>
    </item>
  </channel>
</rss>

