Latest Contributions by Bud

ArcPy: As far as I can tell, there isn't a way to create polyline vertices that have true curves. Could ESRI consider adding a method to the Polyline class for creating true-curve vertices?   ... View more

In the ArcPy Geometry Class documentation, could ESRI provide more detailed information about the hierarchical structure of gemetries? For example, provide a hierarchical diagram, kind of like we have for the SDE.ST_GEOMETRY spatial type, but for the ArcPy Geometry class: Like this, but better: - Geometry - PointGeometry - Multipoint - Point - Polygon - Ring (aka part) - Point - Polyline - Path (aka part) - Point That would help people who are trying to learn ArcPy understand how to access the various levels of the Geometry class. I know there is some info about that in the Cursor docs. But it doesn't explain the hierarchical structure of geometries. For example, as a novice, it was difficult to know how to iterate through a Polyline's components — to get at the individual points/vertices within a feature-part: import arcpy connection = "Database Connections\my_conn.sde" feature_class = connection + "\my_owner.my_fc" with arcpy.da.SearchCursor(feature_class, ["SHAPE@","OID@"]) as cursor: for row in cursor: geometry = row[0] print("Geometry/Polyline: {}".format(row[1])) for i, part in enumerate(geometry): print(" Part: {}".format(i)) for j, point in enumerate(part): print(" Point: {}".format(j)) >>> Geometry/Polyline: 100 Part: 0 Point: 0 Point: 1 Point: 2 Point: 3 Point: 4 Part: 1 Point: 0 Point: 1   It would help a lot if if we could get some more detailed information about the hierarchical structure. Thanks. ... View more

I have an ArcPy script that densifies polylines — to preserve any true curves that were in the features: (the curves become densified straight segments) with arcpy.da.UpdateCursor(fc, 'SHAPE') as cursor: for row in cursor: feature = row[0].densify ("ANGLE", 10000, 0.174533) #0.174533=radians Details: I don't want to densify straight segments, since that's not necessary here. I only want to densify the curved segments. So, in the densify function, I only really care about the TYPE and DEVIATION arguments. I don't need the DISTANCE argument, since all it seems to accomplish is adding vertices to straight segments (not what I want). densify (type, distance, {deviation}) densify ("ANGLE", 10000, 0.174533) #0.174533=radians With that said, I've noticed that the DISTANCE argument is mandatory. So I work around it by putting a dummy value of 10,000 meters in it, since there would never be a segment that big in my data. (I tried setting it to None but I got an error.) Question: Is there a reason why is the DISTANCE argument a required argument? Why can't it be optional, since for cases like mine, I don't want to specify it?   Have I misunderstood something? Thanks. ... View more

I have a multipart polyline FC that has true curves (Oracle 18c SDE.ST_GEOMETRY). I want to update the coordinates of the vertices in the lines via ArcPy — without losing the true curves: import arcpy connection = "Database Connections\my_conn.sde" feature_class = connection + "\my_owner.my_fc" spatial_reference = arcpy.Describe(feature_class).spatialReference with arcpy.da.Editor(connection) as edit_session: with arcpy.da.UpdateCursor(feature_class, "SHAPE@") as cursor: for row in cursor: geometry = row[0].densify("ANGLE", 10000, 0.174533) parts = arcpy.Array() for part in geometry: points = arcpy.Array() for point in part: point.M = geometry.measureOnLine(point) points.append(point) parts.append(points) row[0] = arcpy.Polyline(parts, spatial_reference) cursor.updateRow(row) The script reconstructs and replaces the geometry of the lines. So, unfortunately, it removes the true curves from the shapes. Before running script: After running script: Idea: Could ESRI consider giving us a clean way to edit vertices — without removing the true curves from the SHAPE?  - I don't want to densify the curves into straight segments...I want to keep the true curves.  - It would be ideal if there were a clean way to do this; not a workaround like converting to JSON and parsing out the curve info from the JSON text (would be messy/fragile). For example, a simple method like this would be helpful: UpdateVertex (shape, partNum, vertexNum, [z, m]) #It wouldn't replace the shape or replace the vertex. It would *update* a coordinate in the vertex. #So the true curves would remain intact. ... View more

Currently, it's not possible to determine if a SDE.ST_GEOMETRY line has true curves via SQL. For example, select lines where the SHAPE contains at least one true curve: Could ESRI consider adding a function to SDE.ST_GEOMETRY (Oracle) for this purpose? Something like: SDE.ST_HasCurves() Thanks. ... View more

It would be helpful if there were a out-of-box GP tool that could  batch-replace geometries from one FC to another — via a tabular relationship. Example: I have a polyline FC called FC-A. And I have an additional polyline FC called FC-B. I want to update the shapes in FC-A with the shapes from FC-B. I want to update the existing SHAPE values, without replacing the FC or replacing the records. The link between the two FCs is a tabular ID field. Currently, I don't think there are any tools that can do that.   ... View more

ArcGIS Enterprise/ArcMap 10.7.1 — Oracle 18c — SDE.ST_GEOMETRY I have a polyline FC called FC-A. And I have an additional polyline FC called FC-B. I want to update the shapes in FC-A with the shapes from FC-B. I want to update the existing SHAPE values, without replacing the FC or replacing the records. The link between the two FCs is a tabular ID field. I don't want to use a spatial relationship to link the two FCs. I think that would be unnecessarily messy. I've got a tabular relationship and I'd prefer to use it. Question: Are there any out-of-the-box tools in ArcMap that can batch-replace geometries from one FC to another via a tabular relationship? I know it would be possible with a SQL UPDATE script. But my users aren't SQL client users, so I'm looking for an OOB solution. ... View more

Oracle; SDE.ST_GEOMETRY: For existing SDE.ST_GEOMETRY polylines that have M-values (aka 'measure values' for linear referencing purposes). It would be really helpful if ESRI could add a ST_GEOMETRY SQL function that could be used to UPDATE the M-values to the cumulative length of line. In other words, if we look at the image below, the M-values would be updated so that they're the same as the length of the line at a given vertex.   Could ESRI consider adding a function for that? I believe it would be the equivalent of Oracle Spatial's REDEFINE_GEOM_SEGMENT function. Thanks. ... View more

ArcGIS 10.7.1; Oracle 18c; SDE.ST_GEOMETRY: I have existing SDE.ST_GEOMETRY polylines that have M-values (aka 'measure values' for linear referencing purposes). I want to UPDATE the M-values via Oracle SQL. In my case, the M-values should be the same as the cumulative length of the line. In other words, if we look at the image below, the M-values should be the same as the length of the line at a given vertex.   Using SQL, is there a way to set the M-values to the cumulative length of the line? I'm specifically looking for an Oracle SQL solution. Thanks.       ... View more