Latest Contributions by EdwardBlair

‎07-31-2025

Thanks much for the reply! And for the great level of detail here. Our immediate though for introducing a substation tier was as a means to extract substation internals to our ADMS. Oracle NMS considers substations a distinct "partition" that we export substation internals (currently from an ArcGIS 10.x extractor process) using a query that returns features with a common "Sub FacilityID" field. Going forward we thought we might replace this with a subnetwork trace from the "injection points" on the high side of the station. Given the complexities described for substation tiers we may stick with our current logic of querying with a "Sub FacilityID" field. Thanks again!

‎07-30-2025

Nathan - Thanks much for the feedback. I knew about the dirty areas and the need to validate them, which I probably should have been more clear about. I suppose I should have phrased my question as, "does the validate topology" do everything we need? I've also discovered since I posted my question that there is a U/N GP tool for re-building topology that apparently is used to resolve issues that prevent "Validate Topology" from completing. This seems to be the rough equivalent of the ArcMap "Rebuild Connectivity" tool. Ed

‎07-29-2025

All - Like everyone maintaining a geometric network (at least everyone I know of) we occasionally find "corrupt network features" -- that is, features which, for whatever reason, have become disassociated with their logical network representation. When we find these we use the ArcMap "Rebuild Connectivity" to repair them. Since these occur seemingly at random in different parts of the database we created a process that runs weekly over different parts of the service territory and detects them, writing out a log which a GIS technician subsequently uses to seek out and repair. There are usually only a handful and sometimes none at all. But since they can cause unwanted behavior we feel its best to actively seek them rather than lie undetected. As we are starting to plan what functionality we need as we move to the U/N, the question has come up, so we still need to worry about network features becoming corrupt? And if so, do we need to continue to proactively seek these out and fix them. Any experience or insight would be much appreciated, Ed

‎07-20-2025

This helps a bunch! Thank you very much. Seemed odd that this would be considered a problem. Thanks for confirming it is not. Ed

‎07-19-2025

All - Working with a vendor we were told that the Utility Network would consider it invalid to have a structure network junction coincident with a utility domain device or junction. This seems illogical and I'm looking for a reality check. In our GN implementation we have separate underground structure and electric networks and many cases where an electric feature (i.e., a fuse) is coincident with an underground structure junction (i.e., a conduit end point). Any clarification here would be much appreciated. Thx, Ed

‎06-25-2025

Hi - We are starting discussion on out Utility Network model and are considering adding tiers for sub-transmission and substations. The sub-transmission tier would hold equipment energized at 34.5kV, 25 kV and 23kV - which are distinct from both transmission and distribution tiers. So we feel pretty safe there. But (we *think*) we also want a substation tier that encompasses equipment within the substation - with a subnetwork controller being one or more "injection points" on the high side of the sub. Of course the substation has equipment energized at transmission, distribution and sub-transmission voltage levels. So this would prevent the tiers from being in a consistent hierarchy -- for example sometimes sub-transmission will be on the "load" side of the sub and sometimes sub-transmission will be on the "feed" side of the sub. Will we run into problems with this tier definition? Has anyone configured tiers this way? Any pointers would be much appreciated. Thx, Ed

‎06-06-2025

So... as far as I can tell, this is a bug. However, I did find that another way to accomplish what I want to do is insert into the _EVW. Below is SQL that worked for me. Interestingly, the procedure "sde.next_globalid" works, while "sde.next_rowid" fails. And, apparently, when inserting into the _EVW the OBJECTID is generated as part of the "insert" operation. DECLARE @GID uniqueidentifier EXEC sde.next_globalid @GID OUTPUT INSERT INTO ASSEMBLY_EVW (GLOBALID,PARENTOBJECTID,UNIT,SUBTYPECD,QUANTITY,DATECREATED) VALUES (@gid,1408321,'UTSLV',5,1,GETDATE());

‎06-05-2025

I looked for bugs related to this problem and Gemini told me this: SQL Server Version: Problems with sde.next_rowid have been reported when using SQL statements to import data into an SQL Server SDE database, specifically with GeoDatabase version 10.8 and SQL Server version 2019. Now, I'm using ArcGIS 10.8.1 with SQL*Server version 2022, and I have more than once had Gemini lead me on a wild goose chase, but... any chance anyone knows what "problems" might be referring to? Thx, Ed

‎06-05-2025

David - Thanks for the reply. I had tried using INT prior to BIGINT. Same results. Ed

‎06-05-2025

