Latest Contributions by Bud

Function calls in PL/SQL are quite verbose. In a plain SQL query, we can do this… sde.st_geometryN_f(shape,1) …but in a custom PL/SQL function, we have to do this: sde.st_geometry_operators.st_geometryN_f(shape,1) Which makes the function calls hard to read when we string multiple functions together: -- startpoint X of a multi-part polyline sde.st_geometry_operators.st_x_f(sde.st_geometry_operators.st_startpoint_f(sde.st_geometry_operators.st_geometryN_f(shape,1))); More info: Use SDE.ST_GEOMETRY functions in a custom function Could Esri give us a shorter way to make SDE.ST_GEOMETRY function calls in PL/SQL? ... View more

With Oracle Spatial, we have the option of using sites like db<>fiddle and Oracle Live SQL to mock up SQL or data online...and share it...when troubleshooting code in forums (Esri Community, GIS SE, etc.). That works great when using native datatypes like SDO_GEOMETRY. But when it comes to datatypes like SDE.ST_GEOMETRY, we're out of luck. Could Esri provide an online playground that has the ST_GEOMETRY datatype (in Oracle)? Similar to what we have for Arcade, but also shareable.     ... View more

I have a calculation attribute rule that runs without errors, but doesn't work as expected: Attribute rule works in Pro 2.9.2, but not in Pro 2.6.8 I want to debug the code, to see what part of it is failing to update the geometry's vertices. The code doesn't produce any errors, so I can't use error messages to help me. And ArcGIS Pro 2.6.8 doesn't support outputting console messages (unlike Pro 2.9.2 +/-). Does anyone have any tips for debugging Arcade code in that scenario?   ... View more

I have a calculation attribute rule that works in Pro 2.9.2 (in a 2.9.2 FGDB). It updates the M-values of the polyline geometry: function pythagoras(x1, y1, x2, y2) { return sqrt(pow(x2 - x1, 2) + pow(y2 - y1, 2)); } var geom = Dictionary(Text(Geometry($feature))); var paths = geom['paths']; var oldX = paths[0][0][0]; var oldY = paths[0][0][1]; var line_length = 0; for (var path_idx in paths) { for (var point_idx in paths[path_idx]) { var newX = paths[path_idx][point_idx][0]; var newY = paths[path_idx][point_idx][1]; if (point_idx != 0) { line_length += pythagoras(oldX, oldY, newX, newY); } paths[path_idx][point_idx][-1] = line_length; oldX = newX; oldY = newY; } } return Polyline(geom); However, if I create that attribute rule in Pro 2.6.8 (in a separate 2.6.8 FGDB), it doesn't work as expected. It runs without errors, and it even densifies true curves (which tells me that the code is running), but it doesn't update the M-values of the vertices properly (it sets the M-values to Nan). Question: Is there something in that script that is not supported in older versions of ArcGIS Pro? I believe the Dictionary(), Text(), and Geometry() functions are working ok (since the script successfully returns a densified geometry). So I think it must be something else. Unfortunately, I can't upgrade Pro any further right now, since our version of license manager doesn't support later versions of Pro. Thanks!   ... View more

Could Esri consider changing the "Exclude from Application Evaluation" flag so that it's more intuitive? A lot of people find that flag confusing. For example, change the flag to "Allow Application Evaluation".  Thanks. ... View more

  I have a multi-part polyline in an SDE.ST_GEOMETRY feature class (Oracle 18c EGDB). I've written a PL/SQL function that replaces the geometry's M-values with the cumulative length of the line. (My plan is to eventually create a database trigger that uses the function to update polyline geometries — when features get edited.) Input: MULTILINESTRING M (( 0.0 5.0 -100000.0, 10.0 10.0 -100000.0, 30.0 0.0 -123),( 50.0 10.0 456, 60.0 10.0 789)) --select sde.st_astext(shape) from polylines Output: MULTILINESTRING M ((0 5 0, 10 10 11.18, 30 0 33.54),(50 10 33.54, 60 10 43.54)) --select m_as_length(shape) from polylines Question: The m_as_length() function works as expected.   But I'm a PL/SQL novice, so I thought I'd ask: Can the script be improved?  with function pythagoras(x1 in number, y1 in number, x2 in number, y2 in number) return number is begin return round(sqrt( (x2 - x1) * (x2 - x1) + (y2 - y1) * (y2 - y1)), 2); -- Power is a slow function end; function m_as_length(shape in sde.st_geometry) return varchar2 is result varchar2(32767); vertex_set varchar2(32767); oldX number; oldY number; newX number; newY number; line_len number := 0; begin for vPartIndex in 1..sde.st_geometry_operators.st_numgeometries_f(shape) loop vertex_set := null; for vPointIndex in 1..sde.st_geometry_operators.st_numpoints_f(sde.st_geometry_operators.ST_GeometryN_f(shape,vPartIndex)) loop newX := sde.st_geometry_operators.st_x_f(sde.st_geometry_operators.st_pointn_f(sde.st_geometry_operators.st_geometryn_f(shape,vPartIndex),vPointIndex)); newY := sde.st_geometry_operators.st_y_f(sde.st_geometry_operators.st_pointn_f(sde.st_geometry_operators.st_geometryn_f(shape,vPartIndex),vPointIndex)); if vPointIndex <> 1 then line_len := line_len + pythagoras(oldX, oldY, newX, newY); end if; oldX := newX; oldY := newY; vertex_set := vertex_set || newX || ' ' || newY || ' ' || line_len || ', '; end loop; result := result || '(' || rtrim((vertex_set),', ') || '),'; end loop; return 'MULTILINESTRING M (' || rtrim((result),',') || ')'; end; select m_as_length(shape) from polyline Related: Use SDE.ST_GEOMETRY functions in a custom function Explains why the function calls are so verbose:  sde.st_geometry_operators.st_numgeometries_f. ST_GEOMETRY functions: st_numgeometries st_x st_startpoint st_geometryN st_numpoints st_pointn I'm aware that this sort of thing can be achieved with Arcade in ArcGIS Pro 2.6+. Even still, I want to learn how to do this in PL/SQL, for professional development reasons, and to have a plan B, for scenarios where Arcade won't work (due to compatibility issues, etc.). My FC is registered as versioned (with option to move edits to base). We don't use named versions, we only use the default version (so that we can undo/redo edits while editing). So in this case, using database triggers on a versioned FC shouldn't be an issue -- especially since we're exclusively working in the base FC -- and are using the "with base" option.   ... View more