Latest Contributions by VinceAngelo

You need to include the meat of your execute() function in order to get help on this. The code should include an arcpy.da.Editor "with" block. - V ... View more

Shapefiles use 8-byte (64-bit) IEEE storage for all coordinate values.  The "32-bit" issue was in how what is now called BASIC spatial references handled coordinate processing.  While geodatabases store floating-point coordinates in a compressed bytestream which uses integers, the coordinates can be expressed as 8-byte (double precision) floats at any time. "Fuzzy creep" wasn't really a thing back in ArcInfo days (you'd have to misuse the software, changing the tolerance with each processing step to make it happen), and is less of a thing now (because tolerances are fixed by invariant spatial references). - V ... View more

There's a bunch of issues in the referenced post, wrongly conflated, or just plain wrong. IEEE floating-point storage is not "inaccurate" -- Floating-point operations are way more accurate than geodata It's not the accuracy (or precision) of floating-point representation which makes the fuzzy tolerance necessary, but the inherent accuracy of freely collected vertices ArcMap (and all of ArcGIS Desktop and Server products) has always had access to tolerances in coincident coordinate calculation The shapefile format was independent of ArcView, and the shapefile format does not have any of the quirks of the how ArcView (which is ancient, and retired) calculated coordinate values. While there may be gaps between geometries in shapefiles (or file or enterprise geodatabase), there are tools to detect them, and repair them (if they are significant enough to bother) The title of this thread is misleading, and refers not to coordinates, but dBase values; while dBase does have both binary and textual storage options for floating-point values, the scientific notation used in the text values is either at, or exceeds the stated precision of the field (and often of the IEEE format itself) So, basically, the entire article was wrong then, and hasn't gotten any better in the decades since. Since understanding how coordinate values are maintained is important, I refer you to the Understanding Coordinate Management in the Geodatabase whitepaper. - V ... View more

I've been 64-bit Python for a while now, so I'll admit to getting complacent about caching 6-12GiB of data in an app to write 60 million complex features in a few minutes.  And that was ~10 years back, when 27GiB was a large VM. My rule of thumb is to avoid nesting cursors. Cache with SearchCursor and then Insert or Update. Ba-da-bing, ba-da-boom. Generators are a wonderful trick for managing a non-cursor stream, but I worry about interaction with the underlying object via ArcObjects if selection sets and schema modifications are at play. - V ... View more

Looping on a data source that you are also running selection operations is always going to cause grief. I'd suggest you make an array or a dictionary from the search cursor, then loop on the array/dictionary contents (as Hayden has done).  While it is true that selections run against layers, not sources, playing fast with both at the same time is just trouble. - V ... View more

