<?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 NetCDF time units for seconds in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/netcdf-time-units-for-seconds/m-p/1339675#M74177</link>
    <description>&lt;P&gt;Hi - I'm using ArcGIS to inspect a NetCDF we've created that represents a multidimensional raster created from fused lidar data.&amp;nbsp; Each time slice is one second.&lt;/P&gt;&lt;P&gt;When we load it into ArcGIS Pro, the time isn't picked up correctly.&amp;nbsp; In this &lt;A href="https://drive.google.com/file/d/1ye8czZO-cJqfCtLFfD-cg4FRkxSGiAg-/view?usp=sharing" target="_self"&gt;sample dataset&lt;/A&gt;&amp;nbsp;there are 60 time slices, each a second starting at 2023-04-10 12:35:00.&amp;nbsp; When it gets loaded into ArcGIS Pro (Add Data -&amp;gt; Multidimensional Raster Layer), the time defaults to 2023-04-01 at 12:35am (00:35:00).&lt;/P&gt;&lt;P&gt;I've tracked this down to how the time.units string is formatted.&amp;nbsp; When the string is formatted by xarray as we write it, it looks like this:&lt;/P&gt;&lt;P&gt;Variable attribute value: seconds since 2023-04-10T12:00:00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I force it to remove the "T" (see &lt;A href="https://drive.google.com/file/d/1PDZs4LA-IdX8BNvH_oWq9F6WaCh1n3l9/view?usp=sharing" target="_self"&gt;attached revised file&lt;/A&gt;), ArcGIS Pro picks it up normally / as expected:&lt;/P&gt;&lt;P&gt;Variable attribute value: seconds since 2023-04-10 12:00:00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As far as I can tell, though, the use of the "T" &lt;A href="https://en.wikipedia.org/wiki/ISO_8601" target="_self"&gt;is standard with ISO 8601&lt;/A&gt;.&amp;nbsp; I can force the unit change and fix the problem on my NetCDFs, but I wonder if this isn't undesirable behavior on the ArcGIS side that should be patched.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 19 Oct 2023 16:57:09 GMT</pubDate>
    <dc:creator>ThomasPingel1</dc:creator>
    <dc:date>2023-10-19T16:57:09Z</dc:date>
    <item>
      <title>NetCDF time units for seconds</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/netcdf-time-units-for-seconds/m-p/1339675#M74177</link>
      <description>&lt;P&gt;Hi - I'm using ArcGIS to inspect a NetCDF we've created that represents a multidimensional raster created from fused lidar data.&amp;nbsp; Each time slice is one second.&lt;/P&gt;&lt;P&gt;When we load it into ArcGIS Pro, the time isn't picked up correctly.&amp;nbsp; In this &lt;A href="https://drive.google.com/file/d/1ye8czZO-cJqfCtLFfD-cg4FRkxSGiAg-/view?usp=sharing" target="_self"&gt;sample dataset&lt;/A&gt;&amp;nbsp;there are 60 time slices, each a second starting at 2023-04-10 12:35:00.&amp;nbsp; When it gets loaded into ArcGIS Pro (Add Data -&amp;gt; Multidimensional Raster Layer), the time defaults to 2023-04-01 at 12:35am (00:35:00).&lt;/P&gt;&lt;P&gt;I've tracked this down to how the time.units string is formatted.&amp;nbsp; When the string is formatted by xarray as we write it, it looks like this:&lt;/P&gt;&lt;P&gt;Variable attribute value: seconds since 2023-04-10T12:00:00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When I force it to remove the "T" (see &lt;A href="https://drive.google.com/file/d/1PDZs4LA-IdX8BNvH_oWq9F6WaCh1n3l9/view?usp=sharing" target="_self"&gt;attached revised file&lt;/A&gt;), ArcGIS Pro picks it up normally / as expected:&lt;/P&gt;&lt;P&gt;Variable attribute value: seconds since 2023-04-10 12:00:00&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As far as I can tell, though, the use of the "T" &lt;A href="https://en.wikipedia.org/wiki/ISO_8601" target="_self"&gt;is standard with ISO 8601&lt;/A&gt;.&amp;nbsp; I can force the unit change and fix the problem on my NetCDFs, but I wonder if this isn't undesirable behavior on the ArcGIS side that should be patched.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 16:57:09 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/netcdf-time-units-for-seconds/m-p/1339675#M74177</guid>
      <dc:creator>ThomasPingel1</dc:creator>
      <dc:date>2023-10-19T16:57:09Z</dc:date>
    </item>
  </channel>
</rss>

