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?

Encuentra más publicaciones etiquetadas con

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

KerrieScholefield

Hi,

Geometry operations such as Union, Buffer, Intersect can be dynamically performed on graphics. Once the operation is complete the results can be rendered on the map in a graphics layer. To perform these operations on local data, the LocalGeometryService should be used in conjunction with the use of a GeometryService Task.

Please see the conceptual documentation on LocalGeometryService for more information and code examples:

http://resources.arcgis.com/en/help/runtime-wpf/concepts/index.html#/How_to_use_the_Geometry_task/017000000039000000/

Samples using the LocalGeometry Class can be found in the Sample Application under Geometry> Geometry Operations

Cheers

Kerrie

GeorgeFaraj

I would like to revive this thread. I'm not sure if the above answer is really what I need. I have one or more layers and want to perform operations such as Buffer, Union, Clip, etc onto those layers. I want it to work like in the ArcObjects SDK, where you use the Geoprocessor and you specify the input feature layers, and it would return the resulting features.

Can someone direct me on the right path?

GeorgeFaraj

Is there really no way to run geoprocessing tools without having to pre-package the geometry and tools beforehand? I want to run geoprocessing tools on dynamically added layers (which can be shapefiles) on my map. Is this not possible?

MichaelBranscomb

Hi,

I think depends on what you'd like to achieve with the output. If it's for display purposes or for the duration of the user/app session then the LocalGeometryService and the GeometryService task is a valid approach for the types of functions you mentioned (buffer, clip, union). They work with arrays of individual geometries so you'd need to construct a query first to retrieve the geometries. If you want to store these geometries you could add them to a Geodatabase via a FeatureLayer/ArcGISLocalFeatureLayer or you can also serialize the features to JSON.

Alternatively you can use Geoprocessing packages to create a LocalGeoprocessingService and use in conjunction with the Geoprocessor task. This gives you the benefit of being able to create longer workflows as a model or Python script (i.e. Input > Buffer > Clip > Intersect > Output) and calling it as one operation, asynchronously. Typically these GP tools operate on an entire feature class (although you can easily do selection/filtering in the model/script). You'll get the result back as a set of Graphic objects, or alternatively you can request a MapServer to render the results (better for large datasets). If you want to store the output in a Geodatabase you can have the model/script write the output as required, or create an separate model/script to do this piece. Again, you could also write graphics to a Geodatabase via a FeatureLayer/ArcGISLocalFeatureLayer or serialize the features to JSON.

Cheers

Mike

GeorgeFaraj

Hi Mike,

With regards to your second approach (Geoprocessor), how do I execute a geoprocessing tool on any layer on the map? Everything I've seen in the documentation suggests that I have to create the geoprocessing package beforehand with the geometry. I want to mimick the Geoprocessing functionality that is provided with ArcMap, where you select the tool you want and then set the input parameters, like which layers to use, etc. After running it, I will add the results as a layer.

Charles,

Have you checked the code under ArcGIS Runtime SDK for WPF samples (desktop application )?

Under - Geometry -> Geometry operations -> Buffer a point

Similar to what Mike suggested.

Does this help for your requirement?

GeorgeFaraj

Charles,

Have you checked the code under ArcGIS Runtime SDK for WPF samples (desktop application )?

Under - Geometry -> Geometry operations -> Buffer a point

Similar to what Mike suggested.

Does this help for your requirement?

I am not sure if this works for me. For example, if I run the Buffer operation on Layer1, I want the results of the operation to contain (clones of) the features from Layer1 that are within that buffer. I need to use the attributes for these resulting features to perform other operations on them.

This was easily done using the Geoprocessor class in the ArcObjects SDK, by providing the input layer and a distance.

DominiqueBroux

You can't directly use the layer as input of a geometry service but most of the geometry service accepts a list of feature as input parameter (ex BufferParameter.Features) so setting the input with all graphicsLayer.Graphics is just a particular case.

Though note that the graphics returned by the service don't include the attributes. However the returned graphics are always in the same order as the input graphics so you can easily retrieve the attributes from the input graphics.

For the intersect service (not sure from your description if you are talking about Buffer or Intersect service), some features may not intersect the input geometry but even in this case graphics with a null geometry are returned in the output graphics so the number of output graphics is always equals to the number of input graphics.