What are you quoting there, Dan? Because "multi-part" and "multi-ring" get conflated.  The rules in the underlying SgShape API are clear: A polygon is defined by one or more (non-self-intersecting) rings.  One ring is clearly not multi-part, but an island with a lake (or a county with a contained city) is multi-ring, but still single-part (the underlying API calls internal rings "subparts"). What we have here is two different definitions in the same API (which can happen when three different models are merged): The arcpy.Polygon.isMultipart method uses the Boolean for "has multiple rings" The arcpy.Polygon.partCount method uses parts and subparts definition for parts This script:   import arcpy sr = arcpy.SpatialReference(4326) sr.setFalseOriginAndUnits(-400.0,-400.0,1000) p1r1_wkt = 'POLYGON ((0 0, 9 0, 9 9, 0 9, 0 0))' p1r2_wkt = 'POLYGON ((0 0, 9 0, 9 9, 0 9, 0 0), (4 4, 6 4, 6 6, 4 6, 4 4))' p2r2_wkt = 'MULTIPOLYGON (((0 0, 4 0, 4 4, 0 4, 0 0)), ((5 5, 9 5, 9 9, 5 9, 5 5)))' p2r3_wkt = 'MULTIPOLYGON (((0 0, 4 0, 4 4, 0 4, 0 0), (1 1, 3 1, 3 3, 1 3, 3 3)), ((5 5, 9 5, 9 9, 5 9, 5 5)))' for wkt in [p1r1_wkt,p1r2_wkt,p2r2_wkt,p2r3_wkt]: geom = arcpy.FromWKT(wkt,sr) isMulti = geom.isMultipart partCount = geom.partCount ringCount = geom.boundary().partCount print(f"{wkt}\nMultipart: {isMulti}, Part Count: {partCount}, Ring Count: {ringCount}\n")   returns:   POLYGON ((0 0, 9 0, 9 9, 0 9, 0 0)) Multipart: False, Part Count: 1, Ring Count: 1 POLYGON ((0 0, 9 0, 9 9, 0 9, 0 0), (4 4, 6 4, 6 6, 4 6, 4 4)) Multipart: True, Part Count: 1, Ring Count: 2 MULTIPOLYGON (((0 0, 4 0, 4 4, 0 4, 0 0)), ((5 5, 9 5, 9 9, 5 9, 5 5))) Multipart: True, Part Count: 2, Ring Count: 2 MULTIPOLYGON (((0 0, 4 0, 4 4, 0 4, 0 0), (1 1, 3 1, 3 3, 1 3, 3 3)), ((5 5, 9 5, 9 9, 5 9, 5 5))) Multipart: True, Part Count: 2, Ring Count: 3 so we can see the dichotomy. If you want to use the OGC definition of Polygon, then you have to deal with three conditions: Zero rings ("POLYGON EMPTY") [In the Esri lexicon, this is a Nil-type geometry, not a Polygon] One ring One external ring and one or more internal rings So, at this point it becomes rote:  geom.isMultipart really means "Has multiple rings" and, geom.partCount == 1 is really "Is single part?" If you really want to know how many rings are present, use geom.boundary().partCount - V   ... View more

You haven't specified the data source type, so it's difficult to know what the SQL syntax of the provider requires, and what is optional (in PostgreSQL, you'd cast the string with 'ISO_string'::timestamp). String math is not best practice (slower and difficult to layout and debug).  Instead, you really ought to use "".format() or f"" formatting. - V ... View more

You haven't described how you made polygons from PDFs, or described what would constitute an accurate (or inaccurate) polygon. While it is possible to include too much information, there's no risk of that here. A screenshot, annotated in Paint to show both accurate and inaccurate features would be useful. - V ... View more

-2035 is a low-level "SG_SELF_INTERSECTING" error.  -2008 is "SG_SHAPE_INTEGRITY_ERROR". You should probably convert the SDO geometries to file geodatabase, then do a Repair Geometry there, then tie them back across. - V PS: Note that there are TWO validation procedures (at least). One uses the SDO function. The other is the ArcPy Check Geometry (and its sibling, Repair Geometry) Note that some "repairs" will corrupt the original intended shape (as when a "bowtie" rectangle is converted into two touching triangles, not a properly ordered quadrilateral), so you should review any repairs. ... View more

You haven't mentioned the Oracle release in use, but I've always used SDO_UTIL.TO_WKTGEOMETRY to generate Well-Known Text out of SDO_GEOMETRY. SELECT objectid, SDO_UTIL.TO_WKTGEOMETRY(geom) as wkt FROM schema.tablename At one point I ran into a bug (in an Oracle 19c patch release) where the SDO_UTIL function would produce invalid scientific notation near the Equator or Prime Meridian (e.g., "0.12345e-1.0" instead of  "0.12345e-1"), and I had to wrap the arcpy.FromWKT parser with a repair function. You might want to assure that the source SDO_GEOMETRY is valid before passing it into SDE.ST_GEOMETRY. - V ... View more

There's lots of variables here: The RDBMS, the frequency of data layer creation, the mechanisms used to maintain data contents, use of versioning, availability of SQL admin tool, individual DBA comfort with direct SQL queries,... I often have a SQL script to paste into a DB client (pgAdmin,...), with a follow-up ArcPy script to register as necessary. I once had an ArcPy script that loaded 40 tables into a temporary schema with FeatureClassToGeodatabase, then issued tens of thousands of SQL statements through ArcSDESQLExecute cursors to repopulate the 400M row publishing database. - V ... View more

If it's registered, then there's a layers table entry which could be UPDATEd. Personally, I mostly just use Query Layers, which don't require registration. - V ... View more

This is a really large and open-ended question. Instead of leaping into software selection and design, you probably want to do research into requirements and available data first. - V ... View more