Latest Contributions by Bud

‎02-15-2021

It would be helpful if a timestamp column could be added to the SDE.GDB_ITEMS table (Oracle). Reason: So we can know when a GDB item, such as a domain, was last updated. Example: For integrations to external systems, we need to know if any domain descriptions have been changed, so that we can re-sync the data to the external system. Currently, there is no way to know if/when the values in a domain have been changed. Thank you.

‎02-08-2021

Please consider adding a midpoint attribute to the ST_GEOMETRY datatype (and a MIDPOINT accessor function). Otherwise, it is unnecessarily difficult to calculate the midpoint of a line using SQL/ST_GEOMETRY. Please note that the midpoint should be the true midpoint: half of the distance along the polyline (not the middle vertex, which would not be the true midpoint). Thank you.

‎01-23-2021

Is the view registered with the geodatabase? Can you tell us about the unique ID column? Is it 100% guaranteed to be unique? Is it based on a static column or is it generated/calculated? In ArcGIS Desktop, if you open the attribute table, and navigate to the last record, are you able to select all records? (I'm just trying to get a sense of what's working and what isn't.) I had similar issues. It happened after I made a change to the SQL of a registered view. In my case, I dropped the view and recreated it, and re-registered it. That seemed to fix my selection issues.

‎01-06-2021

Oh, you poor soul! My team has spent the last 1.5 years trying to get Maximo Spatial working properly. After dozens of bug reports and hundreds of hours of effort, it's still not working quite right. Unfortunately, I can't help with the token stuff (I'm not the map service administrator in my organization), but you could try: 1. Asking IBM support 2. Posting a question on the Maximo Spatial Community forum 3. Asking IBM staff directly (such as jmaior@br.ibm.com) Good luck.

‎12-11-2020

I want to create an Oracle 18c materialized view with the fast refresh option on a remote table (in an enterprise GDB). I can do this successfully without a SHAPE column: create materialized view log on source_system.workorder with primary key; grant select source_system.mlog$_workorder to schema_for_dblink; create materialized view my_gis_schema.wo_mv build immediate refresh fast start with sysdate next sysdate + (15/(60*60*24)) as select cast(workorderid as number(38,0)) as objectid, --workorderid is a fake primary key; it has a NOT NULL constraint and a unique index wonum, status, --other fields longitudex, latitudey from source_system.workorder@my_dblink Problem: I want to store the XY coordinates from the source table in a SHAPE column in the MV. Unfortunately, my options seem pretty limited: Oracle doesn’t seem to support SDE.ST_GEOMETRY in MVs (more info here and here). The SQL would be: sde.st_geometry(longitudex,latitudey,null,null, 26917 ) as shape Additionally, Oracle doesn't seem to support SDO_GEOMETRY in MVs on a remote table with the fast refresh option: ORA-12015: cannot create a fast refresh materialized view from a complex query The SQL would be: sdo_geometry(2001, 26917, sdo_point_type(longitudex,latitudey, null), null, null) as shape Question: Is there a way to include a SHAPE column in a materialized view on a remote table with the fast refresh option?

‎08-29-2020

CREATE OR REPLACE TRIGGER D202574_custom BEFORE INSERT ON D202574 FOR EACH ROW DECLARE v_upd_row NUMBER; BEGIN SELECT COUNT(1) INTO v_upd_row FROM A202574 WHERE objectid = :new.sde_deletes_row_id AND sde_state_id = :new.deleted_at; IF v_upd_row = 0 THEN raise_application_error(-20001, 'Deleting has been disabled via a custom trigger.'); END IF; END ;

‎08-26-2020

Kyle Johnson‌ Melanie Williams

‎08-26-2020

Solved: Steps for accessing edited features' attributes from an AGOL webhook URL: AGOL webhook to Integromat/Google Sheets

‎08-22-2020

In unversioned feature classes, we can control privileges through Catalog for SELECT, INSERT, UPDATE, DELETE (using any combination). However, with versioned feature classes, we can only control INSERT, UPDATE, and DELETE as a group (all-or-nothing). We can't allow INSERTS and UPDATES, yet prevent DELETES. It would be great if we could prevent just DELETES in versioned feature classes. Thanks!

‎08-10-2020

In the attribute table of a point feature class in ArcGIS Pro: Give users the option to turn on dynamic, read-only columns that represent each feature's X and Y coordinates. The fields would have similar properties to that of the SHAPE column in the attribute table. This would be helpful for day-to-day GIS analysis activities. And would eliminate the need for users to calculate or generate the X and Y columns themselves.

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by Bud

Add a timestamp column to GDB_ITEMS table (Oracle)

Polyline midpoint: ST_GEOEMTRY

Re: Can't select on a spatial view

Re: Integrate ArcGIS Enterprise with Maximo Spatial

Materialized view with FAST refresh on remote table: How to include a SHAPE column?

Re: Prevent deletes in versioned feature classes

Re: ArcGIS Online Hosted Feature Service Notification on new record/feature added

Re: ArcGIS Online Hosted Feature Service Notification on new record/feature added

Prevent deletes in versioned feature classes

Dynamic columns in attribute table to show XY (ArcGIS Pro)