<?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: Problem wirth XY Table to Point: mysterious invalid fields in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222323#M61144</link>
    <description>&lt;P&gt;Thanks for looking into it Barry, and yes, they should be offshore Ireland. I use AGP 2.8.1&lt;/P&gt;</description>
    <pubDate>Sun, 16 Oct 2022 16:42:59 GMT</pubDate>
    <dc:creator>RArosio</dc:creator>
    <dc:date>2022-10-16T16:42:59Z</dc:date>
    <item>
      <title>Problem wirth XY Table to Point: mysterious invalid fields</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222320#M61141</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I am struggling to load points on a csv table using XY Table To Point (Data Management). The error I receive is either "invalid field type" or "TypeError: '&amp;lt;' not supported between instances of 'int' and 'str'"(see attached) depending on whether I run the tool through a custom toolbox I created or directly using the tool from the Toolboxes list. I double-checked several times and I cannot find any problem with the fields in the csv.&lt;/P&gt;&lt;P&gt;Any help is very welcome.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Oct 2022 15:17:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222320#M61141</guid>
      <dc:creator>RArosio</dc:creator>
      <dc:date>2022-10-16T15:17:14Z</dc:date>
    </item>
    <item>
      <title>Re: Problem wirth XY Table to Point: mysterious invalid fields</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222322#M61143</link>
      <description>&lt;P&gt;I am using AGP 3.0.2 and XY Table To Point worked OK on the csv sample you provided (POINT_X and POINT_Y - WGS84) although it threw a warning that it dropped field Shape_Leng from the output. This field name is usually the truncated version of Shape_Length to meet the shapefile/dBase 10 character limit and might be being treated as reserved? I renamed it as Length and ran the tool again without throwing a warning. Points generated successfully off the coast of Ireland.&lt;/P&gt;&lt;P&gt;Also, people have reported problems associated with Excel when upgrading to 3x. Esri:" &lt;EM&gt;These behaviors are caused by a missing 64-bit Microsoft Access Database Engine driver. ArcGIS Pro 3.0 requires the Microsoft .NET 6 Desktop Runtime – Windows x64 Installer, along with the Microsoft Access Database Engine 2016 Redistributable 64-bit driver for Excel&lt;/EM&gt;".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 16 Oct 2022 16:25:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222322#M61143</guid>
      <dc:creator>BarryNorthey</dc:creator>
      <dc:date>2022-10-16T16:25:52Z</dc:date>
    </item>
    <item>
      <title>Re: Problem wirth XY Table to Point: mysterious invalid fields</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222323#M61144</link>
      <description>&lt;P&gt;Thanks for looking into it Barry, and yes, they should be offshore Ireland. I use AGP 2.8.1&lt;/P&gt;</description>
      <pubDate>Sun, 16 Oct 2022 16:42:59 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/problem-wirth-xy-table-to-point-mysterious-invalid/m-p/1222323#M61144</guid>
      <dc:creator>RArosio</dc:creator>
      <dc:date>2022-10-16T16:42:59Z</dc:date>
    </item>
  </channel>
</rss>

