Latest Contributions by RichRuh

Hi Logan, The Trace geoprocessing tool now has an option to return connectivity as JSON. You will have to parse the JSON yourself.   The Pro SDK does not yet support this option, although you can always call the tool using the geoprocessing API. Our goal when we do support it is to return an object structure, not unformatted JSON. As for ordering, I've not heard of any options there, but I can pass it on to the utility network team. --Rich ... View more

Pro (not just the SDK) does have a timeout that defaults to 3 minutes. I suggest working with tech support to figure out why the queries are taking that long- sounds like something could be wrong there. --Rich ... View more

It's always possible to access Esri REST services such as the feature service outside of the Pro SDK. I'm not familiar with the benefits of that solution, although the integration with Pro would obviously be harder. ... View more

Calling OpenDataset does not download the contents of the table- just some metadata about the table definition.  The only data that is downloaded are the rows specified by the QueryFilter in Table.Search. --Rich ... View more

Hi MKa, I assume these portal tables are part of a feature service, right? Start by creating a connection to the feature service, and then creating a Geodatabase from that connection. You can accomplish this by creating a ServiceConnectionProperties object, and then using the Geodatabase(ServiceConnectionProperties) constructor. Once you have a Geodatabase, you can open tables and query using OpenDataset and Search. I hope this helps, --Rich ... View more

Unfortunately there is no support for creating a Database from an OLE DB connection. ... View more

Thanks for letting me know, Karen. We'll take a look at it- might be a bug. Glad you found a workaround at least. --Rich ... View more

Hi Karen, Geoprocessing only knows how to work with a single memory geodatabase- the one called "memory".  You can execute your copy like this: var parameters = Geoprocessing.MakeValueArray(@"C:\Users\kbmeinstein\Desktop\DeformTest\50Ma_Pro_Deftest_model_save.gdb\DefMotion_50Ma", @"in_memory\test"); IGPResult result = await Geoprocessing.ExecuteToolAsync("FeatureClassToFeatureClass_conversion", parameters, null, null, null, GPExecuteToolFlags.AddOutputsToMap); If you later need to access this new table using the Pro SDK, you can do so with the following code: MemoryConnectionProperties memoryConnectionProperties = new MemoryConnectionProperties(); Geodatabase geodatabase = SchemaBuilder.CreateGeodatabase(memoryConnectionProperties); FeatureClass testFeatureClass = geodatabase.OpenDataset<FeatureClass>("test"); (In this instance, the CreateGeodatabase call doesn't really create a new geodatabase, but rather returns a connection to the existing memory geodatabase.) I hope this helps, --Rich ... View more

@KenBuja Yes. You can now use the Pro SDK to create a geodatabase in memory, and then create tables and feature classes within that geodatabase.  Details are here.  You can create a layer from a memory feature class like any other. Just note that the memory feature class goes away when the Pro session ends- so if you save those layers into a APRX file, they will show as disconnected when reloading the project. ... View more

Now let's talk about this line...  if (featureLayer.Name.Contains("ASSEMBLY")) When you define your utility network schema, you can set the association deletion semantics for a container or structure type. You can see these in the Network Properties dialog that you can get by right-clicking on the utility network layer. There are three values for this setting: None. When you delete the container, the association is automatically deleted. The content features are left behind (no longer part of the container) Cascade. When you delete the container, the content features are automatically deleted with it (and the containment associations between them, naturally).  Restrict. You are unable to delete the container without first deleting the content.  This is the scenario you are dealing with above. Now the reason this setting exists is to prevent users from accidentally deleting a container that contains a large number of features- like a large switching cabinet or even a substation.   I would consider two things. 1. Instead of looking for the name "Assembly", ask the feature if it is a container and, if so, what is the association deletion semantics. You can do this as follows: bool needToDeleteAssociations = false; Element element = un.CreateElement(tempFeat); AssetType assetType = element.AssetType; if (assetType.AssociationRoleType == AssociationRoleType.Container) {   if (assetType.AssociationDeletionSemantics == AssociationDeleteType.Restricted) {     needToDeleteAssociations = true;   } } (Structures can have association deletion semantics too) 2. The second thing to consider is... should you be doing this? The schema was defined to restrict deletion of these containers. Was it intentional?  If so, your code is... well... subverting that setting. If it wasn't intentional, maybe the right solution isn't to write any code at all but to change the schema to not have this setting... I can't answer the question for you, but I would encourage you to ask it if you haven't already. --Rich     ... View more