Latest Contributions by NarelleChedzey

Hi Jeff,  I wanted to follow up on this thread.  We were able to duplicate your issue with the SetIsEditingEnabledAsync API method when switching between editing versioned and non versioned workspaces. Thanks for your very clear repro case.   This bug has been fixed and will be in Pro 3.6.  In addition the work has been completed to add additional API methods to specify single workspace edit sessions.  This includes the additional setting on the EditingOptions class along with extension methods on the Project class to specify the workspace to edit.   You'll be able to specify the workspace to edit in a number of different ways.  Using a ArcGIS.Core.Data.Datastore datastore object, using a MapMember, or using a new class - a DatastoreConfiguration  - that will allow you to specify the datastore along with a versioned/non-versioned state for the cases where the datastore has a mixture of versioned and non-versioned data.  Thanks Narelle   ... View more

Hello,  We found a similar issue within our Pro 3.5 development cycle where the EditOperation.Create(Layer, Inspector) created rows with null values instead of the default values with fields that have domains attached.  It sounds very much like the issue you are seeing.  We fixed this issue within 3.5 which was released a few days ago.   Are you able to upgrade to Pro 3.5 to see if your issue is resolved?   If you are not able to upgrade, then would adding a Modify after the Merge (within the same EditOperation) be a workaround.  Make sure that you specify EditOperation.ExecuteMode = ExecuteModeType.Sequential prior to the Merge and Modify calls.   I would suggest using the version of the Modify that takes a dictionary of attributes - https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic9530.html  Thanks Narelle ... View more

Hi Jeff,  Unfortunately we do not have this capability in the Editing API at this point  We do have an issue in our backlog for this work and will be addressing it for the 3.6 release.  Narelle   ... View more

Hi,  Thanks for the code and the error string.  I don't see any problems with your feature class creation code nor the way you are constructing the renderer for the layer.  But I do have concerns about the CreateCurrentImageryFootprintLayerDefinition method and how / where you are using the return CIMFeatureLayer value. - if at all.  Just to confirm that you are creating the layer using the LayerFactory CreateLayer method  (https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic76685.html) Here's an example of adding a feature class to a map // get the fc var fc = geodatabase.OpenDataset<FeatureClass>(name); CIMRGBColor fillColor = new() { R = 0, G = 0, B = 255, Alpha = 0 }; CIMRGBColor outlineColor = new() { R = 0, G = 0, B = 255 }; CIMSolidStroke solidStroke = new() { Color = outlineColor, Width = 1.5 }; var polySymbol = ArcGIS.Desktop.Mapping.SymbolFactory.Instance.ConstructPolygonSymbol(fillColor, SimpleFillStyle.Null, solidStroke); var rd = new ArcGIS.Desktop.Mapping.SimpleRendererDefinition() { Label ="Imagery footprints", SymbolTemplate = polySymbol.MakeSymbolReference() }; var fLayerParams = new ArcGIS.Desktop.Mapping.FeatureLayerCreationParams(fc) { Name = "Current Imagery Footprints", RendererDefinition = rd, }; var fLayer = ArcGIS.Desktop.Mapping.LayerFactory.Instance.CreateLayer<ArcGIS.Desktop.Mapping.FeatureLayer>(fLayerParams, ArcGIS.Desktop.Mapping.MapView.Active.Map);   We don't have every property available to set on the FeatureLayerCreationParams so if you need to update additional properties after the layer has been added then add the following  // update the rest of the layer properties as necessary var fLayerDef = fLayer.GetDefinition() as CIMFeatureLayer; // fLayerDef.ShowLegends = false; // this causes the warning fLayerDef.Selectable = false; fLayerDef.Description = "Current Custom Imagery Footprints"; fLayerDef.CustomProperties = new CIMStringMap[] { new() { Key = "IsCustomLayer", Value = "True" } }; fLayer.SetDefinition(fLayerDef);   In your particular case it appears that the ShowLegends is the property that is causing the Symbology Pane to display the warning.  I believe that this should be true.    If you wish to hide the symbol in the TOC then the best way to do that is to use the layer SetExpanded  method  (https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic11772.html) Let me know if you have any additional questions. Narelle   ... View more

