[postgis-users] Does ArcGIS 2.7 Pro work with PostgreSQL 13 / PostGIS 3.1

[Regina Obe]

Has anyone tried running PostgreSQL 13 with PostGIS 3.1 and using ArcGIS Pro
2.7 for editing?

I gather from this that it is not supported?

https://desktop.arcgis.com/en/system-requirements/latest/database-requiremen
ts-postgresql.htm

I think for ST_Geometry type (ESRI's version) I would need to stick with
PostgreSQL 12 since they probably don't have PostgreSQL 13 binaries.

But I assume even for that case PostgreSQL 12 / PostGIS 3.1 should work fine
as it's not reliant on ESRI's libs.

Thanks,
Regina

_______________________________________________
postgis-users mailing list
postgi...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users

[Darafei "Komяpa" Praliaskouski]

ESRI has multiple issues in itself that are terrible to debug.

A client of ours fights a bug where it can't browse tables once you set random_page_cost to the SSD values of 1.1 instead of 4. So I guess if we're using a bit more index scan than usual there may be an unknown problem that does not show itself with QGIS and GeoServer.

--

Darafei "Komяpa" Praliaskouski
OSM BY Team - http://openstreetmap.by/

[Marco Boeringa]

I doubt this browsing issue has anything to do with 'random_page_cost'... Why on earth would it? This is a PostgreSQL setting, to which the ESRI software is essentially completely oblivious.

The ESRI software just sits on top of this PostgreSQL infrastructure, it essentially doesn't do anything different than QGIS does, just watch the SQL statements coming in in PgAdmin.

I have been running ArcMap and latest ArcGIS Pro versions against up to PostgreSQL 13 / PostGIS 3.1 mostly fine using ArcGIS "Query Layers", including browsing data from the catalogs in ArcMap and Pro, with a postgresql config optimized for SSD (both run against SATA and NVMe raid), and an OpenStreetMap "planet" size database on an HPZ840 dual CPU (S2) workstation that I managed to recently acquire second hand from a refurbished hardware supplier.

Yes, I have a few bug cases open at ESRI support, including one related to a very specific serious performance issue of one of the geoprocessing tools, but none of that related to 'random_page_cost'. Also, as soon as you start upgrading the technical challenges to OpenStreetMap "planet" size databases, ArcGIS certainly isn't the only software out there running into issues here and there, QGIS does too, as well as many other software packages. Handling > 500M record tables, just requires thought, whatever toolbox you happen to open...

Marco

Op 22-5-2021 om 12:51 schreef Darafei "Komяpa" Praliaskouski:

[Alexandre Neto]

I have this question for years... Never got a straight answer.

Is it possible to edit PostGIS tables/geometries using ArcGIS? (Without converting into the proprietary geometry type)

If so, what license level is needed?

Thanks,

Alexandre Neto

[Simon Greener]

I haven't used ArcGIS etc for many years, but the old answer was yes but you needed an Enterprise GeDatabase (ArcSDE) license which works with any of the supported "storage formats".

Get BlueMail for Android

[Brian Wilson]

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

[Basques, Bob (CI-StPaul)]

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 <postgis-us...@lists.osgeo.org> on behalf of Brian Wilson <br...@wildsong.biz>
Reply-To: PostGIS Discussion <postgi...@lists.osgeo.org>
Date: Monday, May 24, 2021 at 11:32 PM
To: PostGIS Discussion <postgi...@lists.osgeo.org>
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.

[Basques, Bob (CI-StPaul)]

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.