nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Local Geoprocessing without packages

GeorgeFaraj

I'm opening feature layers from map packages and now I need to run tools such as Union, Buffer, Intersect, etc. dynamically on those layers, then add the results as a new layer in the map. What is the best way to do this locally without using pre-modeled packages?

Find more posts tagged with

Runtime SDK for WPF

Accepted answers

GeorgeFaraj

I finally got this working. I'll put the code here in case anyone else needs help with this. I needed to specify the correct field type, and especially I needed to correctly identify the OID field too. Thanks for everyone that helped.

  public static ICollection<Field> GetFields(Graphic graphic)   {    var fields = new List<Field>();    foreach (var attribute in graphic.Attributes)    {     var field = new Field()     {      FieldName = attribute.Key,      Alias = attribute.Key     };     if (attribute.Key.ToLower() == "shape")     {      field.Type = Field.FieldType.Geometry;     }     else if (attribute.Key.ToLower() == "fid")     {      field.Type = Field.FieldType.OID;     }     else if (attribute.Key.ToLower() == "objectid")     {      field.Type = Field.FieldType.OID;     }     else if (attribute.Value is int)     {      field.Type = Field.FieldType.Integer;     }     else if (attribute.Value is double)     {      field.Type = Field.FieldType.Double;     }     else if (attribute.Value is float)     {      field.Type = Field.FieldType.Single;     }     else if (attribute.Value is DateTime)     {      field.Type = Field.FieldType.Date;     }     else     {      field.Type = Field.FieldType.String;     }     fields.Add(field);    }    return fields;   }

All comments

GeorgeFaraj

That's interesting... I tried doing this to test it out:

var inputFeatures = new GPFeatureRecordSetLayer("InputFeatures");
inputFeatures.FeatureSet.Fields = new List<Field> { new Field() { FieldName = "PROP_ID" } };

but the Geoprocessor fails now and these are the details of the error:

Unable to complete operation.
Error executing tool.: ERROR 000210: Cannot create output C:\Users\gfaraj\AppData\Local\Temp\arcgisruntime_8188\geotools\jobs\_\j13c432afc4014a6a9eed8b1b446e0a6b\scratch\scratch.gdb\OutputFeature
Failed to execute (Buffer).
Failed to execute (BufferModel).
Failed to execute (BufferModel).
Failed to execute (BufferModel).

Any ideas?

KevinHibma

Off the top of my head? No.
I'll try to make some time this afternoon to test it.

GeorgeFaraj

Any updates, Kevin?

Thanks.

KevinHibma

I got looking at this mid last week and was off Thursday/Friday, so I handed it off to Mike.
Everything I've seen makes it look possible. I had to hand it off to Mike because I wasn't sure of the code to combine features and attributes into a single parameter. I'm not sure if Mike had anytime to look at it.
As for the code you posted earlier, I think you're on the right track. It just didnt look like yours had any geometry being sent, it was only sending the attributes.

MichaelBranscomb

Hi,

Apologies for the delay.

Here's an example of creating a FeatureSet in order to pass both geometry and attributes into a GP service:

             /* 
             * Build the GP Parameters...
             */
            // We want to specify input attributes - create a new FeatureSet.
            FeatureSet featureSet = new FeatureSet();

            // Create the Fields and add one called "VALUE".
            featureSet.Fields = new List<Field> { new Field() { FieldName = "VALUE", Type = Field.FieldType.String, Alias = "VALUE" } };
            
            // Create the graphic to submit.
            Graphic g = new Graphic() { Geometry = e.MapPoint };

            // Add the graphic to the FeatureSet
            featureSet.Features.Add(g);

            // Set the graphic's attribute
            featureSet.Features[0].Attributes["VALUE"] = "Hello";

            // Create a new list of GPParameters
            List<GPParameter> parameters = new List<GPParameter>();

            // Add a new GPFeatureRecordSetLayer to the parameter list, passing in the FeatureSet created above.
            parameters.Add(new GPFeatureRecordSetLayer("Input_Features",featureSet));

The above code ensures the input feature has both geometry and attributes. In order to have the input attributes persisted on your output features you'll additional steps within your model/script.

Cheers

Mike

GeorgeFaraj

Thanks Mike. Still getting the same error when running the tool. Here's the code that gathers the parameters:

var featureSet = new FeatureSet();
var layer = GetSelectedInputLayer();

