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?

Vind meer berichten getagd met

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

  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;   }

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

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

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

Clip_127.jpg

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,

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

Let me know how that turns out please. 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

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

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

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

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.

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

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.

GeorgeFaraj

Any updates, Kevin?

Thanks.

KevinHibma

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

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

I don't have the Runtime explanation, but I can explain it from the GP Service perspective.
With a GP Service you can override the schema by passing in a description (fields tag below) of the fields the output will have...
The following JSON example shows that ID and NAME field have been defined, and then you see those fields attached to the geometry.

{ 
"geometryType" : "esriGeometryPoint",
"spatialReference" : {"wkid" : 4326},
"fields":[
{"name":"Id","type":"esriFieldTypeOID","alias":"Id"},
{"name":"Name","type":"esriFieldTypeString","alias":"Name"}
],
"features"  : [
{
    "geometry" : {"x" : -104.44, "y" : 34.83},
    "attributes" : {"Id" : 43, "Name" : "Feature 1"}
},
{
    "geometry" : {"x" : -100.65, "y" : 33.69},
    "attributes" : {"Id" : 67, "Name" : "Feature 2"}
}
]
}

So to answer your question, you will probably need to define the schema when you pass in the features. I'm not entirely sure how to do that in the Runtime without testing.

GeorgeFaraj

Question: Is there a way for the resulting feature set to contain the attributes of the input feature set parameters? I'm getting back the parameters that were in the schema I used in ArcMap, and not the attributes of the actual features I'm passing to the geoprocessor.

MichaelBranscomb

Glad to hear you got it working.

There's a sample in the WPF Sample App which could help in future - GPTaskInfo, it spins up a new LocalGPService based on your GPK and lists the parameters, etc. Looks like this: http://resources.arcgis.com/en/help/runtime-wpf/samples/index.html#/GPTaskInfo/02q20000004w000000/

Cheers

Mike

GeorgeFaraj

Nevermind, I got it working. I was passing my input parameter with the wrong name. Thanks to everyone who helped!

GeorgeFaraj

I fixed my input parameters, they were not set correctly. I got it to complete, but got no results back. Apparently this is because I had no output parameter set up. I went back to ArcMap and set the output of the Buffer tool to be a Model Parameter. I am now getting this error:

Error executing tool.: ERROR 000210: Cannot create output C:\Users\gfaraj\AppData\Local\Temp\arcgisruntime_7576\buffertest1\jobs\_\j8adb6feeb81f41cab48b4ec3f22a011d\scratch\scratch.gdb\BufferResult
Failed to execute (Buffer).
Failed to execute (BufferModel).
Failed to execute (BufferModel).
Failed to execute (BufferModel).

Any ideas?

buffertool2.png

GeostatisticalWizard 2.jpg

GeorgeFaraj

The ExecuteCompleted handler doesn't get called, only the Failed handler does. I edited my reply above with more info, but here it is too:

Found more details about the error inside the failed event args:

[0] = "Error executing tool.: ERROR 000800: The value is not a member of parcels."

'parcels' is the name of my FeatureLayer. It's also the name of the layer I used as a sample input when I ran the tool in ArcMap.

EDIT:

My LocalServer log:

2013-01-22 10:49:35,418  INFO rid=22  'server' AdminWebService - POST admin/createService
2013-01-22 10:49:35,420  INFO rid=22  'server' GPServer-buffertest1 - Creating.
2013-01-22 10:49:35,420  INFO rid=22  'server' GPServer-buffertest1 - Create
2013-01-22 10:49:35,420  INFO rid=22  'server' ServerObjectHostProcess-buffertest1_host - Creating.
2013-01-22 10:49:35,420  INFO rid=22  'server' ServerObjectHostProcess-buffertest1_host - Launching.
2013-01-22 10:49:35,428  INFO rid=22  'server' ServerObjectHostProcess-buffertest1_host - Launched process 12220
2013-01-22 10:49:35,506  INFO rid=    'worker-12220' STAServerObjectHost - Creating.
2013-01-22 10:49:35,511  INFO rid=22  'worker-12220' STAServerObjectHost - Received Request.
2013-01-22 10:50:09,628  INFO rid=22  'worker-12220' STAServerObjectHost - Received Request.
2013-01-22 10:50:09,632  INFO rid=22  'server' GPServer-buffertest1 - Created
2013-01-22 10:50:09,633  INFO rid=22  'server' WebServer - Added request handler for HTTP resource: /CVGcCl/arcgis/rest/services/buffertest1
2013-01-22 10:50:09,633  INFO rid=22  'server' WebServer - Loaded static web service for resource (/CVGcCl/arcgis/rest/services/buffertest1)
2013-01-22 10:50:09,637  INFO rid=23  'server' GPServer-buffertest1 - GET GPServer?f=json&tstmp=634944486096376811
2013-01-22 10:50:09,650  INFO rid=23  'server' GPServer-buffertest1 - Request handled.
2013-01-22 10:50:09,658  INFO rid=24  'server' GPServer-buffertest1 - GET GPServer/BufferModel?f=json&tstmp=634944486096576831
2013-01-22 10:50:09,659  INFO rid=24  'server' GPServer-buffertest1 - Request handled.
2013-01-22 10:50:09,761  INFO rid=25  'server' GPServer-buffertest1 - POST GPServer/BufferModel/execute
2013-01-22 10:50:09,764  INFO rid=25  'worker-12220' STAServerObjectHost - Received Request.
2013-01-22 10:50:13,087  INFO rid=25  'server' GPServer-buffertest1 - Request handled.
2013-01-22 10:50:23,088  INFO rid=    '' WebServer - Lost connection on port 50000

