Latest Contributions by RichRuh

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

@Zoggo  Here is a snippet showing how to create a memory geodatabase. Once you have created the geodatabase, here is a snippet showing how to create a feature class. I hope this helps, --Rich   ... View more

It still feels like a threading problem to me.   First, each of these processes is finishing before it executes a second time, right? Second, have you tried calling Dispose on each of the geodatabase objects (including the version manager, any version objects you create, feature classes, cursors, rows, etc.), or use `using` statements?  If you don't clean them up, it's possible that one thread is creating them and another thread is reusing them (the objects might be cached internally). Other than that, I'm out of ideas.   ... View more

One more thing to try if you're still willing.  What happens if you call ArcGISSignOn.IsSignedOn prior to the call to VersionManager.GetVersionNames()?  I'm guessing it returns True in those cases where GetVersionNames succeeds, and returns False in those cases where it fails, but it would be good to know for sure.  ... View more