featureSet.Fields = new List<Field> { new Field() { FieldName = "PROP_ID", Type = Field.FieldType.Double, Alias = "PROP_ID" } };
foreach (var graphic in layer.SelectedGraphics)
{
 featureSet.Features.Add(graphic);
}
parameters.Add(new GPFeatureRecordSetLayer("InputFeatures", featureSet));
parameters.Add(new GPLinearUnit("Distance", esriUnits.esriMeters, Convert.ToDouble(distanceText.Text)));

Again the exception contains the following details:

Unable to complete operation.
Error executing tool.: ERROR 000210: Cannot create output C:\Users\gfaraj\AppData\Local\Temp\arcgisruntime_8188\geotools\jobs\_\j13c432afc4014a6a9eed8b1b446e0a6b\scratch\scratch.gdb\OutputFeature
Failed to execute (Buffer).
Failed to execute (BufferModel).
Failed to execute (BufferModel).
Failed to execute (BufferModel).

If I remove the line that sets the Fields on the feature set, the tool completes, but the resulting graphics don't have the original inputs' attributes.

GeorgeFaraj

I'm still having this problem. Can someone help?

MatthewBrown1

Hi Charles,

This may not be related but we had some problems with local GP tasks intermittently failing on some machines, often returning "Error: 000210 : Cannot create output..." (amongst others). This was related to anti-virus and group policy security settings in our corporate environment. (Everything worked fine in my dev environment, but the same code/data failed elsewhere.)

Are you running 1.0 or 10.1.1? The upgrade solved a few quirky issues we were having, so might be worth a try.

Also, if you have access to ArcGIS Server, try publishing a GP service and calling that from your Runtime app. (In my case the full AGS GP service worked, when the local GPK failed.)

Good luck!

GeorgeFaraj

This may not be related but we had some problems with local GP tasks intermittently failing on some machines, often returning "Error: 000210 : Cannot create output..." (amongst others). This was related to anti-virus and group policy security settings in our corporate environment. (Everything worked fine in my dev environment, but the same code/data failed elsewhere.)

Interesting. The thing is, the tool runs fine if I don't specify the Fields collection. But then the output doesn't contain the fields of the input features; it contains the fields of the schema set in the GPK; which is the problem I'm trying to resolve.

Are you running 1.0 or 10.1.1? The upgrade solved a few quirky issues we were having, so might be worth a try.

I'm running 10.1.1 already.

Also, if you have access to ArcGIS Server, try publishing a GP service and calling that from your Runtime app. (In my case the full AGS GP service worked, when the local GPK failed.)

I don't have access to ArcGIS Server right now.

Thanks!

MatthewBrown1

... the tool runs fine if I don't specify the Fields collection. But then the output doesn't contain the fields of the input features; it contains the fields of the schema set in the GPK; which is the problem I'm trying to resolve.!

I've hit this issue as well, and I got around it by using a bunch of conditional Add Field/Calculate Field/Delete Field tools to tidy things up. Hardly ideal!

I haven't tried this in the Runtime, but I will have a go later this week (time permitting) as I too am often frustrated by subtle changes in schema.

GeorgeFaraj

Let me know how that turns out please. Thanks!

MichaelBranscomb

Hi,

Here's the code I'm using to persist from the input featureset to the output featureclass:

  /* 
             * Build the GP Parameters...
             */
            // We want to specify input attributes - create a new FeatureSet.
            FeatureSet featureSet = new FeatureSet();

            // Create the Fields and add one called "VALUE".
            featureSet.Fields = new List<Field> { new Field() { FieldName = "VALUE", Type = Field.FieldType.String, Alias = "VALUE" } };
            
            // Create the graphic to submit.
            Graphic g = new Graphic() { Geometry = _mercator.ToGeographic(e.MapPoint) };

            // Add the graphic to the FeatureSet
            featureSet.Features.Add(g);

            // Set the graphic's attribute
            featureSet.Features[0].Attributes["VALUE"] = "Hello";

            // Create a new list of GPParameters
            List<GPParameter> parameters = new List<GPParameter>();

            // Add a new GPFeatureRecordSetLayer to the parameter list, passing in the FeatureSet created above.
            parameters.Add(new GPFeatureRecordSetLayer("Input_Features",featureSet));

            // Handler for the completed event
            _gpTask.ExecuteCompleted += (s, e1) =>
            {
                //OutputCopyFeatures
                GPExecuteResults results = e1.Results;
                GPFeatureRecordSetLayer rs = results.OutParameters[0] as GPFeatureRecordSetLayer;
                // Check the attributes... output feature should have attribute Field "VALUE" with value "Hello".
            };