GeorgeFaraj

Though note that the graphics returned by the service don't include the attributes. However the returned graphics are always in the same order as the input graphics so you can easily retrieve the attributes from the input graphics.

That doesn't make sense to me. If I want a buffer of N kms around X features, I want the results to also contain features outside of those X features but within the buffer distance. In other words, the results should have X or more features.

AutoID Form.png

DominiqueBroux

That doesn't make sense to me. If I want a buffer of N kms around X features, I want the results to also contain features outside of those X features but within the buffer distance. In other words, the results should have X or more features.

The Buffer geometry service returns one buffer polygon by input geometry. Each input geometry is buffered at the specified distance and the buffer polygon is returned as output.
Note that there is also an option to get only one output geometry that is the union of all buffers.

But in no case the result has more features than the input.

GeorgeFaraj

Yeah, I need to get info about features that are not part of the input, but are affected by the operation. I used to do this with the Geoprocessor class in the ArcObjects SDK. I want to use the Geoprocessor here too, but I don't want to have to package the geometry with the geoprocessing tool. The user should be able to open any layers and perform the geoprocessing operation on those layers (just like you would in ArcMap). Is this possible?

MatthewBrown1

Hi Charles,

Further to Mike's earlier post, have you tried creating a geoprocessing package or service and sending a dataset from the Runtime using GP parameters? This will allow you to have control over the data you send, including the attributes you require, and this data doesn't have to be stored in the GPK.

Here's a generic example from the online help:

//Create a new Geoprocessor object
Geoprocessor gp = new Geoprocessor(_localGPService.UrlGeoprocessingService + "/Buffer");

//Create a new List of type GPParameter to hold the parameters for the service
List<GPParameter> parameters = new List<GPParameter>();

//Create a new GP FeaturerecordSetLayer with parameter name
GPFeatureRecordSetLayer gpFeatureRecordSetLayer = new GPFeatureRecordSetLayer("Input_Locations");

//Add the GpFeatureRecordSetLayer to the parameter list
parameters.Add(gpFeatureRecordSetLayer);

The architecture of the Runtime SDK is different to ArcEngine and Desktop, so you have to adjust your workflows (and GP models/scripts!) to suit the service-oriented architecture. (Also, be aware that not all GP tools are supported in the Runtime local geoprocessor and there are some limitations in terms of the size of the datasets you send to the GP service - you can adjust the output, but the input seems to be fixed at 1000 records from the work I have done.)

Having said that, ArcGIS 10.1 uses some kind of Runtime local service to perform background geoprocessing on "standard" GP tools (i.e. no GPK is required), so I think there is merit to your initial question.

Hope this helps,

Matt

KevinHibma

The architecture of the Runtime SDK is different to ArcEngine and Desktop, so you have to adjust your workflows (and GP models/scripts!) to suit the service-oriented architecture. (Also, be aware that not all GP tools are supported in the Runtime local geoprocessor and there are some limitations in terms of the size of the datasets you send to the GP service - you can adjust the output, but the input seems to be fixed at 1000 records from the work I have done.)

Having said that, ArcGIS 10.1 uses some kind of Runtime local service to perform background geoprocessing on "standard" GP tools (i.e. no GPK is required), so I think there is merit to your initial question.

You're correct about the modifying of models and scripts.
I can explain things a little further from the GPK/GP Runtime side of things, but I dont have the core knowledge of Runtime... so hopefully this might be enough to move you forward:

When you create a GPK for Runtime - that GPK will end up the same way if you created a GP Service. In a way you can think of Runtime hosting a GP Service for you.
For example, if you create a model which takes a featureclass as input, and create a runtime gpk, then that featureclass parameter becomes a featureset in the gpk. Featureclass is not a supported input type for GP Server (thus Runtime), but featureset is. (I know this sounds trivial, but its important to understand the parameter type in regards to how it can take input)

So, lets say I created a GP Service and this service made use of a featureset as input. I could consume this in Desktop and pass in a layer to the featureset parameter (desktop streams the features to the server) and the service would act upon them.
Now this is the part I dont know enough about in Runtime: if you have the same notion of layers in Runtime as you do in ArcMap, I'd say its conceivable that those layers could be passed to the "gp service" (ie the geoprocessing task runtime has spun up).
So if you know the answer to the "layer" question, and its "yes", then I'd suspect you could pass that layer into the GP parameter within the applications code and it should act upon it.

