Latest Contributions by Bud

‎02-25-2022

@DavidCardella

‎02-25-2022

When ESRI staff merge ideas by converting the duplicate idea to a comment: It would help if the comment could indicate that it was inserted by the system/ESRI — and was formerly an idea. Reason: Comments that were converted from ideas often appear to come out of nowhere. As far as I can tell, there's no way to tell that they were originally ideas. Example: https://community.esri.com/t5/arcgis-pro-ideas/calculating-the-x-and-y-coordinate-automatically/idc-p/940925/highlight/true#M15674 That idea—>comment doesn't have any context. So the person who had commented previously was confused, since they’d already addressed the issue in a previous comment. If some background info were added as a auto-generated header, explaining where the comment came from, then that would avoid confusion. "This comment was originally a separate idea; merged."

‎02-25-2022

It would be helpful if ESRI could add a hasCurve geometry property to Arcade. Use case: When using Calculation Attribute Rules to update the shape column of features, it would be helpful if we could check if polylines or polygons have true curves or not. https://developers.arcgis.com/arcade/guide/types/#polyline Thanks.

‎02-24-2022

Good call. When reading the docs for Arcade, I came across this line: "Geometry is immutable, meaning it is not possible to change the geometry after it is created." https://developers.arcgis.com/arcade/guide/types/#geometry So I figured Attribute Rules wouldn't be an option. But I think I must have misunderstood. Related info here: Idea: Easy way to update geometry in real time — after an edit is saved

‎02-24-2022

@Scott_Harris Thanks! I'd been reading the docs for Arcade, and came across this line: "Geometry is immutable, meaning it is not possible to change the geometry after it is created." https://developers.arcgis.com/arcade/guide/types/#geometry So I figured Attribute Rules (which I think use Arcade) wouldn't be an option. But I must have misunderstood.

‎02-23-2022

Related: Script (ArcPy) vs field calculator (Python Parser) behaviour of getPart in ArcGIS for Desktop?

‎02-23-2022

It would be great if there were an easy way to update the geometry of existing features in real time / after an edit is made. It would be the equivalent of a DB trigger, but using logic similar to the Python field calculator script below: #Updates the vertices of existing features def new_shape(geom): spatial_reference = geom.spatialReference geom = geom.densify("ANGLE", 10000, 0.174533) parts = arcpy.Array() for i in range(geom.partCount): part = geom.getPart(i) points = arcpy.Array() for j in range(part.count): point = part.getObject(j) point.M = geom.measureOnLine(point) points.append(point) parts.append(points) return arcpy.Polyline(parts, spatial_reference) Currently, there doesn't seem to be an easy way to do that in ArcGIS Pro, without customizing via a .NET add-in. And unfortunately, it's not possible in the DB either, since the SDE.ST_GEOMETRY (Oracle) functions are too limited.

‎02-23-2022

Using Arcade: Is there a way to update the geometry of an existing feature after an edit is made? It would be the equivalent of a DB trigger, but using logic similar to the Python field calculator script below: #written for ArcMap (https://gis.stackexchange.com/q/423806/62572) def new_shape(geom): spatial_reference = geom.spatialReference geom = geom.densify("ANGLE", 10000, 0.174533) parts = arcpy.Array() for i in range(geom.partCount): part = geom.getPart(i) points = arcpy.Array() for j in range(part.count): point = part.getObject(j) point.M = geom.measureOnLine(point) points.append(point) parts.append(points) return arcpy.Polyline(parts, spatial_reference) I suspect that's not possible, but just wanted to check to be sure. I'm having a hard time finding a solution — something that will be executed in real time after a feature is edited. There doesn't seem to be a way to do that. Even the SDE.ST_GEOMETRY functions (for an Oracle db trigger) are too limited.

‎02-23-2022

@jcarlson Yeah, I don't know why the <code> tags need to be stripped out. It seems like forums from other vendors like the IBM Community forum use the same underlying 3rd party text editor that the ArcGIS community uses. But in IBM's implementation of the text editor, inline code snippets are allowed. For example, I can enter a code snippet, and it will be highlighted in red, just like the ArcGIS Community forum. But the difference is: it won't be stripped out. The inline code snippet will show up in the final post without issue. I wonder if ESRI could consider allowing inline code snippets too? Cheers.

‎02-22-2022

It would be helpful if inline code snippets could be supported in ArcGIS Community posts. Example: While we can change the font of in-line text: for point in part:, it would be better if we could also change the background color to grey, etc. That would make it a lot easier to read text that has inline code. Thanks!