GeorgeFaraj

Hi Mike,

If you scroll up a little bit, you'll see that I'm using similar code. The only difference is that I'm getting my input features from the SelectedGraphics collection. And I will emphasize that these features have a different attribute schema than the one I used to save my GPK.

Thanks.

MichaelBranscomb

Hi,

Apologies, for the delay in replying - to pursue this issue a little further I actually demo'd it at the recent Esri Dev Summit. You can download the code for all the demos from GitHub or ArcGIS.com:

https://github.com/Esri/tips-and-tricks-wpf
http://www.arcgis.com/home/item.html?id=3f69c79bbd7340b09fad396647a977a5

I've also attached the specific demo to this post.

Cheers

Mike

Persisting-Schema-On-Gp-Outputs.zip

GeorgeFaraj

Thank you Mike, I will be trying this out today.

GeorgeFaraj

Hi Mike,

I was doing something similar to your sample app. But the difference is that I'm working with pre-existing graphics with pre-existing attributes, while you were creating a new graphic and adding a new field.

I got this to work well now, which is a big progress:

var featureSet = new FeatureSet();
var layer = GetSelectedInputLayer();

featureSet.Fields = new List<Field>((layer as FeatureLayer).LayerInfo.Fields);
foreach (var graphic in layer.SelectedGraphics)
{
 featureSet.Features.Add(graphic);
}
parameters.Add(new GPFeatureRecordSetLayer("InputFeatures", featureSet));
parameters.Add(new GPLinearUnit("Distance", esriUnits.esriMeters, Convert.ToDouble(distanceText.Text)));

The problem now is that this only works with Feature Layers that have a LayerInfo value. I want this to work with a regular GraphicsLayer too, and the list of fields is not known to me ahead of time.

I wrote the following helper methods that will return the list of Fields for any layer:

public static ICollection<Field> GetFields(Graphic graphic)
{
 var fields = new List<Field>();
 foreach (var attribute in graphic.Attributes.Keys)
 {
  fields.Add(new Field()
  {
   FieldName = attribute, Type = Field.FieldType.Unknown, Alias = attribute
  });
 }
 return fields;
}

public static ICollection<Field> GetFields(Layer layer)
{
 if (layer is FeatureLayer)
 {
  var featureLayer = layer as FeatureLayer;
  if (featureLayer.LayerInfo != null)
  {
   return featureLayer.LayerInfo.Fields;
  }
  else if (featureLayer.Graphics.Count > 0)
  {
   return GetFields(featureLayer.Graphics[0]);
  }
 }
 else if (layer is GraphicsLayer)
 {
  var graphicsLayer = layer as GraphicsLayer;
  if (graphicsLayer.Graphics.Count > 0)
  {
   return GetFields(graphicsLayer.Graphics[0]);
  }
 }

 return new List<Field>();
}

So basically I'm looping through the attributes of the first Graphic and retrieving the Fields this way. But when I pass this collection of fields to the geoprocessor, it fails. It's obvious that the fields are causing the failure because if I don't specify the Fields property of the FeatureSet, the geoprocessor succeeds.

Is there a more accurate way of getting a list of fields/attributes from non-feature layers like Graphics layers?

Thanks!

GeorgeFaraj

  public static ICollection<Field> GetFields(Graphic graphic)   {    var fields = new List<Field>();    foreach (var attribute in graphic.Attributes)    {     var field = new Field()     {      FieldName = attribute.Key,      Alias = attribute.Key     };     if (attribute.Key.ToLower() == "shape")     {      field.Type = Field.FieldType.Geometry;     }     else if (attribute.Key.ToLower() == "fid")     {      field.Type = Field.FieldType.OID;     }     else if (attribute.Key.ToLower() == "objectid")     {      field.Type = Field.FieldType.OID;     }     else if (attribute.Value is int)     {      field.Type = Field.FieldType.Integer;     }     else if (attribute.Value is double)     {      field.Type = Field.FieldType.Double;     }     else if (attribute.Value is float)     {      field.Type = Field.FieldType.Single;     }     else if (attribute.Value is DateTime)     {      field.Type = Field.FieldType.Date;     }     else     {      field.Type = Field.FieldType.String;     }     fields.Add(field);    }    return fields;   }

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.