Hi - I'm trying to use sde.next_rowid to get an OID for a new row to be created in a table registered and versioned within a SQL*Server 10.8.1 geodatabase. Here's my syntax: DECLARE @next_oid AS BIGINT EXEC sde.next_rowid 'gisadmin', 'ASSEMBLY', @next_oid OUTPUT Here's the error I receive: Msg 8144, Level 16, State 2, Procedure gisadmin.i36_get_ids, Line 0 [Batch Start Line 13] Procedure or function i36_get_ids has too many arguments specified. I'm afraid I'm stumped. The syntax I'm using matches what has been documented here (https://community.esri.com/t5/geodatabase-questions/using-sde-next-rowid-in-t-sql/td-p/761989) and other places. Any suggestions would be greatly appreciated. Thx, Ed

‎03-19-2025

Hi George - I do have an 10.8.1 client -- though its not identical to the 10.6.1 client. I tested creating a version with the 10.8 client on the 10.6.1 Geodatabase with the Geodatabase Administration too. This worked without error. I can't really say whether the problem occurred recently. Creating versions with the Geodatabase Administration tool is not part of our company's normal work flow. I happened to do it last week as part of a test. The problem may have been present a long time. ArcPro and the U/N is, as I'm sure you know, a big, costly decision and above my pay grade. Since we're moving to 10.8 soon and since we rarely create versions with the Geodatabase Admin tool, I may leave this sleeping dog lie. Though I might first take a look at other differences between the 10.6.1 and 10.8.1 clients. Thanks again for your help. Ed

‎03-19-2025

Right. This is ArcGIS 10.6.1. We'll be upgrading to 10.8.1 in a month. The DBMS is SQL*Server 2017. The database has a geometric network, so ArcGIS Pro does not apply. Thanks for the reply. Ed

‎03-19-2025

I should note that my steps to create the version are: 1. Open the Geodatabase Administration tool 2. Right-click on the SDE.Default version and select "New Version" 3. Complete the New Version dialog. The dialog disappears and Arc tries to think a little while before it gets stumped and crashes.

‎03-19-2025

... it also crashes in ArcMap. However, using the "Create New Version" tool in ArcMap works fine without error. Also, though the process of creating a new version in the "Geodatabase Administration" tool results in a rapid exit, the version is still created and seems to be no worse for wear. My hunch is that the error occurs when Arc is tying to reload the form's list of versions, *not* when trying to create the version itself. I say this because when I examine the resulting dmp file with WindDbg it looks like the error is raised from the Windows Presentation Framework (below). This could be completely off base, but any suggestions on how I might resolve this would be greatly appreciated. Thx, Ed STACK_TEXT: 00000000 00000000 ArcCatalog.exe!unknown_function+0x0 00000000 00000000 unknown![.ecxr]+0x0 00bddcd8 7736d652 KERNELBASE!RaiseException+0x62 00bddd3c 7393d9a1 clr!RaiseTheExceptionInternalOnly+0x27c 00bdddd8 7393e846 clr!IL_Throw+0x146 00bddea0 12c06e14 PresentationCore_ni!System.Windows.Automation.Peers.AutomationPeer.GetChildren+0x38c468 00bddec4 12879be1 PresentationCore_ni!System.Windows.Automation.Peers.AutomationPeer.isDescendantOf+0x19

‎03-18-2025

Is it possible that when we shut down the sync-enabled feature services that we also go into the system services and stop the sync geoprocessing service that this would prevent client requests from entering the queue? Ed

Online Status	Online
Date Last Visited	yesterday

My Ideas

Latest Contributions by EdwardBlair

Re: Electric Utility Network Subtransmission and Substation Tiers

Re: Corrupt network features in the U/N

Corrupt network features in the U/N

Re: Coincidence between utility domain and structure network features

Coincidence between utility domain and structure network features

Electric Utility Network Subtransmission and Substation Tiers

Re: SDE.next_rowid failing in SQL*Server

Re: SDE.next_rowid failing in SQL*Server

Re: SDE.next_rowid failing in SQL*Server

SDE.next_rowid failing in SQL*Server

Re: Create Version in "Geodatabase Administration" Tool Crashes ArcCatalog

Re: Create Version in "Geodatabase Administration" Tool Crashes ArcCatalog

Re: Create Version in "Geodatabase Administration" Tool Crashes ArcCatalog

Create Version in "Geodatabase Administration" Tool Crashes ArcCatalog

Re: Sync-enabled service sync requests when the service is down

Re: UPDM Gas Valve "Current Position" field

Electric Utility Network Subtransmission and Subst...

Re: Electric Utility Network Subtransmission and S...

Re: Coincidence between utility domain and structu...

Coincidence between utility domain and structure n...