Your note about the runtime local service for background in desktop: True again. Note though: Well, yes they share common components and the same name - they do not equal one another. Background server in Desktop has zero interaction with a Runtime application. Basically I dont want you to confuse that just because you can do something in Desktop+Background you could potentially do the same in Runtime.

MatthewBrown1

Now this is the part I dont know enough about in Runtime: if you have the same notion of layers in Runtime as you do in ArcMap, I'd say its conceivable that those layers could be passed to the "gp service" (ie the geoprocessing task runtime has spun up).
So if you know the answer to the "layer" question, and its "yes", then I'd suspect you could pass that layer into the GP parameter within the applications code and it should act upon it.

Your note about the runtime local service for background in desktop: True again. Note though: Well, yes they share common components and the same name - they do not equal one another. Background server in Desktop has zero interaction with a Runtime application. Basically I dont want you to confuse that just because you can do something in Desktop+Background you could potentially do the same in Runtime.

Hi Kevin,

I wouldn't say layers in Desktop and Runtime are the same from my experience, but I've set up a few local GP services that *only* consume data from the application (both feature service and graphics layers) and I think you are correct about FeatureSets being the key. It took me a while to figure this out when I started using the Runtime SDK, and even though the documentation is more complete now than during the beta and pre-release, it could be made more obvious for folk coming from Desktop/ArcEngine or those with complicated projects that go beyond the GP samples.

Yes, I figured as much when I couldn't see a REST endpoint or anything in Fiddler, but it would be quite cool if this was opened up in the future as I have been frustrated with some GP tools not being available with the Runtime SDK. ArcPy gets better with every release, so some missing tools can be replaced with scripts, but it would be great if ArcInfo-level tools were supported in the Runtime. (But I guess this would contradict the intended purpose of the Runtime and you would be better to use something else from the ESRI stack.)

KevinHibma

Hi Kevin,

I wouldn't say layers in Desktop and Runtime are the same from my experience, but I've set up a few local GP services that *only* consume data from the application (both feature service and graphics layers) and I think you are correct about FeatureSets being the key. It took me a while to figure this out when I started using the Runtime SDK, and even though the documentation is more complete now than during the beta and pre-release, it could be made more obvious for folk coming from Desktop/ArcEngine or those with complicated projects that go beyond the GP samples.

For 10.1 sp2 (due probably around March) - we've enhanced the GPK for Runtime creation.
You'll now have parameter control support. So the whole point above about how parameters being mapped to a supported type happen under the hood: now you'll be able to play with those parameters when creating your GPK. Basically we've given the GP Service creation experience to the Runtime GPK experience. Hopefully this will make it easier for you and everyone else trying to do crafty things with GP in the Runtime.

Yes, I figured as much when I couldn't see a REST endpoint or anything in Fiddler, but it would be quite cool if this was opened up in the future as I have been frustrated with some GP tools not being available with the Runtime SDK. ArcPy gets better with every release, so some missing tools can be replaced with scripts, but it would be great if ArcInfo-level tools were supported in the Runtime. (But I guess this would contradict the intended purpose of the Runtime and you would be better to use something else from the ESRI stack.)

If theres a tool you want/need but it isn't supported: either submit it to the ideas site, or present it to the forums with a brief description of what you're doing. The Runtime team (Mike, etc) are very accepting of feedback. Theres many driving factors which determined what tools made the cut, so simply bringing up a good use case might help them be considered.

GeorgeFaraj

Let me see if I understand what you're saying.

I can use ArcMap to create a GPK with only the set of tools that I need, and I can have the geometry passed through a GP parameter when executing the tool.

Is this accurate?

KevinHibma

Let me see if I understand what you're saying.

I can use ArcMap to create a GPK with only the set of tools that I need, and I can have the geometry passed through a GP parameter when executing the tool.

Is this accurate?

Yeah - more or less.
You'll have to run the tool to get a result to turn into a GPK...
But if you have 3 or 4 workflows, get some "sample" data, construct each workflow, run each, then build them into the single GPK.

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?

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

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

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

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

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

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

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

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

GeorgeFaraj

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

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

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.

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.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

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