|
POST
|
Is there an easy way to dynamically label a feature's vertex numbers in ArcGIS Pro? It would look like this: Ideally, it would use the zero-based numbering system — to be consistent with the vertex numbers in the Sketch window. Thanks.
... View more
06-08-2022
07:37 PM
|
1
|
6
|
3506
|
|
IDEA
|
For example, SDO_GEOMETRY provides a helpful error when validating that geometry: select
sdo_geom.validate_geometry_with_context(
sdo_geometry ('polygon ((676832.320 4857578.086, 665287.423 4857578.086, 665277.423 4878109.585,
676832.320 4878119.585, 676842.320 4857588.086))', 26917)
, 0.005)
from
dual
Result:
13348 [Element <1>] [Ring <1>] ORA-13348: polygon boundary is not closed Cause: The boundary of a polygon does not close.
... View more
06-08-2022
08:34 AM
|
0
|
0
|
1149
|
|
IDEA
|
Regarding the docs for the ST_GEOMETRY() constructor function: https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/st-geometry.htm Idea for improving the docs: When constructing a polygon via WKT: Could a blurb be added to the docs to make it clear that the last vertex of the polygon needs to be exactly the same as the first vertex of the polygon? I don't think the docs currently include that information. Key details like that would be very helpful when troubleshooting issues. I suppose this would apply to the ST_GeomFromText() function too, which does something similar to ST_Geometry().
... View more
06-08-2022
12:08 AM
|
1
|
2
|
958
|
|
IDEA
|
SDE.ST_GEOMETRY in Oracle 18c: If I were to create a polygon geometry from this incorrect WKT (the last vertex is slightly different from the first vertex, which is wrong), I would get the following error in SQL Developer: select
sde.st_geometry ('polygon ((676832.320 4857578.086, 665287.423 4857578.086, 665277.423 4878109.585,
676832.320 4878119.585, 676842.320 4857588.086))', 26917)
from
dual ORA-20004: --Note: I'm not sure why that junk symbol is being returned. ORA-06512: at "SDE.ST_GEOMETRY_SHAPELIB_PKG", line 12 ORA-06512: at "SDE.ST_GEOMETRY", line 55 That error message isn't very helpful. The problem is: the polygon doesn't close properly. But ST_GEOMETRY doesn't say anything to that effect. Could the ST_GEOMETRY error messages be improved? That would really help when troubleshooting issues.
... View more
06-08-2022
12:00 AM
|
1
|
1
|
1182
|
|
POST
|
Regarding the various spatial types that are supported by ArcGIS: What types auto-validate geometries? And what types don't auto-validate? For example, if I were to create a polygon geometry from this incorrect WKT (the last vertex is slightly different from the first vertex, which is wrong), what would happen? Would the incorrect geometry be accepted, or would it throw an error? --Example: SDE.ST_GEOMETRY select
sde.st_geometry ('polygon ((676832.320 4857578.086, 665287.423 4857578.086, 665277.423 4878109.585,
676832.320 4878119.585, 676842.320 4857588.086))', 26917)
from
dual ORA-20004: ORA-06512: at "SDE.ST_GEOMETRY_SHAPELIB_PKG", line 12 ORA-06512: at "SDE.ST_GEOMETRY", line 55 SDE.ST_GEOMETRY in Oracle: Auto-validates — would throw an error. SDO_GEOMETRY (Oracle): Doesn't auto-validate — doesn't throw an error, unless we explicitly perform a validation via a validation function(?). Others? Have I understood that correctly?
... View more
06-07-2022
11:36 PM
|
0
|
0
|
875
|
|
IDEA
|
SDE.ST_GEOMETRY in Oracle: I have two vertices of a rectangle: Lower-left: 10,10 Upper-right: 100,100 I want to construct a rectangle polygon from those two vertices using ST_GEOMETRY functions. Currently, there doesn't seem to be a a way to construct that rectangle using only the two vertices. It seems like the only way to construct the rectangle is to determine what all four (or five?) vertices are — and construct the rectangle that way. It would help if functionality could be added so that we could construct an ST_GEOMETRY rectangle from just the lower-left and upper-right vertices. Similar to what we can do with SDO_GEOMETRY's rectangle functionality: select sdo_geometry(2003, 26917, null, sdo_elem_info_array(1, 1003, 3), sdo_ordinate_array(665287.423,4857578.086, 676832.320,4878119.585)) -- only two vertices 🡅 🡅 from dual Result: [MDSYS.SDO_GEOMETRY]
... View more
06-07-2022
10:32 PM
|
0
|
0
|
561
|
|
POST
|
Does SDE.GDB_ITEMS_VW help you at all? Also, looking at the SQL definition of that view might be of interest.
... View more
06-06-2022
05:16 PM
|
0
|
0
|
1592
|
|
IDEA
|
In an item's properties in Catalog (tables, FCs, views, etc.): It would help if the item's creation date were available in the properties window. Possibly in the General tab. That would be helpful for data management purposes. I'm aware that the creation date can be gleaned from the db via SQL in a pinch. But that's inconvenient, not available to non-DBA users, and doesn't help us for non-enterprise GDBs. Out-of-the-box info in Pro would be better.
... View more
06-06-2022
11:56 AM
|
13
|
2
|
1150
|
|
POST
|
In the diagrams in the spatial grid index docs: Why are the grid cells parallelograms instead of rectangles? As a novice when it comes to indexing, I would have expected the grid cells to be right angles.
... View more
06-04-2022
01:23 PM
|
0
|
1
|
1234
|
|
POST
|
SDE.ST_GEOMETRY spatial indexes (in Oracle 18c): I’ve read that the indexes are domain indexes. I’ve also read that they’re grid indexes. Which is it? Or is it both? Thanks.
... View more
06-04-2022
01:13 PM
|
14
|
1
|
1027
|
|
POST
|
Oracle Feature classes that use ST_Geometry storage use a separate table to store information for the spatial index. The spatial index table is named S<n>_IDX$, where <n> is the geometry index value for the table. The geometry index value is stored in the SDE.ST_GEOMETRY_COLUMNS geodatabase system table. The spatial index table is created as an Oracle Indexed Organized Table (IOT). The spatial index on the ST_Geometry attribute appears as A<n>_IX1 when viewed through Oracle Enterprise Manager. The value of <n> represents the LAYER_ID value stored in the LAYERS geodatabase system table. Spatial indexes and ST_Geometry https://oracle-base.com/articles/8i/index-organized-tables Does that bolded blurb in the docs mean it’s possible to select the index data as rows in a query from the ST_GEOMETRY stpatial index? Like this: select * from _; spatial_index_data
----------------------
[ST_GEOMETRY shape]
[ST_GEOMETRY shape]
[ST_GEOMETRY shape]
[ST_GEOMETRY shape]
… Background: Get map to use function-based spatial index (ST_GEOMETRY) Thanks.
... View more
06-04-2022
11:55 AM
|
0
|
0
|
918
|
|
IDEA
|
Regarding registering a database view with the geodatabase - via the view’s properties in Catalog: Registering a view is painfully slow (minutes, not seconds). It’s not clear why it takes so long, since the operation is merely inserting a few rows into GDB system tables. Sure, the operation might be calculating the extents of the view, which can take some time. But calculating the extents is a lot faster when doing other things like adding a non-registered view directly to the map as a layer. So it seems weird that it would be so much slower when doing it via the register-with-GDB tool. Maybe it’s doing multiple extents-calculations or select *’s unnecessarily? Why is registering a view with the GDB so slow? Can it be improved?
... View more
06-04-2022
06:37 AM
|
0
|
0
|
445
|
|
POST
|
Your table or view must meet the following criteria to register it with the geodatabase: The field data types used in the table or view you register with the geodatabase must map to ArcGIS data types. If they do not, registration will fail. See DBMS data types supported in ArcGIS for a list of data types you can use. The table or view can contain only one spatial field. If the table or view contains a spatial field, it can store only one geometry type (such as point, line, or polygon). Register a table or view with the geodatabase
... View more
06-04-2022
06:19 AM
|
0
|
0
|
2110
|
|
POST
|
@George_Thompson Thanks! Side note: Is there a chance there's a small typo in your comment? Should "3000###" be "300###"? That's obviously not a big deal. I just thought there's a chance it could cause confusion for someone else reading this post.
... View more
06-03-2022
03:30 PM
|
0
|
1
|
4336
|
|
POST
|
ArcMap 10.7.1.: I've created a new point FC from scratch using Catalog (using all the default settings). The General tab mentions "Storage: High Precision": Whereas the Domain, Resolution and Tolerance tab mentions "XY Resolution": What's the difference between "Precision" and "XY Resolution". Thanks.
... View more
06-03-2022
03:19 PM
|
0
|
10
|
3179
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-20-2026 02:12 PM | |
| 1 | 03-19-2026 11:42 AM | |
| 1 | 06-03-2026 04:02 AM | |
| 1 | 03-18-2026 07:08 PM | |
| 2 | 07-08-2026 01:29 PM |