<?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 Enable Editing of native PostGIS geometry without enterprise geodatabase (and license) in ArcGIS Pro Ideas</title>
    <link>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idi-p/1361421</link>
    <description>&lt;P&gt;Under current capabilities (as of 2023-12-15), it is not possible to edit spatial tables in a PostgreSQL database with native PostGIS geometry unless you &lt;STRONG&gt;first&lt;/STRONG&gt; undertake the "Create Enterprise Geodatabase" &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/setup-geodatabase-postgresql-windows.htm" target="_self"&gt;process.&lt;/A&gt; (And that process requires an expensive enterprise license.)&lt;/P&gt;&lt;P&gt;This is true despite the fact that Esri expresses "support" for "using" native PostGIS geometry in &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/data-types-postgresql.htm" target="_self"&gt;this help section&lt;/A&gt;. It is true you can &lt;STRONG&gt;read &lt;/STRONG&gt;such spatial tables (via query layer), and you can even &lt;STRONG&gt;load&lt;/STRONG&gt; them in (via geoprocessing), but you cannot &lt;STRONG&gt;edit&lt;/STRONG&gt; them. So that "support" is fairly limited when it comes to a core capability.&lt;/P&gt;&lt;P&gt;True, there are many cases when an "Enterprise Geodatabase" is advantageous. But there are other cases where it is not required and introduces unnecessary overhead. For very basic spatial data management, true support for PostgreSQL and PostGIS geometry would include editing from Pro.&lt;/P&gt;</description>
    <pubDate>Fri, 15 Dec 2023 15:34:26 GMT</pubDate>
    <dc:creator>MikeDolbow</dc:creator>
    <dc:date>2023-12-15T15:34:26Z</dc:date>
    <item>
      <title>Enable Editing of native PostGIS geometry without enterprise geodatabase (and license)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idi-p/1361421</link>
      <description>&lt;P&gt;Under current capabilities (as of 2023-12-15), it is not possible to edit spatial tables in a PostgreSQL database with native PostGIS geometry unless you &lt;STRONG&gt;first&lt;/STRONG&gt; undertake the "Create Enterprise Geodatabase" &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/setup-geodatabase-postgresql-windows.htm" target="_self"&gt;process.&lt;/A&gt; (And that process requires an expensive enterprise license.)&lt;/P&gt;&lt;P&gt;This is true despite the fact that Esri expresses "support" for "using" native PostGIS geometry in &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/data-types-postgresql.htm" target="_self"&gt;this help section&lt;/A&gt;. It is true you can &lt;STRONG&gt;read &lt;/STRONG&gt;such spatial tables (via query layer), and you can even &lt;STRONG&gt;load&lt;/STRONG&gt; them in (via geoprocessing), but you cannot &lt;STRONG&gt;edit&lt;/STRONG&gt; them. So that "support" is fairly limited when it comes to a core capability.&lt;/P&gt;&lt;P&gt;True, there are many cases when an "Enterprise Geodatabase" is advantageous. But there are other cases where it is not required and introduces unnecessary overhead. For very basic spatial data management, true support for PostgreSQL and PostGIS geometry would include editing from Pro.&lt;/P&gt;</description>
      <pubDate>Fri, 15 Dec 2023 15:34:26 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idi-p/1361421</guid>
      <dc:creator>MikeDolbow</dc:creator>
      <dc:date>2023-12-15T15:34:26Z</dc:date>
    </item>
    <item>
      <title>Re: Enable Editing of native PostGIS geometry without enterprise geodatabase (and license)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idc-p/1611331#M34670</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/7679"&gt;@MikeDolbow&lt;/a&gt;&amp;nbsp;- there is a workaround to edit Postgres data that I use without having ArcGIS Enterprise.&amp;nbsp; I use Python and FastAPI to create an editable feature service.&amp;nbsp; Then I add the feature service to ArcGIS Pro, and the data is editable, even though it is in Postgres.&amp;nbsp; These posts I wrote may help:&amp;nbsp;&lt;A href="https://www.linkedin.com/pulse/web-mapping-apps-postgres-arcgis-without-enterprise-rhys-donoghue" target="_blank"&gt;https://www.linkedin.com/pulse/web-mapping-apps-postgres-arcgis-without-enterprise-rhys-donoghue&lt;/A&gt;&amp;nbsp;and&amp;nbsp;&lt;A href="https://www.linkedin.com/pulse/how-load-geojson-from-postgres-using-bounding-box-arcgis-donoghue" target="_blank"&gt;https://www.linkedin.com/pulse/how-load-geojson-from-postgres-using-bounding-box-arcgis-donoghue&lt;/A&gt;.&amp;nbsp; At some stage I am planning on making my code open source.&amp;nbsp; I am bit too busy for that at the moment though.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 03 May 2025 00:58:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idc-p/1611331#M34670</guid>
      <dc:creator>rhys-kdrm</dc:creator>
      <dc:date>2025-05-03T00:58:58Z</dc:date>
    </item>
    <item>
      <title>Re: Enable Editing of native PostGIS geometry without enterprise geodatabase (and license)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idc-p/1612014#M34679</link>
      <description>&lt;P&gt;Thanks &lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/419427"&gt;@rhys-kdrm&lt;/a&gt; - I've heard about similar workarounds and I might pursue them. For now, I'm pretty comfortable either doing all my editing in QGIS or "offline" in Pro (then loading the data into the database with ArcPy).&lt;/P&gt;&lt;P&gt;Nevertheless, I'd still like to see this implemented.&lt;/P&gt;</description>
      <pubDate>Tue, 06 May 2025 15:36:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idc-p/1612014#M34679</guid>
      <dc:creator>MikeDolbow</dc:creator>
      <dc:date>2025-05-06T15:36:16Z</dc:date>
    </item>
    <item>
      <title>Re: Enable Editing of native PostGIS geometry without enterprise geodatabase (and license)</title>
      <link>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idc-p/1658404#M36441</link>
      <description>&lt;P&gt;I have used GISquirrel successfully in the past.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Oct 2025 13:18:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-ideas/enable-editing-of-native-postgis-geometry-without/idc-p/1658404#M36441</guid>
      <dc:creator>PatricePineaultWSP</dc:creator>
      <dc:date>2025-10-16T13:18:30Z</dc:date>
    </item>
  </channel>
</rss>