EDIT2: I should post my code:

var gp = new Geoprocessor(GetGeoprocessingService().UrlGeoprocessingService + "/BufferModel");

var parameters = new List<GPParameter>();

var gpFeatureRecordSetLayer = new GPFeatureRecordSetLayer("InputLocation");

foreach (var graphic in (MyMap.Layers["parcels"] as FeatureLayer).SelectedGraphics)
{
 gpFeatureRecordSetLayer.FeatureSet.Features.Add(graphic);
}

parameters.Add(gpFeatureRecordSetLayer);
gp.ExecuteCompleted += (senderObject, gpExecuteCompleteEventArgs) =>
{
};
gp.Failed += (senderObject, taskFailedEventArgs) =>
{
};
gp.ExecuteAsync(parameters);

MichaelBranscomb

You've got a couple of options:

#1. Iterate over the GPMessages

e.g.

geoprocessor.ExecuteCompleted += (s1, e1) =>
                        {
                            GPExecuteResults results = e1.Results;

                            foreach (GPMessage message in results.Messages)
                            {
                                // Do Something e.g. Console.WriteLine(message.Description);
                            }
                        };

geoprocessor.ExecuteAsync(new List<GPParameter>());

#2. Take a look at the actual RuntimeLocalServer log files - sometimes there may be additional info in there.
Use the LocalServerUtility (accessed from the Start Menu) to enable logging for your central developer Runtime install then rerun your code. This will generate a log file - you can use the LocalServerUtility to view these logfiles, or at least the location of them anyway - they're just textfiles written to your temp folder.

Cheers

Mike

GeorgeFaraj

Thanks. I had forgotten to pass Execute in the service's constructor. Now I'm getting another error. Any idea how to figure out what's wrong now?

Unable to complete operation.

EDIT: Found more details about the error inside the failed event args:

[0] = "Error executing tool.: ERROR 000800: The value is not a member of parcels."

'parcels' is the name of my FeatureLayer. It's also the name of the layer I used as a sample input when I ran the tool in ArcMap.

MichaelBranscomb

The type of method call you make: ExecuteAsync or SubmitJobAsync needs to correspond the the GPServiceType you start the Local GP Service as (GpServiceType.Execute, etc) - see http://resources.arcgis.com/en/help/runtime-wpf/apiref/index.html?ESRI.ArcGIS.Client.Local~ESRI.ArcGIS.Client.Local.GPServiceType.html for more info.

It's an architectural detail of the way the RuntimeLocalServer manages the LocalGPService, but it's a choice you need to make. Typically the Execute (synchronous) type of service should only be used for very quick models/taks.

Cheers

Mike

GeorgeFaraj

Well, that was a quick reply! 🙂

I actually noticed that and edited the error message above. This is the error I'm getting now:

Bad request: POST GPServer/BufferModel/execute The 'execute' operation is not supported.

MichaelBranscomb

Hi,

The task within the service takes the same name as the model name - from your screenshot it looks like you should be using "BufferModel" in your code?

Cheers

Mike

GeorgeFaraj

Thanks for the suggestions guys. I still need some more help though. When I try to run the tool in my Runtime app, the geoprocessor fails with this error:

Bad request: POST GPServer/BufferModel/execute The 'execute' operation is not supported.

Any ideas why this would happen? I am attaching a screenshot of the Model Builder. When I run this tool in ArcMap, I select a sample layer for the InputFeatures parameter, and I have the Distance pre-set to 350 meters. The tool succeeds, and after that I am sharing it as a Geoprocessing Package.

buffertool.png

1.png

MatthewBrown1

You'll have to run the tool to get a result to turn into a GPK...

Hi Charles,

In addition to Kevin's post, you might want to use the 'Package schema only' option so only empty layers are packaged with the GPK.

I'm not sure if this is what you'd call "best practice" in terms of GPK creation, but it works for me (and seems to fit your scenario):

Create your script/model tool using FeatureSet for input parameter(s) instead of Feature Class/Layer/etc.
Run your tool with no data to get (an empty) result. (You can set the schema from the sample data if developing/testing your tool in Modelbuilder.)
Create GPK. I use options 'Package schema only' and 'Support ArcGIS Runtime' but the former might be redundant with empty inputs.

Any other suggestions from forum members?

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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