Geoprocessor always returns the same results
Hi,
A strange behavior is happening.
I have a geoprocessing service (arcpy script) that I'm using in a workflow. Basically, it uses a DisplayCaptureGeometry to run a trace in a geometric network in that location.
Using this workflow, it always returns the same set of results, the same ones from when I published the geoprocessing service in ArcGIS Desktop.
The geoprocessing service runs normally in ArcGIS Desktop, Web App Builder and ArcGIS Viewer for Silverlight, so I can safely assume that the script is correct.
The parameters that I'm using in the workflow are very simple. I'm checking the XY coordinates of the Faults variable just before entering the Geoprocessor and they are correct. The GPMains, GPLaterals, GPClients and GPValves are my feature layer outputs. Right a fter the Geoprocessor I check the features returned and the set is always the same, so it appears that the problem is in the Geoprocessor.
/customer/servlet/servlet.FileDownload?file=00P6000000elzitEAA
Any suggestion how to solve this problem? I'm really out of ideias.
Thanks,
Pedro Cruz
-
I'd suggest publishng your service with null values for your optional parameters. I've had issues before with this where any value I defined in an optional parameter seemed to stick, regardless if I was over-writing it.
Maybe you want to write the values coming into your script at the top, just to see what they are too.
Just some ideas.
0 -
Ryan,
Thank you for your reply.
Actually the optional parameter (the barriers) was already null when I published the service. Following you suggestion, I published the service again with the barriers not null but the result was the same.
The values appear to be fine. I picked the values in the workflow before entering the Geoprocessor and used them directly by rest and the result was correct.
Thanks again.
Pedro Cruz
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
2 Kommentare