Latest Contributions by Bud

It looks like the FD's XY Resolution and XY Tolerance are wrong. I don't think those values should be so small...I'm guessing they should be set to what the FC has (0.0001 and 0.001) which are likely the defaults. I'll look into fixing the FD. I don't imagine it'll be easy. ... View more

Good idea. See:  Improve error messaging when moving FC to FD due spatial reference mismatch https://community.esri.com/t5/arcgis-pro-ideas/improve-error-messaging-when-moving-fc-to-fd-due/idi-p/1183977/ ... View more

Yeah, that's the source of my query. I mention it in the link in the original post. ... View more

I suppose one way to do it would be to modify the existing query: Details: (1) Keep only the horizontal lines. Exclude the vertical lines. where startpoint_y = endpoint_y Here's a sample horizontal line: OBJECTID STARTPOINT_X STARTPOINT_Y ENDPOINT_X ENDPOINT_Y SHAPE ---------- ------------ ------------ ---------- ---------- -------------- 219 0 0 0 1 [SDO_GEOMETRY] (2) Add an additional outer query where we generate 5 vertices (a polygon) from the existing 2 vertices (from the original horizontal line): startpoint_x, --vertex 1 (original vertex from the horizontal line) startpoint_y, endpoint_x, --vertex 2 (original vertex from the horizontal line) endpoint_y, endpoint_x, --vertex 3 endpoint_y+1, startpoint_x, --vertex 4 startpoint_y+1, startpoint_x, --vertex 5 (same as vertex 1) https://gis.stackexchange.com/q/433083/62572 startpoint_y, (3) Just like with the lines query, construct a polygon geometry by concatenating the coordinates together into WKT. sdo_geometry('polygon(('||startpoint_x||' '||startpoint_y||', '||endpoint_x||' '||endpoint_y||', '||endpoint_x||' '||(endpoint_y+1)||', '||startpoint_x||' '||(startpoint_y+1)||', '||startpoint_x||' '||startpoint_y||'))',26917) as shape (4) Now, the coordinates look like this (the vertex direction is counterclockwise; vertex 1 and 5 are both 0,0): (5) This is what the full query looks like: --create or replace view sdo_geom_grid_polygons_vw as ( select objectid, 'polygon(('||startpoint_x||' '||startpoint_y||', '||endpoint_x||' '||endpoint_y||', '||endpoint_x||' '||(endpoint_y+1)||', '||startpoint_x||' '||(startpoint_y+1)||', '||startpoint_x||' '||startpoint_y||'))' as wkt, sdo_geometry('polygon(('||startpoint_x||' '||startpoint_y||', '||endpoint_x||' '||endpoint_y||', '||endpoint_x||' '||(endpoint_y+1)||', '||startpoint_x||' '||(startpoint_y+1)||', '||startpoint_x||' '||startpoint_y||'))',26917) as shape from ( with dimension as ( select 0 as point from dual union all select level from dual connect by level <= 10 ), points as ( select a.point as startpoint, b.point as endpoint, c.point as fixed from dimension a cross join dimension b cross join dimension c where b.point - a.point = 1 ) select cast(rownum as number(38,0)) as objectid, startpoint_x, startpoint_y, endpoint_x, endpoint_y from ( select startpoint as startpoint_x, fixed as startpoint_y, endpoint as endpoint_x, fixed as endpoint_y from points union all select fixed as startpoint_x, startpoint as startpoint_y, fixed as endpoint_x, endpoint as endpoint_y from points ) order by startpoint_x, startpoint_y, endpoint_x, endpoint_y ) where startpoint_y = endpoint_y --get horizontal lines only --);   ... View more

@DanPatterson As you mentioned, Z-values aren't enabled in the ArcToolbox GP tool, so that's good. I find it easier to use the Catalog method...but good to be reminded of the GP tool too.   ... View more

That's an interesting idea. If I understand correctly, I think you're saying we could: ...reference those "Geometry Attributes" (fields in the attribute table but not in the underlying db table) right in Arcade. I think I've done the same sort of thing with the  $feature.shape_length:  https://community.esri.com/t5/arcgis-pro-ideas/hascurve-arcade-geometry-property/idc-p/1149449/highlight/true#M18873  Is that what you were thinking? Never mind. Those "Geometry Attribute" fields aren't dynamic. Add Geometry Attributes (Data Management) The values in these fields are not automatically recalculated after edits. If you edit the features, you'll need to run this tool again to update the field values.   ... View more