Latest Contributions by VinceAngelo

The third option is an ON INSERT OR UPDATE trigger to preserve the contents of the actual column. - V ... View more

This is more like a religious issue than a technical one. The DBA should have a say in the process, since they'll be the one supporting the configuration. Esri supports both (provided you're using the release documented as supported [and recognize "and higher" where appropriate]). Benchmarking both for your requirements is not a bad idea. - V ... View more

Okay, it could be the Esri DLL that's at fault, but it's more likely the FME code. The best way to explore this is with FME tech support (Safe Software -- https://support.safe.com/knowledgesubmitcase ). It's best to build as small of a test dataset as exhibits the issue (and if size impacts it, be sure to let them know where the cutoff is). ... View more

Is this the FME extension to ArcGIS or FME which is crashing? Esri doesn't support FME software. Does it work with a file geodatabase target (which you could then process with less complexity)? - V ... View more

If the user is really "User_20230925" and database is really "Test_20230925", you might be having issues due to the upper-case characters. The connection code recases object names to lowercase. I've never been able to connect to mixed case named databases or as a mixed case username. - V ... View more

Are you using the "Append" tool? Is the "geodatabase"  file geodatabase or enterprise (and if so, which RDBMS)? Even if it would allow it, I wouldn't be terribly comfortable trying to project on the fly as an append. - V ... View more

Possible? Yes.  Supported? Big no. Yes (a change since I last attempted it, at 10.4) If you're familiar with how PostgreSQL works, hacking in via conf file changes might get you in,  [or you can use the supported tools to show the user/password and enable external connections], but it's possible that it won't get you too far, because you'd then need to traverse the geodatabase architecture from SQL (in psql or pgAdmin) You really want to work with Tech Support to resolve the root problem. - V ... View more

There are better, more useful ways to lock down a Python install than to just ban Python use. Doing it this way is so simplistic it doesn't bode well for "business reasons" arguments. This is more a management issue than a technical one. You need someone to lean on the IT folks to create a workable solution, not to just punt the problem to the end-users. - V ... View more

"TRUNCATE" is an unlogged removal process, so you probably mean "UPDATE" or "DELETE". "Append" is generally an INSERT. Your update criteria isn't very clear, so it's not easy to make a specific recommendation. I've had good luck using FeatureClassToFeatureClass or FeatureClassToGeodatabase into a temporary table in the database, then using SQL to UPDATE changed rows, INSERT new rows, and DELETE removed rows. This was not in a versioned feature class, so I didn't have to deal with versioned views. arcpy.ArcSDESQLExecute() can be used to issue the SQL from ArcPy. Not sure what the Pro SDK equivalent would be. - V ... View more

Hexagons can't be tessellated themselves. You need to move on to triangles after the initial layer. I've actually got code for this in my Blog post. Squares (aka diamonds) can be sub-tessellated, as can triangles themselves. It's not clear what a unic layer might be. - V ... View more

The value in the computed length field depends on the map projection used in your canvas. Web Mercator is useless for planar measurement (the poles are infinitely far from the Equator, so all measurements not along the Equator itself are skewed, potentially infinitely), as are all geographic coordinate systems (Cartesian degrees are meaningless). Some measurement calculations in the UI are smart enough to not trust Web Mercator, and to do geodesic computation with a geographic coordsys, but the table rows are going to return Cartesian results (the units of which may not make sense). If you use a coordinate reference which is not the same as the data source, any stored values in the original coordref may not agree with the values computed "on-the-fly" by reprojection.  The amount of error may vary by location (e.g. over Africa vs. over Iceland). - V ... View more

Any query returning over a hundred thousand rows of 2 million is always going to be slow, especially through a service that only returns 2000 records at a time, in a format that's much, much larger than the raw data. This has nothing to do with PostgreSQL and everything to do with throughput.  - V ... View more

It's more likely that the ST_Intersects() is your performance bottleneck, especially if you have not constructed a spatial index. Personally, I'd do this query as a single statement using a virtual table, and with an ST_Within:   UPDATE parcel_new_pin u SET zoning = vt.zoning FROM ( SELECT p.pin, p.zoning FROM parcel_new_pin p JOIN ZONING z2 ON sde.ST_Within(sde.ST_PointOnSurface(p.shape,z2.shape)) = 1 WHERE p.zoning <> z2.zoning_district AND z2.zoning_district <> 'HB-S MLKO' ) vt WHERE u.pin = vt.pin;   For this query, I'd make sure that ZONING has an index on the geometry column, and PARCEL_NEW_PIN has an index on PIN.  Additionally, you can test the raw performance of the ST_PointOnSurface query in isolation:   SELECT sde.ST_PointOnSurface((p.shape)) FROM parcel_new_pin p   And the performance of the JOIN without UPDATE:   SELECT p.pin, p.zoning FROM parcel_new_pin p JOIN ZONING z2 ON sde.ST_Within(sde.ST_PointOnSurface(p.shape,z2.shape)) = 1 WHERE p.zoning <> z2.zoning_district AND z2.zoning_district <> 'HB-S MLKO'   If you haven't built a spatial index on the polygons of ZONING, that should be your first priority, though it's probably easiest to use the ArcPy utility Add Spatial Index (Data Management) via an enterprise geodatabase connection (.sde) file, at least at first, since the parameters can be tricky. - V ... View more

I've done a join with 72M ST_PointOnSurface calculations against a 35M polygon layer to verify parent-child relationships using PostgreSQL with PostGIS geometry, and it ran in less than 25min (on a RDS xlarge instance). I never tried that in Oracle with SDE.ST_GEOMETRY (or with the PG sde.ST_Geometry implementation) How many features? What is the average vertex count in the polygons? How are the indexes built? What does the query plan look like? How long does a simple "SELECT geomcol FROM tablename" query take on the table, and how long does a unbounded ST_PointOnSurface query take.  Including the actual query will help generate feedback. - V ... View more