Latest Contributions by Bud

I think the synopsis/subject line would be acceptable. And maybe some other non-sensitive information like the status and dates?  I assume the full user story is confidential and can't be posted publicly. To be honest, I don't really know what info to ask for, since I've never seen a full ENH. They're a bit of a mystery to me. Sometimes I see ENH numbers in community posts, etc. But I don't have a way to look them up. Thanks. ... View more

Here's an example of a bug I reported 9 months ago, but it still isn't available on the Esri Technical Support website: https://support.esri.com/en/search-results#search?q=000150273&content-type=Bugs BUG-000150273 - ST_Geometry functions applied to the Shape field in Select By Attributes return the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned. Reported: June 24, 2022 I'm told the bug is still "In Review". Does it normally take that long for Esri to review bugs? ... View more

BUG-000150273 Status In Review  Synopsis ST_Geometry functions applied to the Shape field in Select By Attributes return the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned.   Environment Reproduced in: ArcGIS Pro 3.0 or ArcGIS Pro 2.9.3 or ArcMap 10.8.2 or ArcMap 10.7.1 Geodatabase version 10.9.2 or 10.7.1 Oracle 18c   Steps to Reproduce Create a line feature class Add some features to feature class Use Select by Attributes to query fc Where: "sde.st_length(shape) > 400" (use whatever value makes sense for the length of the lines) The selection will work Register the feature class as versioned Repeat the Select by Attribute query from step 3 - you will receive an error "Error 000358: Invalid expression" Additional information Not reproducible in SQL Server (i.e. "SHAPE.STLength() > 400" Similar to BUG-000109287 Reproducible with other queries (i.e. query customer was using "abs(sde.st_maxm(shape) - sde.st_length(shape))  > 1" - find polylines where the maximum M-value doesn't equal the length) Error in ArcMap is: [ORA-00904: "SHAPE": invalid identifier] Workarounds Place the expression in subquery. For example: OBJECTID IN  (SELECT    OBJECTID FROM   USER1.ACTIVE_TRANSPORTATION where   sde.st_length(shape) > 400 ) [OR] Use calculate geometry or calculate field to populate new fields with the values. Then, apply any further ST_Geometry functions on the fields instead of using the shape field. ... View more

Is the following correct? All rings are closed, but not all closed are rings. ... View more

I think the answer is: I should be using isRing. The word "Ring" is self-explanatory. I was originally thrown off by the fact that some of my lines are multi-parts. So, an individual part could technically be a ring, even though the feature as a whole didn't appear to be a ring. So, both of my example features were being identified as closed and as rings (my query only looked at the first part of multi-part features; in my examples, the first part was a ring). I've accounted for the multi-part quirk, and other quirks, in the following query: objectid in ( select objectid from roads where sde.st_numgeometries(shape) = 1 --Needs to be evaluated before isRing. Otherwise, isRing throws an error since it can't be used on multi-part features. and sde.st_isRing(shape) = 1 and name not like ('% CT') --Some courts are literally just a loop with no straight portion. They are technically legitimate rings. So I'll omit them since I'm specifically looking for roundabouts, not courts. --and ownership = 'ABC' and sde.st_length(shape) <= 200 --If a road is longer than 200m, then it probably isn't a roundabout. --In the future, if needed, I could omit roads with this text in the name (similar to what I did with CT): PL, CIRCLE, DR, TRAIL, CRES, LOOP, SQUARE. --However, right now, that doesn’t seem to be necessary. Those road types get successfully excluded via the “must be shorter than 200m” criteria. )   ... View more

It turns out the cul-de-sac in the second example is actually a multi-part feature: Bud_0-1677686951178.png     ... View more

I think this idea should be re-opened. ... View more

Esri Canada Case 03268522 - Comments in SQL expressions - Single-line comment at and of statement causes error ENH-000156157 - ArcGIS Pro - Add a line break automatically to the end of any definition query SQL expression applied to a mobile geodatabase feature class to avoid the error "The SQL expression has invalid syntax." when a SQL single-line comment that is not terminated by a line break is inserted at the end of the expression. ENH-000156184 - ArcGIS Pro - Change the error message displayed when a SQL single-line comment that is not terminated with a line break and that doesn't include a space is inserted at the end of a definition query SQL expression applied to a mobile geodatabase feature class from "Fields do not match." to "The SQL expression has invalid syntax.". ENH-000156189 - ArcGIS Pro - Add documentation that outlines how to add single-line and multi-line comments to a definition query SQL expression applied to a mobile geodatabase feature class. ... View more

BUG-000156143 - An SQL query containing the EXISTS predicate validates successfully but returns incorrect results from a file geodatabase. ENH-000156158 - Raise exception when using unsupported SQL expressions in file geodatabases. Esri Canada Case 03264937 - Exception not raised when unsupported FGDB SQL used (correlated subquery) ... View more

BUG-000156143 - An SQL query containing the EXISTS predicate validates successfully but returns incorrect results from a file geodatabase. ENH-000156158 - Raise exception when using unsupported SQL expressions in file geodatabases. Esri Canada Case 03264937 - Exception not raised when unsupported FGDB SQL used (correlated subquery) ... View more

BUG-000156143 - An SQL query containing the EXISTS predicate validates successfully but returns incorrect results from a file geodatabase. ENH-000156158 - Raise exception when using unsupported SQL expressions in file geodatabases. Esri Canada Case 03264937 - Exception not raised when unsupported FGDB SQL used (correlated subquery) ... View more

BUG-000156143 - An SQL query containing the EXISTS predicate validates successfully but returns incorrect results from a file geodatabase. ENH-000156158 - Raise exception when using unsupported SQL expressions in file geodatabases. Esri Canada Case 03264937 - Exception not raised when unsupported FGDB SQL used (correlated subquery) ... View more

Do you find you use the quote functionality much? I wonder if the UI/tree serves the same purpose when making replies. ... View more