Latest Contributions by Bud

Oracle 18c SDE.ST_GEOMETRY EGDB: Has anyone ever tried adding additional "attributes" to an ST_GEOMETRY object column? Such as adding an SDO_GEOMETRY attribute to the object column: ENTITY NUMBER(38) NUMPTS NUMBER(38) MINX FLOAT(64) MINY FLOAT(64) MAXX FLOAT(64) MAXY FLOAT(64) MINZ FLOAT(64) MAXZ FLOAT(64) MINM FLOAT(64) MAXM FLOAT(64) AREA FLOAT(64) LEN FLOAT(64) SRID NUMBER(38) POINTS BLOB SDO_GEOM SDO_GEOMETRY Source: ST_Geometry in Oracle Or, alternatively, add an additional "subtype" to the object supertype. Sure, it wouldn't be supported. But that's not what I'm asking about. I'm asking if anyone has tried it. Reason: I want to use Oracle Spatial linear referencing functionality, but can't switch my FCs from ST_GEOMETRY over to SDO_GOMETRY. We can't add additional geometry columns to a FC (causes errors). And I want to avoid creating dozens of helper SDO_GEOMETRY FCs if I can help it. Thanks. ... View more

If I make a change to a feature class's properties in Catalog, such as renaming it or registering it as versioned, then Catalog refreshes the list of FCs in the connection, and navigates away from the  FC (to the top of the list). That's fairly aggravating. We have to scroll through the list of hundreds of objects in the EGDB to find the FC to resume what we were doing. If the operation takes a couple of minutes, we might even forget what we were doing by the time it refreshes. Or when we go to navigate back to the object, we might accidently go to the wrong object. Little things like that could be avoided if Catalog didn't navigate away from the object in the first place. I understand why it would need to refresh after a change. But it would be better if Catalog could scroll back to the FC and re-select it. Or just refresh the affected object(s), instead of the entire list, avoiding the need to navigate away from the object. Could Catalog be enhanced so that it doesn't navigate away from an object after a change is made? ... View more

Is there a way to set a default projection when creating new feature classes? (enterprise GDB) 100.0% of our feature classes are NAD83 UTM 17N. I never need to create a FC with a different projection. So it would be nice if I could set a default. I create projects/maps from scratch, without any default layers, so I don't think Pro could grab the projection from any existing info in the project/map. ... View more

Regarding SDE.ST_GEOMETRY shape object columns (Oracle): Rumor has it, true curve info (aka CAD blob data) is stored separately from ST_GEOMETRY info — all within the same shape object/column. In other words, if we query the geometry via ST_GEOMETRY functions, we don't have access to true curve data, since it's stored in a separate object attribute (an LOB attribute). (I imagine the wording above is wrong, but that's because I don't have any documentation to reference.) Could information about the above be added to the docs? Otherwise, I'm just fumbling around in the dark. I know the usual suspects are likely to say, "You can't access the CAD blob via ST_GEOMETRY anyway, so it's a moot point." That might be, but I still need to understand how it's been set up...so I can understand what the limitations are and how to work around them. For example, I need to understand how ST_GEOMETRY pre-densifies the true curves into straight segments. What logic is used for the pre-densification?   Edit - Related: Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB? ... View more

The ArcGIS Oracle privileges doc —> DATA CREATOR section should include CREATE INDEX privilege info: Privileges for using ArcGIS with an Oracle database  CREATE INDEX is an important privilege for data creators. Especially since we can use it to create function-based indexes (spatial and non-spatial). Omitting that privilege from the doc seems like an oversight. ... View more

There seem to be three different wordings for converting XY data to points: 1. Right click layer in TOC --> "Display XY Data" Bud_0-1657293569312.png I find that wording to be misleading. The word "display" makes it sound like we're creating a dynamic event layer, which isn't the case. It creates a new feature class. I know the info in the mouseover explains it a bit further. But I honestly don't usually think to hover/wait/read the mouseover text. Could the "Display XY Data" wording be improved? 2. Ribbon --> Map tab --> "XY Point Data": Bud_1-1657293748897.png The wording in the subscript is misleading. We're not simply "Adding x,y point data to the map". We're creating a feature class.  3. Ribbon --> Analysis --> Tools --> Search for "XY" --> "XY Table to Point" GP tool. Bud_2-1657293861843.png Bud_3-1657293877181.png This tool is pretty straightforward. It creates a new feature class, which is clearly stated in the tool description. And is obvious because we need to fill in the "Output Feature Class" parameter. Note: The three options above are not to be confused with the "Make XY Event Layer" GP tool, which creates a dynamic event layer, not a feature class. Bud_4-1657294402148.png Idea: If I understand correctly, all three options use the same underlying GP tool: "XY Table to Point". Bud_3-1657293877181.png If all three options do the same thing, then why not use consistent wording, to avoid confusion from the user? And why not make it crystal clear that all three options create a new FC? Feel free to let me know if I've misunderstood something. Cheers. ... View more