Hi Mody,  Use the Inspector from the Template object to provide temporary override values for field values prior to calling the EditOperation.Create method.  Here is an example // perform the creation var op = new EditOperation(); op.Name = "Create feature"; // use template default field values op.Create(template, geometry); // to modify default template properties var insp = template.Inspector; insp["City"] = "Perth"; // create with the modified fields and a different geometry op.Create(template, geometry2); // reset the template fields back to original defaults insp.Cancel(); // execute the operation bool result = op.Execute(); ... View more

Hi,  So I've dug a bit deeper over the last day and know a bit more about what is going on. And why the EditOperation.Create is not working correctly for dimension features.  As the documentation states, a dimension feature consists of 4 points (the begin, end points, the dimension line point and the text point).  These points are stored as x,y fields in the feature class.  The polygon shape of the dimension is the bounding rectangle of these points and it should be calculated when the feature is created or modified.  In the case of the creation; we supply the points as a mutlipoint geometry, however the calculation to generate the bounding polygon from this point information and the other attributes is not being performed and the shape value of the created feature is null  (which is why it is not displayed).  As you've seen if you make any modifications to the point coordinate attributes or other attributes, the dimension becomes visible - because it's polygon shape has been generated. So basically we need to look into a way to force this shape generation to occur on a creation as the software is not working as it should.    Having said all of that, lets deal with the original question you had first - how to move a dimension feature.  Assuming we're dealing with a well-defined dimension feature  (ie one that is displaying correctly); you should be able to use EditOperation.Move function.   For example // assuming on the MCT // get a dim layer DimensionLayer dimLayer = MapView.Active.Map.GetLayersAsFlattenedList().OfType<DimensionLayer>().FirstOrDefault(); var selection = dimLayer.GetSelection(); var oids = selection.GetObjectIDs(); var oid = oids.FirstOrDefault(); var op = new EditOperation(); op.Name = "Move dimension"; op.Move(dimLayer, oid, 10, 0); // move it in the x direction only var success = op.Execute();   Alternatively you can modify the BeginX, BeginY, EndX, EndY, DimX, DimY and TextX and TextY fields individually if you'd rather using the EditOperation.Modify method and an Inspector class.  Here's an example snippet of this // assuming on the MCT // get a dim layer DimensionLayer dimLayer = MapView.Active.Map.GetLayersAsFlattenedList().OfType<DimensionLayer>().FirstOrDefault(); var selection = dimLayer.GetSelection(); var oids = selection.GetObjectIDs(); var oid = oids.FirstOrDefault(); var insp = new ArcGIS.Desktop.Editing.Attributes.Inspector(); insp.Load(dimLayer, oid); // get all the coordinates Double.TryParse(insp["BeginX"].ToString(), out double BeginX); Double.TryParse(insp["BeginY"].ToString(), out double BeginY); Double.TryParse(insp["EndX"].ToString(), out double EndX); Double.TryParse(insp["EndY"].ToString(), out double EndY); Double.TryParse(insp["DimX"].ToString(), out double DimX); Double.TryParse(insp["DimY"].ToString(), out double DimY); Double.TryParse(insp["TextX"].ToString(), out double TextX); Double.TryParse(insp["TextY"].ToString(), out double TextY); // modify the x positions BeginX += 10; EndX += 10; DimX += 10; // assign the new values to the fields insp["BeginX"] = BeginX; insp["EndX"] = EndX; insp["DimX"] = DimX; // do the edit var op = new EditOperation(); op.Name = "Modify dimension"; op.Modify(insp); var success = op.Execute();   You can use any of the other EditOperation.Modify overloads as appropriate.  The key is that you need to modify the x,y fields of the points and not the shape field itself.   Despite supplying a mtulipoint to the EditOperation.Create to generate a dimension feature we cannot use a multipoint within an EditOperation.Modify to modify the geometry.  I've verified that both of these scenarios work correctly at 3.4.  Can you try and see if they work for you at 2.9.    As for the creation, you were on the correct path with regards to the DimensionFeature. and the SetDimensionShape method.  This is the call we have to  make to force the shape generation to occur as the workaround for this bug.  The way to use this method within an EditOperaiton is to hook into the RowCreated event.   Here's a button that is based on your code snippet with the row event and the SetDimensionShape method.  protected override void OnClick() { var CurrentMap = MapView.Active.Map; DimensionLayer dimLayer = MapView.Active.Map.GetLayersAsFlattenedList().OfType<DimensionLayer>().FirstOrDefault(); QueuedTask.Run(() => { var sr = dimLayer.GetSpatialReference(); // use layer selection to get an oid var selection = dimLayer.GetSelection(); var oids = selection.GetObjectIDs(); var oid = oids.FirstOrDefault(); // load inspector with the feature var insp = new ArcGIS.Desktop.Editing.Attributes.Inspector(); insp.Load(dimLayer, oid); // get the x,y coords of the the dimension points Double.TryParse(insp["BeginX"].ToString(), out double BeginX); Double.TryParse(insp["BeginY"].ToString(), out double BeginY); Double.TryParse(insp["EndX"].ToString(), out double EndX); Double.TryParse(insp["EndY"].ToString(), out double EndY); Double.TryParse(insp["DimX"].ToString(), out double DimX); Double.TryParse(insp["DimY"].ToString(), out double DimY); Double.TryParse(insp["TextX"].ToString(), out double TextX); Double.TryParse(insp["TextY"].ToString(), out double TextY); // create a new multipoint for updated dimension points var DimPoints = new List<MapPoint>() { MapPointBuilderEx.CreateMapPoint(BeginX + 10, BeginY, 0, sr), MapPointBuilderEx.CreateMapPoint(EndX + 10, EndY, 0, sr), MapPointBuilderEx.CreateMapPoint(DimX + 10, DimY, 0, sr) }; var UpdatedGeom = MultipointBuilderEx.CreateMultipoint(DimPoints, AttributeFlags.AllAttributes); // attributes var Attributes = new Dictionary<string, object>() { { "StyleID", 0 }, { "DimType", 0 }, { "BeginX", DimPoints[0].X }, { "BeginY", DimPoints[0].Y }, { "EndX", DimPoints[1].X }, { "EndY", DimPoints[1].Y }, { "DimX", DimPoints[2].X }, { "DimY", DimPoints[2].Y } }; // subscribe to the RowCreatedEvent // do this as close as possible to the EditOperation to // minimize the time that we are monitoring the creates var table = dimLayer.GetTable(); SubscriptionToken token = ArcGIS.Desktop.Editing.Events.RowCreatedEvent.Subscribe(OnRowCreated, table); // wrap in a try/catch/finally to ensure that we can unsubscribe // if there is a failure bool success = false; var Op = new EditOperation(); Op.Name = "Test"; try { Op.Create(dimLayer, UpdatedGeom, Attributes); success = Op.Execute(); } catch (Exception ex) { } finally { // unsubscribe if (token != null) ArcGIS.Desktop.Editing.Events.RowCreatedEvent.Unsubscribe(token); } if (!success) { throw new Exception(Op.ErrorMessage); } }); } private void OnRowCreated(ArcGIS.Desktop.Editing.Events.RowChangedEventArgs args) { var row = args.Row; if (row is ArcGIS.Core.Data.Mapping.DimensionFeature df) { try { // force the dimension polygon shape generation // a simple get and then set will accomplish this var shape = df.GetDimensionShape(); df.SetDimensionShape(shape); } catch (Exception ex) { } } }   Again, this works on 3.4; can you verify that it will work for you on 2.9.      I've entered an issue into our backlog to fix the dimension creation.  In the meantime, I'll get this workaround documented on the Editing Dimensions concept page.  Thanks for drawing our attention to this; unfortunately we don't have too many dimension feature SDK users.  Let me know if you have any additional questions or run into any problems with the snippets I've posted. Narelle   ... View more

Kerry,  Sorry for the confusion.  I would have to qualify my above statement with regards to determining when a button / command has finished executing; is that it depends on the command.  In the example in the documentation, the command "esri_mapping_createBookmark"  displays a modal dialog and performs some action on the ok button.  The command in your example  "esri_editing_DivideCommand" activates the divide tool and displays a UI in a dockpane.  This is not a modal dialog as tools very often require some interaction with the map.  The divide command at this point has finished executing.  It is the divide tool and the dockpane UI that actually controls the divide operation.   The only way to know when the user has finished interacting with the UI and executed the divide edit is to use the edit events. .  Hope this helps clarify things a bit.    Narelle ... View more