Latest Contributions by Bud

‎06-15-2022

This example might be helpful to some people: Arcade Code Review: Set polyline M-values to cumulative length of line

‎06-15-2022

What are the steps needed to convert a Oracle table to a FC in an EGDB? For example: 1. Take an existing Oracle table. 2. Add a geometry column if needed. 3. If it's an SDO_GEOMETRY column, then register with USER_SDO_GEOM_METADATA? 4. Add a spatial index using the Add Spatial Index GP tool? 5. Register with the geodatabase using Catalog in ArcMap? 6. Other? I've tried various combinations of the above steps, but I often have problems like the resulting FC's attribute table is empty when I view it in ArcMap. Or the spatial reference is broken. Or the geometry type (point/line/polygon) isn't properly defined, etc. I usually give up at that point and try something else, like create an empty FC via ArcMap, create a spatial view on the Oracle table, and then use the Load tool in Catalog to load the data into the empty FC. But that's pretty clunky...I'm hoping there's a better way. Thanks.

‎06-15-2022

Yeah, could be. Although, as a "Regular Contributor"/non-Esri staff person, I'm not aware of any special powers that I have. And the person who accidently did it to me today is a "New Contributor II"/non-Esri staff member. So in those two cases, my guess is neither of us have special ranking/abilities.

‎06-15-2022

Why do I have the ability to accept a solution in someone else's post? It seems weird to me that people can accept answers to other people's questions. For example, I've had it a couple of times where someone accepted the answer to one of my posts...before I even had a chance to read the answers and decide which one worked best. I actually found it kind of off-putting, so I asked those people about it, and it turned out they did it by accident (they meant to hit the kudos button instead). Do we like that functionality? Is it meant to be like that?

‎06-15-2022

In ArcMap, using the Load tool in Catalog, we had a window that let us do field matching: That functionality was extremely useful. The input fields don't always match the target fields, so the matching window let us manually set up the field mapping as needed. That was a huge improvement over the Append tool. Does ArcGIS Pro have equivalent functionality?

‎06-14-2022

I have a multipart polyline FC in an SDE.ST_GEOMETRY EGDB (Oracle 18c). For testing purposes, I want to create a new polyline FC that only has the first segment of the original lines. For multi-part features, I want to ignore the additional parts. For example, I don't want to get the first segment of the second part. It's a one-time operation, so using geoprocessing tools would be fine (no need for automation or custom scripting). How can I do that using ArcGIS Pro 2.6.8 or ArcMap 10.7.1? (advanced license)

‎06-14-2022

Edited to make it clear that this idea pertains to an editing session, not a layer's label properties. It would be helpful if there were an optional setting where we could see vertex numbers on nodes while editing. It would look like this: Could that be added as an optional setting in ArcGIS Pro? A different, but related idea here: Vertex number as dynamic labels (in a layer's label properties)

‎06-14-2022

Here's one way of doing it: --create or replace view sdo_geom_grid_vw as ( --select * 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, sdo_geometry('linestring('||startpoint_x||' '||startpoint_y||', '||endpoint_x||' '||endpoint_y||')',26917) as shape 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 --)) OBJECTID STARTPOINT_X STARTPOINT_Y ENDPOINT_X ENDPOINT_Y SHAPE ---------- ------------ ------------ ---------- ---------- -------------- 219 0 0 0 1 [SDO_GEOMETRY] 109 0 0 1 0 [SDO_GEOMETRY] 208 0 1 0 2 [SDO_GEOMETRY] 108 0 1 1 1 [SDO_GEOMETRY] 120 0 2 0 3 [SDO_GEOMETRY] 99 0 2 1 2 [SDO_GEOMETRY] Notes: Source: https://stackoverflow.com/questions/72620062/generate-grid-line-coordinates-using-sql Related: Oracle Spatial Community - Generate grid line coordinates The query currently produces SDO_GEOMETRY shapes. But it can very easily be adapted to generate SDE.ST_GEOMETRY shapes — since it converts the coordinates to shapes via WKT (supported by both geometry types). Just change sdo_geometry( —to— sde.st_geometry( in the outer query. When I added the query as a view to ArcMap, selecting the features was very buggy. For example, if I selected a few rows of cells at the top of the grid, ArcMap would also select a few random rows/cells at the bottom of the grid too, which was incorrect. That seems to be a problem in general with spatial views in ArcGIS. I was able to solve that problem by registering the view with the GDB. I had the same problem with both SDO_GEOMETRY and SDE.ST_GEOMETRY views. Registering the view solved it for both datatypes.

‎06-14-2022

