Latest Contributions by RichRuh

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

I think the single biggest thing you could do is use the Pro SDK to create your feature class.  There is a snippet showing how to do this here. You will need to create a feature layer for this feature class after filling it.  Assuming you don't need to have undo/redo work with this data, then I would forego the EditOperation as @GKmieliauskas suggests. The order would be: 1. Create the feature class in the in-memory geodatabase 2. Fill it in with InsertCursor 3. Create a feature layer and add it to the map I hope this helps, --Rich ... View more

Jack,  Would you mind posting some code snippets so that we can see what (if anything) you are doing wrong? --Rich ... View more

Jack, If you just want to stick with geoprocessing, here is a link for using geoprocessing with in-memory geodatabases (you don't even have to create it first). --Rich ... View more

If this custom file format is something you use frequently, you might want to consider writing a PlugIn datasource (Conceptual Doc, Guide). This would allow you to read and display the data in the map without needing to copy it into another format. If you want to stick with the current copying idea, shapefiles are good, but an in-memory database is probably better.  Instructions for creating an in-memory database are here. Once the database is created, you can create a feature class, and then copy data into it. If you go the route of using an in-memory database, keep in mind that they are destroyed when closing ArcGIS Pro. So if you create a layer from an in-memory database, that layer will come in broken if you save it in a map and restart Pro. I hope this helps, --Rich ... View more

The calls to the SchemaBuilder and the OpenDataset call should also be inside QueuedTask.Run() ... View more

I'm sorry, I forgot that step. After calling schemaBuilder.Build() you can get a FeatureClass pointer using Geodatabase.OpenDataset<FeatureClass>("SourcePackageFootprint"). ... View more

I'm not sure why the URI isn't accepted, but have you tried just creating the layer from the feature class itself? --Rich ... View more