<?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: ArcPy Data Access Support for numpy.datetime64 and Python datetime in Python Questions</title>
    <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636853#M49596</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apart from waiting for 10.4 does anyone have suggestions for dealing with dates not coming across from a numpy array to a table?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 18 Jun 2015 21:35:01 GMT</pubDate>
    <dc:creator>LorneDmitruk</dc:creator>
    <dc:date>2015-06-18T21:35:01Z</dc:date>
    <item>
      <title>ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636848#M49591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Recent questions/discussions on GeoNet got me thinking about an ArcPy Data Access module limitation I hadn't thought about in a while, specifically the lack of date and time support when working with NumPy arrays.&amp;nbsp; Given where date and time support in NumPy was in 2012 when Esri introduced the ArcPy Data Access module, I can understand why support was missing then, but I think the time is right for them to start supporting it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I went ahead and created the suggestion on the ArcGIS Ideas site:&amp;nbsp; &lt;A href="http://ideas.arcgis.com/ideaView?id=087E0000000CxERIA0"&gt;ArcPy Data Access Support for numpy.datetime64 and Python datetime&lt;/A&gt;.&amp;nbsp; I also logged an enhancement request with Esri Support:&amp;nbsp; &lt;SPAN style="font-family: tahoma,arial,helvetica,sans-serif;"&gt;&lt;SPAN style="color: #3334ca;"&gt;ENH-000086993: Update the ArcPy Data Access module to include support for numpy.datetime64 and Python datetime&lt;/SPAN&gt;.&lt;/SPAN&gt;&amp;nbsp; If you would like to see date and time support for the NumPy-related methods in the ArcPy Data Access module, I encourage you to go promote the idea on ArcGIS Ideas and submit your own use case to Esri Support to have your customer number attached the aforementioned enhancement request.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2015 21:44:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636848#M49591</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2015-04-16T21:44:52Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636849#M49592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Done...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2015 21:55:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636849#M49592</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2015-04-16T21:55:52Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636850#M49593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just to reiterate what David Wynne mentioned on the idea, this is fixed in Pro 1.1, and will likely also be included for Desktop 10.4. I agree it's a great feature to have, so that the NumPy array can serve as the common intermediate format for tabular data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;BR /&gt;Shaun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2015 00:53:23 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636850#M49593</guid>
      <dc:creator>ShaunWalbridge</dc:creator>
      <dc:date>2015-04-17T00:53:23Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636851#M49594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/31672"&gt;Shaun Walbridge&lt;/A&gt;​, good news, indeed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With Pro having its own numbering/versioning scheme, separate from ArcGIS Desktop, it gets a bit confusing in terms of what will be released when.&amp;nbsp; Outside of ArcGIS 10.3.1 being released shortly, is release information for ArcGIS Desktop 10.3.2, ArcGIS 10.4, and ArcGIS Pro 1.1 publicly documented anywhere?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2015 01:48:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636851#M49594</guid>
      <dc:creator>JoshuaBixby</dc:creator>
      <dc:date>2015-04-17T01:48:15Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636852#M49595</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We announce specific dates for releases that are close to release (like 10.3.1 as you mentioned). For Pro, the releases aren't tied directly to the rest of the ArcGIS release, but generally you should see a Pro release complimentary to each broader release. Note that Pro has an improved mechanism for updating which means that upgrades are more seamless and will likely require less planning around. Pro 1.1 will release in the coming months, and 10.4 and Pro 1.2 will also likely ship in 2015, based on &lt;A href="http://video.esri.com/watch/4213/the-arcgis-platform"&gt;the plenary at DevSummit&lt;/A&gt;. Shipping software depends on a number of external factors, and there is naturally some variability in the specifics of the releases.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Apr 2015 02:38:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636852#M49595</guid>
      <dc:creator>ShaunWalbridge</dc:creator>
      <dc:date>2015-04-17T02:38:30Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636853#M49596</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Apart from waiting for 10.4 does anyone have suggestions for dealing with dates not coming across from a numpy array to a table?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 18 Jun 2015 21:35:01 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636853#M49596</guid>
      <dc:creator>LorneDmitruk</dc:creator>
      <dc:date>2015-06-18T21:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636854#M49597</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is your situation/scenario exactly?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2015 14:33:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636854#M49597</guid>
      <dc:creator>JamesCrandall</dc:creator>
      <dc:date>2015-06-19T14:33:53Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636855#M49598</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm reading a view from a non geodatabase Oracle table containing a number of date fields. In addition the view field names also contain spaces and parentheses. So I read the table into a pandas data frame using an sql query to get the field names GDB friendly, convert to a numpy record array and from there into a scratch table in a file GDB. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have played around using table to table but if I use field maps it takes a really long time to process, the table has over 100 fields as that's what the users want. Also the view has a couple of fields that are not required and I strip them out in the sql query. Unfortunately I don't have control over how the view was created and can't get it changed. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2015 15:32:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636855#M49598</guid>
      <dc:creator>LorneDmitruk</dc:creator>
      <dc:date>2015-06-19T15:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636856#M49599</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Improper field names sounds like it should be addressed at the database rather than doing a bunch of gymnastics to transform it elsewhere.&amp;nbsp; That's an easy fix, just order the dba's to fix it. &lt;IMG src="https://community.esri.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What if you were to do the pandas DataFrame-to-numpy-to-featureclass/table minus the date fields, create a secondary pandas dataframe with just a "joinable" field and the date fields then Table_To_Table() those separately and join them back to the larger featureclass/table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We do similar processing using cx_Oracle to integrate non-spatial tables. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 Jun 2015 17:25:32 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636856#M49599</guid>
      <dc:creator>JamesCrandall</dc:creator>
      <dc:date>2015-06-19T17:25:32Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636857#M49600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm looking at the documentation in using NumPy in ArcGIS Pro and the only reference I can find to date format is &amp;lt;m8[us]. I'm having issues trying to populate a table using datetime64[ns]; the output type from pandas.to_datetime()&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Was this fully implemented? I'm not super familiar with the different types of datetime&amp;nbsp;so this has been fairly hard to research.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="http://pro.arcgis.com/en/pro-app/arcpy/get-started/working-with-numpy-in-arcgis.htm" title="http://pro.arcgis.com/en/pro-app/arcpy/get-started/working-with-numpy-in-arcgis.htm"&gt;Working with NumPy in ArcGIS—ArcPy Get Started | ArcGIS Desktop&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Nov 2018 03:42:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636857#M49600</guid>
      <dc:creator>GIS_Spellblade</dc:creator>
      <dc:date>2018-11-14T03:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636858#M49601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;just do a 'help' or 'dir' on these&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;np.datetime64, &amp;nbsp; np.datetime_as_string, &amp;nbsp; np.datetime_data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;most is defined in multiarray&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="link-titled" href="https://github.com/numpy/numpy/blob/master/numpy/core/multiarray.py" title="https://github.com/numpy/numpy/blob/master/numpy/core/multiarray.py"&gt;numpy/multiarray.py at master · numpy/numpy · GitHub&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you want to explore the current and backward compatability.&lt;/P&gt;&lt;P&gt;Pandas derives from these&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Nov 2018 04:27:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636858#M49601</guid>
      <dc:creator>DanPatterson_Retired</dc:creator>
      <dc:date>2018-11-14T04:27:56Z</dc:date>
    </item>
    <item>
      <title>Re: ArcPy Data Access Support for numpy.datetime64 and Python datetime</title>
      <link>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636859#M49602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In addition to Dan's advice, there's also the ArcGIS API for Python which is included in Pro, and includes a direct conversion to pandas via the spatially enabled data frame: &lt;A class="link-titled" href="https://developers.arcgis.com/python/guide/introduction-to-the-spatially-enabled-dataframe/" title="https://developers.arcgis.com/python/guide/introduction-to-the-spatially-enabled-dataframe/"&gt;Introduction to the Spatially Enabled DataFrame | ArcGIS for Developers&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also see this GIS.SE post with some details on conversion: &lt;A class="link-titled" href="https://gis.stackexchange.com/a/221670/143" title="https://gis.stackexchange.com/a/221670/143"&gt;arcpy - NumPyArrayToTable - RuntimeError: unsupported time units. use M8[us] - Geographic Information Systems Stack Exch…&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2018 06:57:07 GMT</pubDate>
      <guid>https://community.esri.com/t5/python-questions/arcpy-data-access-support-for-numpy-datetime64-and/m-p/636859#M49602</guid>
      <dc:creator>ShaunWalbridge</dc:creator>
      <dc:date>2018-12-06T06:57:07Z</dc:date>
    </item>
  </channel>
</rss>

