Latest Contributions by ThomasEmge

Correct, the view understanding for Pro has been unified such that the code for 2D and 3D is essentially the same or very similar. For more information please take a look at the concept documentation for map exploration ProConcepts Map Exploration · Esri/arcgis-pro-sdk Wiki · GitHub ... View more

Luke, you were stating earlier that the field remains <null>. Depending on when and where you are checking the changed attribute value the invalidate is required as Pro might be showing you a cached state of the data and unless you invalidate the cached state is considered the current state. Please do take a look at ArcGIS Pro 1.2 API Reference Guide for the overloaded Create method. We have method signatures that accept a table as an argument. A feature class is inheriting from table so you can have multiple feature classes participate in a single edit operation regardless if they are shown in the map or not. Please keep in mind that you will still need to save the edits done by the edit operation in order to be persisted in the geodatabase. The alternative is ArcGIS Pro 1.2 API Reference Guide which is new at 1.2 and is happening as a single source on the geodatabase. Thomas ... View more

Luke, please do take a look at the sample code again. I believe you are missing the context.invalidate call. However for just changing a single attribute using the callback approach is overkill. A single edit operation with multiple Modify calls should suffice. Thomas ... View more

You have a condition on the button declaration that takes precedence and is redundant if you would like to use the Command pattern. The CanOnMyCustomButtonClick in your example will take the role of the condition. Please take a look at this example https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Map-Exploration/FeatureSelection/FeatureSelection on the syntax and usage. ... View more

Ben, please take a look at this editing sample https://github.com/Esri/arcgis-pro-sdk-community-samples/tree/master/Editing/EventModule It does attribute changes based on editing events. It might be a good starting point and require only minor tweaking to fit your definition for 'session' and 'job'. ... View more

My mistake, the first argument is the target table. using ArcGIS.Desktop.Core.Geoprocessing;  await QueuedTask.Run(() =>      {          Geoprocessing.ExecuteToolAsync("AddField_management", Geoprocessing.MakeValueArray(@"c:\temp\demo.gdb\sample", "FieldName", "LONG", 9));      }); When you are working with layers in your map this would be that way to get the location: FeatureLayer firstLayer = MapView.Active.Map.Layers.OfType<FeatureLayer>().FirstOrDefault(); await QueuedTask.Run(() => { FeatureClass fc = firstLayer.GetTable() as FeatureClass; Datastore ds = fc.GetDatastore(); string dc = ds.GetConnectionString(); if (ds is Geodatabase) {   Geodatabase gdb = fc.GetDatastore() as Geodatabase;   string gdbPath = gdb.GetPath(); } string name = fc.GetName(); }); ... View more

You are not missing anything in the API. The API is designed following the data manipulation language (DML). In order to add a field you would make a call using geoprocessing such as using ArcGIS.Desktop.Core.Geoprocessing; await QueuedTask.Run(() =>     {         Geoprocessing.ExecuteToolAsync("AddField_management", Geoprocessing.MakeValueArray("FieldName", "LONG", 9));     }); ... View more

Adam, if you await any of the async functions, you are essentially writing sequentially executed code. The fact that the functionality of the async methods is going of to spin up new threads or does whatever it needs to do is kind of not relevant. This line in code will not advance until the layer is generated and added to the container. await QueuedTask.Run(() => {     LayerFactory.CreateLayer(new Uri(Path.Combine(CoreModule.CurrentProject.DefaultGeodatabasePath, "Sample")), MapView.Active.Map); }); You can choose not to await the XXAsync methods, however that choice depends on your code/workflow logic. One of the reasons for Pro is to free the UI thread from business logic and always stay responsive. ... View more

Adam, here is the code to do it. The caveat here is that this approach is not recommended for versioned data. QueuedTask.Run(() =>     {         string gdbPath = CoreModule.CurrentProject.DefaultGeodatabasePath;         Geodatabase gdb = new Geodatabase(gdbPath);         var featureClass = gdb.OpenDataset<FeatureClass>("Sample");         var featureBuffer = featureClass.CreateRowBuffer();         var newFeature = featureClass.CreateRow(featureBuffer) as Feature;         newFeature.SetShape(pointGeometry);         newFeature.Store();     }); ... View more

We have 'ProSnippets' as part of the wiki at https://github.com/esri/arcgis-pro-sdk/wiki next to the concepts. You can find the geometry snippets at https://github.com/esri/arcgis-pro-sdk/wiki/ProSnippets-Geometry ... View more