Brian, Also, forgot this little tidbit that we (I?) discovered a while back, don’t even know if it’s a limitation anymore, but ESRI won’t allow much of anything edit-wise against the default database name (postgres) stating that it thinks this is a System database. Have you tried using a different database name, something other than “postgres” for connecting, and to edit? I didn’t pursue things after discovering this other than trying to set up a database alias to postgres, but this didn’t work the way I was expecting it to. It seems like a silly limit though, since we’ve been using the postgres database for our data for over a decade?? With no problems.
Anyway, some food for thought. Bobb From: postgis-users <[email protected]> on behalf of Bob Basques <[email protected]> Reply-To: PostGIS Discussion <[email protected]> Date: Wednesday, May 26, 2021 at 9:18 AM To: PostGIS Discussion <[email protected]> Subject: Re: [postgis-users] Does ArcGIS 2.7 Pro work with PostgreSQL 13 / PostGIS 3.1 Think Before You Click: This email originated outside our organization. Brian, Very interesting observations. I was actually wondering about this same type of scenario recently, A lot of the limits applied on the ESRI side end up being some sort of default setting that can be handled in some form, the biggest piece is finding the setting(s), the next is having control over trying to mitigate them . . . The newest version (400) of the AutoCAD extension for ESRI allows editing for example but with a bunch of predefined settings that need to be tweaked to make it work effectively. Not exactly the same as editing in Postgres, but similar, so I’m sure there is a path to pursue here. Bobb From: postgis-users <[email protected]> on behalf of Brian Wilson <[email protected]> Reply-To: PostGIS Discussion <[email protected]> Date: Monday, May 24, 2021 at 11:32 PM To: PostGIS Discussion <[email protected]> Subject: Re: [postgis-users] Does ArcGIS 2.7 Pro work with PostgreSQL 13 / PostGIS 3.1 Think Before You Click: This email originated outside our organization. When I've asked in the past, Esri people told me that PostGIS editing will not work. I always try things myself, regardless of what Esri people say. My answer is still NO, you cannot edit. I think the chances of them enabling editing are pretty much non-existent. They want everyone to subscribe to an annual license for ArcGIS Enterprise and supporting PostGIS would dilute that effort so this is no surprise to me. I just installed ArcGIS Pro 2.8 this afternoon and tested it with a fresh install of PostGIS 3 / Postgresql 12 (running on Ubuntu Server installed from UbuntuGIS). I am using a "personal" license so it's the "Advanced" version of Pro and I have the interop extension too. To get some data into PostGIS I loaded a polygon shapefile into QGIS and then used drag and dropto copy it into PostGIS, AMAZING and stunning to me how easy that was. Then I closed it and I started Pro 2.8, and I was able to connect to the database and load in the PostGIS table as a feature class. It worked just fine. Then I tried to edit it and it said "This layer's workspace is readonly." I searched the properties for the layer and I searched Esri online help for that string and found nothing. I am connected with the same credentials in both QGIS and Pro so the problem is in Pro. Then I launched QGIS and edited a polygon there. I stumbled because I have not used it for editing but I managed to move a vertex. Then I refreshed the layer in Pro and the change immediately appeared. I don't have any way to test the Basic license of Pro. I disabled Interop to make sure it was not doing something behind the scenes to allow me to view PostGIS data, and that had no effect. With it turned off I restarted Pro and the PostGIS layer loaded. AFAIK interop is just a very complicated ETL filter tool and does not do anything directly in the Pro GUI. Hope this helps -- Brian
_______________________________________________ postgis-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/postgis-users