Oracle 18c: Using an SQL query, I want to generate square grid graph features: The underlying vertices would look like this: STARTPOINT_X STARTPOINT_Y ENDPOINT_X ENDPOINT_Y SHAPE ------------ ------------ ---------- ---------- ---------- 0 0 1 0 [SHAPE] --horizontal lines 1 0 2 0 [SHAPE] 2 0 3 0 [SHAPE] 3 0 4 0 [SHAPE] 4 0 5 0 [SHAPE] 5 0 6 0 [SHAPE] ... 0 0 0 1 [SHAPE] --vertical lines 0 1 0 2 [SHAPE] 0 2 0 3 [SHAPE] 0 3 0 4 [SHAPE] 0 4 0 5 [SHAPE] 0 5 0 6 [SHAPE] ... [220 rows selected] Details: The lines would be split at each intersection. So, in the image above, there are 220 lines. Each line is composed of two vertices. Ideally, I would have the option of specifying in the query what the overall grid dimensions would be. For example, specify this somewhere in the SQL: DIMENSIONS = 10 x 10 (or DIMENSIONS = 100 x 100, etc.). To keep things simple, we can: Assume the grid's overall shape will always be a square (length = width). For the purpose of this question, we can make the cell size 1 unit. And the grid can start at 0,0 and be built "up and right" (to the northeast). I've supplied sample data in this db<>fiddle (non-spatial XY coordinates). I created that data using Excel. Hint: The vertical grid lines start at row 111. The reason I want to generate this data is: I want sample line data to work with when testing Oracle Spatial queries. Sometimes I need a few hundred lines. Other times, I need thousands of lines. And I need to share the data online via https://dbfiddle.uk, so I can't use real/proprietary GIS data. Also, if the lines are in a grid pattern, then it will be obvious if any lines are missing in my analysis results (by looking for gaps in the data in a map). I'm aware that there are ways to do this with ArcGIS tools. In this case, I want to do it using SQL. How can I generate those grid lines using Oracle SQL?

‎06-13-2022

I think both options you mentioned would be useful: Vertices be labelled in EDIT mode Vertices be labelled in non-edit mode (as part of a layer's labels) Regarding the risk you mentioned, I suppose we could handle that by setting a scale tolerance on the labels in the layer. I.e. only show the labels when zoomed in to at least 1,000 scale, or whatever is appropriate.

‎06-12-2022

As a non-DBA/developer, I’ve always found resources about SQL joins to be clunky. I came across a resource recently that I found helpful: https://oracle-base.com/articles/misc/sql-for-beginners-joins [INNER] JOIN ... ON LEFT [OUTER] JOIN RIGHT [OUTER] JOIN FULL [OUTER] JOIN CROSS JOIN NATURAL JOIN [INNER] JOIN ... USING Additional Joins One thing I like about that list is: it accounts for join name synonyms (variations in join names) via the words in brackets. Another thing I like: the list of join types is actually complete (unlike most join lists). For example, it includes information about CROSS JOIN LATERAL in the Additional Joins link, which is a join type that’s often overlooked (use case here). In general, I really like oracle-base.com. It’s much better than the Oracle docs, which seems to be missing a lot of key information, are hard to read, and out-of-date. And seem to be meant for people who are already experts on the content. Whereas oracle-base.com is the opposite of all those things. Many people will already know about that resource, but some might not, so I thought I’d share. Cheers.

Re: Esri Community Team's New Members · ‎06-10-2022

@JesseCloutier I camped in leaf-off poison ivy last year. And managed to rub it in my eyes, mouth, and ears. I feel your pain.

Re: Esri Community Team's New Members · ‎06-09-2022

Welcome! I am an active member. You will soon hate me. 🙂

‎06-09-2022

Edited to make it clear that this idea pertains to a layer's label properties, not an editing session. It would be helpful if there were an easy way to dynamically label a feature's vertex numbers in a layer's label properties. Could that be added as OOTB functionality in ArcGIS Pro? A different, but related idea here: Display vertex numbers on nodes while editing

‎06-08-2022

I've created a polygon in an Oracle 18c SDO_GEOMETRY FC via ArcMap. In ArcMap, the vertices are displayed in the direction that I drew them: clockwise. However, if I query the data via SQL, then the vertices are listed in counterclockwise order: select t.x, t.y from sdo_polygons p cross join sdo_util.getvertices(p.shape) t --https://stackoverflow.com/q/72590279/5576771 ID X Y -- -- -- 1 10 10 2 20 10 3 20 20 4 10 20 5 10 10 Questions: Why is there a difference in the vertex order — between ArcMap and SQL? Are two different sets of vertices stored within a single feature? Related: I happen to be aware of an Oracle error message that suggests that SDO_GOMETRY polygons need to be counterclockwise: ORA-13367: wrong orientation for interior/exterior rings Cause: In an Oracle Spatial geometry, the exterior and/or interior rings are not oriented correctly. Action: Be sure that the exterior rings are oriented counterclockwise and the interior rings are oriented clockwise. Oracle Spatial Community: Why do polygon vertices need to be counterclockwise? GIS SE: Order of polygon vertices in general GIS: clockwise or counterclockwise

My Ideas

Latest Contributions by Bud

Re: Arcade: Get paths array from feature — why so much overhead?

Convert a Oracle table to a feature class?

Re: Why do I have the ability to accept a solution in someone else's post?

Why do I have the ability to accept a solution in someone else's post?

Catalog Load tool: Field matching functionality

Extract first segment of polylines

Display vertex numbers on nodes while editing

Re: Generate grid line features using SQL

Generate grid line features using SQL

Re: Dynamic vertex number labels

Learning about Oracle JOIN types, etc.

Re: Esri Community Team's New Members

Re: Esri Community Team's New Members

Vertex number as dynamic labels (in a layer's label properties)

SDO_GEOMETRY polygon: Vertices are clockwise in ArcMap, but counterclockwise in SQL

Integrate ArcGIS Data Pipelines in ArcGIS Enterpri...

Send configurable email notifications from ArcGIS ...

Re: How reliable are ArcGIS Online webhooks?

How reliable are ArcGIS Online webhooks?

Sharepoint List Connector

GIS Jobs

Roads and Highways User Group (RHUG)

Local Government Solutions Users

Mapping and Charting Enterprise Databases

ArcGIS Arcade