<?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>idea ArcPy to handle NA types when utilizing to_featureclass() conversion from Spatially Enabled Dataframe in ArcGIS API for Python Ideas</title>
    <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/arcpy-to-handle-na-types-when-utilizing-to/idi-p/1269036</link>
    <description>&lt;P&gt;Currently when a Spatially Enabled Dataframe contains the NA Type, to process to_featureclass() fails less than gracefully.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The error message returned does not provide context for the row number and field that contain the error&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="225453354-55236124-13e7-4ad7-9f9a-e9fec0ebcab2.png" style="width: 845px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/65580i7EFEDCB1B4395A2A/image-size/large?v=v2&amp;amp;px=999" role="button" title="225453354-55236124-13e7-4ad7-9f9a-e9fec0ebcab2.png" alt="225453354-55236124-13e7-4ad7-9f9a-e9fec0ebcab2.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;The error message could be avoided entirely with additionally processing from ArcPy to handle what is otherwise a standard datatype. Per this ArcGIS API for Python Idea by &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/649712"&gt;@vmarquart_max-boegl&lt;/a&gt;&amp;nbsp;:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-api-for-python-ideas/support-a-pd-na-to-np-nan-conversion-inside-the/idi-p/1266352" target="_blank"&gt;https://community.esri.com/t5/arcgis-api-for-python-ideas/support-a-pd-na-to-np-nan-conversion-inside-the/idi-p/1266352&lt;/A&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The idea here is to handle NA types better within the function.&lt;/STRONG&gt; While the NA type may not be handled by the endpoint database or file location, it is a relatively easy conversion process to make the item a null value or other value that is supported.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The maximal solution here is for that conversion to be handled "under the hood" by ArcPy and abstract this error checking/handling away from the user.&lt;/LI&gt;&lt;LI&gt;The minimal solution would be better error message output to provide a user explicit instruction on both row number (object_id since this is coming out of a spatially enabled dataframe) and column name/index.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Github issue that prompted this request:&amp;nbsp;&lt;A href="https://github.com/Esri/arcgis-python-api/issues/1494#event-8780331130" target="_blank"&gt;https://github.com/Esri/arcgis-python-api/issues/1494#event-8780331130&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 17 Mar 2023 16:46:54 GMT</pubDate>
    <dc:creator>feralcatcolonist</dc:creator>
    <dc:date>2023-03-17T16:46:54Z</dc:date>
    <item>
      <title>ArcPy to handle NA types when utilizing to_featureclass() conversion from Spatially Enabled Dataframe</title>
      <link>https://community.esri.com/t5/arcgis-api-for-python-ideas/arcpy-to-handle-na-types-when-utilizing-to/idi-p/1269036</link>
      <description>&lt;P&gt;Currently when a Spatially Enabled Dataframe contains the NA Type, to process to_featureclass() fails less than gracefully.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The error message returned does not provide context for the row number and field that contain the error&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="225453354-55236124-13e7-4ad7-9f9a-e9fec0ebcab2.png" style="width: 845px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/65580i7EFEDCB1B4395A2A/image-size/large?v=v2&amp;amp;px=999" role="button" title="225453354-55236124-13e7-4ad7-9f9a-e9fec0ebcab2.png" alt="225453354-55236124-13e7-4ad7-9f9a-e9fec0ebcab2.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;The error message could be avoided entirely with additionally processing from ArcPy to handle what is otherwise a standard datatype. Per this ArcGIS API for Python Idea by &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/649712"&gt;@vmarquart_max-boegl&lt;/a&gt;&amp;nbsp;:&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-api-for-python-ideas/support-a-pd-na-to-np-nan-conversion-inside-the/idi-p/1266352" target="_blank"&gt;https://community.esri.com/t5/arcgis-api-for-python-ideas/support-a-pd-na-to-np-nan-conversion-inside-the/idi-p/1266352&lt;/A&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The idea here is to handle NA types better within the function.&lt;/STRONG&gt; While the NA type may not be handled by the endpoint database or file location, it is a relatively easy conversion process to make the item a null value or other value that is supported.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;The maximal solution here is for that conversion to be handled "under the hood" by ArcPy and abstract this error checking/handling away from the user.&lt;/LI&gt;&lt;LI&gt;The minimal solution would be better error message output to provide a user explicit instruction on both row number (object_id since this is coming out of a spatially enabled dataframe) and column name/index.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Github issue that prompted this request:&amp;nbsp;&lt;A href="https://github.com/Esri/arcgis-python-api/issues/1494#event-8780331130" target="_blank"&gt;https://github.com/Esri/arcgis-python-api/issues/1494#event-8780331130&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Mar 2023 16:46:54 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-python-ideas/arcpy-to-handle-na-types-when-utilizing-to/idi-p/1269036</guid>
      <dc:creator>feralcatcolonist</dc:creator>
      <dc:date>2023-03-17T16:46:54Z</dc:date>
    </item>
  </channel>
</rss>

