<?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: Pandas and DateTimes in Pro 3.2 in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1384448#M69921</link>
    <description>&lt;P&gt;There were changes to Pandas, perhaps this might provide some extra information&lt;/P&gt;&lt;P&gt;&lt;A href="https://developers.arcgis.com/python/guide/part5-time-series-analysis-with-pandas/" target="_blank"&gt;Part 5 - Working with Time Series Data | ArcGIS API for Python&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 20 Feb 2024 17:00:28 GMT</pubDate>
    <dc:creator>DanPatterson</dc:creator>
    <dc:date>2024-02-20T17:00:28Z</dc:date>
    <item>
      <title>Pandas and DateTimes in Pro 3.2</title>
      <link>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1384429#M69920</link>
      <description>&lt;P&gt;I have a workflow scripted in which I export a Pandas dataframe to a geodatabase table using the method:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;df.spatial.to_table(out_table_path)&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After upgrading Pro to 3.2, I noticed that my script changed how it was handling dates.&amp;nbsp; After a little digging, I found that my dataframe fields with a datetime64[s] data type were casting to the new ESRI 'Time Only' field during the conversion to a geodatabase table, despite containing both dates and times.&amp;nbsp; This is obviously a deviation from the behavior in older versions of Pro, which had only a single type of field for handling date times.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;My Question:&lt;/STRONG&gt; Is this the expected behavior, or a bug?&amp;nbsp; Anyone else having problems?&amp;nbsp; I haven't been able to find good documentation on how the new ESRI date time field types work with the arcgis.features module.&amp;nbsp; I did find, via some trial-and-error, that I could get what I needed by forcing my pandas field datatype to datetime64[ns] prior to export, but this doesn't feel like it should be necessary and is far higher resolution than what I need for my data.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;JF&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 16:32:31 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1384429#M69920</guid>
      <dc:creator>JoshuaFlickinger</dc:creator>
      <dc:date>2024-02-20T16:32:31Z</dc:date>
    </item>
    <item>
      <title>Re: Pandas and DateTimes in Pro 3.2</title>
      <link>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1384448#M69921</link>
      <description>&lt;P&gt;There were changes to Pandas, perhaps this might provide some extra information&lt;/P&gt;&lt;P&gt;&lt;A href="https://developers.arcgis.com/python/guide/part5-time-series-analysis-with-pandas/" target="_blank"&gt;Part 5 - Working with Time Series Data | ArcGIS API for Python&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Feb 2024 17:00:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1384448#M69921</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2024-02-20T17:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: Pandas and DateTimes in Pro 3.2</title>
      <link>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1385337#M69930</link>
      <description>&lt;P&gt;I have found other problems with 64 bit Integers now called BigInteger. Integer fields defined in geopackages and spatialite are now cast by default to BigInteger instead of Integer.&amp;nbsp; RelationshipClasses cannot use them which was a surprise because I suddenly had BigIntegers for every primary and foreign key in my database.&lt;/P&gt;&lt;P&gt;I have had to go back and explicitly cast to Integer (32 bit) using FieldMapping on every copy operation so I am not surprised that Pandas needs editing. Just about to do some datetime manipulation, thanks for the heads-up.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Feb 2024 09:42:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/pandas-and-datetimes-in-pro-3-2/m-p/1385337#M69930</guid>
      <dc:creator>KimOllivier</dc:creator>
      <dc:date>2024-02-22T09:42:57Z</dc:date>
    </item>
  </channel>
</rss>