‎02-22-2022

Thanks very much. That really helps. I posted an ArcGIS Pro Idea about it here: Enhance the geoprocessing array: Directly iterate over items in a container Feel free to suggest improvements to that idea.

‎02-22-2022

The answer in this post describes it best: Why does "for point in part:" work in a standalone ArcPy script, but not in the Field Calculator? The difference in behavior is due to the fact that objects within geoprocessing tools are not the same as objects within ArcPy. The pattern of directly iterating over items in a container, for point in part:, is a Python use pattern that is implemented in most ArcPy classes but not in ArcObjects classes being used by geoprocessing tools. The geoprocessing array does not implement the __iter__ special method while ArcPy Array does implement it. Idea: Could ESRI please enhance the geoprocessing array so that we can directly iterate over items in a container? Examples: for part in geometry: for point in part: Thanks.

‎02-22-2022

Regarding this recent video from ESRI: ArcGIS Platform - A Developer's Introduction The presenter talks about the following: "There is a client-side geometry engine that includes an SQL API for querying features in-memory (for both spatial queries and attribute queries) and thus minimizing trips back and forth to the server." Question: Where can I find more information about the "SQL API"? I tried googling it, and found a page called JavaScript API —> geometryEngine. But it doesn't seem to mention anything about SQL. Thanks.

‎02-21-2022

ArcMap 10.7.1 — Oracle 18c SDE.St_Geometry — Polyline FC I have an ArcPy function that works as expected in a standalone ArcPy script (PyScripter): def new_shape(geom): spatial_reference = geom.spatialReference parts = arcpy.Array() for i in range(geom.partCount): part = geom.getPart(i) points = arcpy.Array() for point in part: point.M = geom.measureOnLine(point) points.append(point) parts.append(points) return arcpy.Polyline(parts, spatial_reference) That function works correctly, including the following for loop. It returns a reconstructed shape to the main ArcPy Script. for point in part: point.M = geom.measureOnLine(point) points.append(point) However, when I use that same function in the Field Calculator, the script runs without errors, but it returns an empty shape. The problem seems to be the for loop: for point in part:. When I debug the code, I can see that the script doesn't enter the for loop. I was able to work around the issue by using a different style of for loop and the .getObject() array property. Now, the script enters the for loop and constructs the shape from the points, as expected: for j in range(part.count): point = part.getObject(j) point.M = geom.measureOnLine(point) points.append(point) Question: Why does for point in part: work in a standalone ArcPy script, but not in the Field Calculator? I would like to understand this better — in case I'm doing something wrong.

‎02-18-2022

ArcMap & Enterprise 10.7.1 — Oracle 18c SDE.ST_GEOMETRY — SQL Developer 18: I have an SDE.ST_GEOMETRY polyline FC that is M-enabled: In an SQL client like SQL Developer, I can query for the M-value of the endpoint of the line: select sde.st_m(sde.st_endpoint(shape)) from my_fc The result of that query is -Infinity. I didn't know that was possible and I wouldn't have thought to account for it when querying for possible values. Question: Is that behavior expected from ST_GEOMETRY functions? If anything, I would have expected the value to be Null, not -Infinity.

My Ideas

Latest Contributions by Bud

Re: Client-side geometry engine that includes an SQL API for querying features in-memory

When converting a duplicate idea to a comment: Indicate that the comment was originally an idea

hasCurve Arcade geometry property

Re: Update geometry after edit in real time — via Arcade?

Re: Easy way to update geometry in real time — after an edit is saved

Re: Why does "for point in part:" work in a standalone ArcPy script, but not in the Field Calculator?

Easy way to update geometry in real time — after an edit is saved

Update geometry after edit in real time — via Arcade?

Re: Support inline code snippets in ArcGIS Community posts

Inline code snippets

Re: Why does "for point in part:" work in a standalone ArcPy script, but not in the Field Calculator?

Geoprocessing array: Directly iterate over items in a container

Client-side geometry engine that includes an SQL API for querying features in-memory

Why does "for point in part:" work in a standalone ArcPy script, but not in the Field Calculator?

SDE.ST_M() returns negative infinity

Copy diagnostic monitor logs using CTRL+C

Store default raster symbology in geodatabase

Re: Attribute table fields constantly changing app...

Re: Annoying resizing of Columns in attribute tabl...

Re: How to delete a nonexistent, broken database v...

GIS Jobs

Roads and Highways User Group (RHUG)

Mapping and Charting Enterprise Databases