<?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 AddField should be able to add a shape field to a table in Data Management Ideas</title>
    <link>https://community.esri.com/t5/data-management-ideas/addfield-should-be-able-to-add-a-shape-field-to-a/idi-p/923580</link>
    <description>&lt;P&gt;I have a table that I want to make into a featureclass by adding a shape field and then populating the values.&lt;BR /&gt;This is not supported so I looked for alternatives. They are all very clumsy.&lt;BR /&gt;&lt;BR /&gt;It comes about because I have a many to many relation so a simple join will not do. I want the first point from one featureclass to populate many rows in the table so that I end up with a featureclass with some coincident points.&lt;BR /&gt;&lt;BR /&gt;Suggestion 1: In CreateFeatureClass() there is a &amp;lt;template&amp;gt; option. This will do.... oh no it won't! Why not? We already have to define a shape type and the spatial reference template at the end of the options is required for the spatial reference.&amp;nbsp; So why cannot we just use a table as a template without a shape field?&lt;BR /&gt;&lt;BR /&gt;Suggestion 2: Simply allow AddField to add a shape field with suitable spatial reference. Then I don't have to painfully copy the table row by row into a dummy featureclass using a Python cursor. This is tricky to set up a field list, strip off the objectid field carefully and loop about.&lt;BR /&gt;&lt;BR /&gt;Suggestion 3: Just use FME and abandon ArcGIS. Because this is available as a workaround nothing will change I fear.&lt;BR /&gt;&lt;BR /&gt;Once I have the ( null) shape field it would be easy to populate it from a dictionary of XY values obtained from another featureclass.&lt;BR /&gt;&lt;BR /&gt;Another complex workaround which could handle a many to one would be to use a Querylayer but both tables have to be in the same geodatabase so that would be another copy of another table.&lt;BR /&gt;&lt;BR /&gt;I am ending up with a slow complex Python script that could be a simple one-liner.&lt;/P&gt;&lt;!--  content transformation source ID: 087E00000005Fd3  --&gt;</description>
    <pubDate>Tue, 13 Sep 2022 18:07:05 GMT</pubDate>
    <dc:creator>KimOllivier</dc:creator>
    <dc:date>2022-09-13T18:07:05Z</dc:date>
    <item>
      <title>AddField should be able to add a shape field to a table</title>
      <link>https://community.esri.com/t5/data-management-ideas/addfield-should-be-able-to-add-a-shape-field-to-a/idi-p/923580</link>
      <description>&lt;P&gt;I have a table that I want to make into a featureclass by adding a shape field and then populating the values.&lt;BR /&gt;This is not supported so I looked for alternatives. They are all very clumsy.&lt;BR /&gt;&lt;BR /&gt;It comes about because I have a many to many relation so a simple join will not do. I want the first point from one featureclass to populate many rows in the table so that I end up with a featureclass with some coincident points.&lt;BR /&gt;&lt;BR /&gt;Suggestion 1: In CreateFeatureClass() there is a &amp;lt;template&amp;gt; option. This will do.... oh no it won't! Why not? We already have to define a shape type and the spatial reference template at the end of the options is required for the spatial reference.&amp;nbsp; So why cannot we just use a table as a template without a shape field?&lt;BR /&gt;&lt;BR /&gt;Suggestion 2: Simply allow AddField to add a shape field with suitable spatial reference. Then I don't have to painfully copy the table row by row into a dummy featureclass using a Python cursor. This is tricky to set up a field list, strip off the objectid field carefully and loop about.&lt;BR /&gt;&lt;BR /&gt;Suggestion 3: Just use FME and abandon ArcGIS. Because this is available as a workaround nothing will change I fear.&lt;BR /&gt;&lt;BR /&gt;Once I have the ( null) shape field it would be easy to populate it from a dictionary of XY values obtained from another featureclass.&lt;BR /&gt;&lt;BR /&gt;Another complex workaround which could handle a many to one would be to use a Querylayer but both tables have to be in the same geodatabase so that would be another copy of another table.&lt;BR /&gt;&lt;BR /&gt;I am ending up with a slow complex Python script that could be a simple one-liner.&lt;/P&gt;&lt;!--  content transformation source ID: 087E00000005Fd3  --&gt;</description>
      <pubDate>Tue, 13 Sep 2022 18:07:05 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/addfield-should-be-able-to-add-a-shape-field-to-a/idi-p/923580</guid>
      <dc:creator>KimOllivier</dc:creator>
      <dc:date>2022-09-13T18:07:05Z</dc:date>
    </item>
    <item>
      <title>Re: AddField should be able to add a shape field to a table</title>
      <link>https://community.esri.com/t5/data-management-ideas/addfield-should-be-able-to-add-a-shape-field-to-a/idc-p/923581#M204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;I have found a workaround at 10.3 - use a spatlalite database where you can do precisely this. Add a shape column to an existing table. Apparently every other GIS in the world already works like this!

&lt;!-- content transformation source ID: 00aE000000B5040 --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Mar 2015 08:15:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-ideas/addfield-should-be-able-to-add-a-shape-field-to-a/idc-p/923581#M204</guid>
      <dc:creator>KimOllivier</dc:creator>
      <dc:date>2015-03-30T08:15:43Z</dc:date>
    </item>
  </channel>
</rss>

