Custom sketch tool

Question

I want to create a tool that the user uses like an edit template's sketch tool.  I want to get geometry from the user that is not tied to a particular layer, just want the user to digitize a geometry using their snapping environment.  When they're done I want to use that geometry and do some things with it.  Is there an existing sketch tool that I can inherit from in my tool class or something?

Anonymous User · Answer

Yeah were seeing some interesting coding patterns out there which prompted the doc review.

Thanks for the feedback.

TedChapin · Answer

Sean Jones​ Thank you, that is exactly what I was looking for.  You wouldn't believe the path I was going down.  I had a button that activated the layer's edit template, so the users could make their sketch and listened for OnRowCreated.  Then  I validated the feature and if it failed (using the sketch geometry, if it didn't connect to the right things) I used args.Row.delete to prevent the feature from getting saved.  That was working, until I needed to use the sketch geometry to create features in other layers as well.  Then I started the RowBuffer, Row, Store pattern.  Way too granular.  EditOperation.Create with a layer and a dictionary is much more concise.  And I like that you can Execute or ExecuteAsync.  For just adding a single simple feature to a layer in the map it doesn't seem worth the async plumbing.

I'm glad you're continuing to work on the documentation.  Often what I want is in the API reference, but I don't know where.  The concepts doc should tell you what pattern you should be using and guide you to the API reference for the syntax to implement that pattern.  Not a big fan of the GitHub wiki.  I wish the Pro SDK docs were more like this: ArcGIS API for JavaScript  or this:What is ArcPy?—Help | ArcGIS for Desktop​

And more VB code samples please!

Anonymous User · Answer

Hi Ted, There's a bit of misconception about when to use the callback method to make edits in Pro. Were in the process of cleaning up the help this week to make it a bit clearer. Generally speaking, If your layers are in the project (in a map) then you should be using the other methods on EditOperation to perform the edits (create, modify, etc). The callback method was introduced to allow edits on geodatabase feature classes that weren't usually in a map. The following example shows the OnSketchCompleteAsync method for a point sketch tool that creates a point feature with some attribute values: protected override Task OnSketchCompleteAsync(Geometry geometry) { //run on MCT return QueuedTask.Run(() => { //find layer by name var rsLayer = MapView.Active.Map.FindLayers("Ranger stations").FirstOrDefault() as FeatureLayer; //set some attributes via a dictionary (field name, value) var atts = new Dictionary(); atts.Add("Shape", geometry); atts.Add("Location", "Redlands"); //create and execute the EditOperation var op = new EditOperation(); op.Name = "Create feature with attributes"; op.Create(rsLayer, atts); op.Execute(); return op.IsSucceeded; }); } In the example im using the Create method to create a feature in the layer with a dictionary. If I didn't care about the attributes I could have used the other create methods to create the feature using just the layer and accepting the layer default attributes; or a feature template with its default attributes. Using this pattern, Pro looks after the layer refresh. And yes, all edits should be encapsulated within an editoperation to keep Pro in sync.