Geo-processing service testing/debugging
Thanks for the breakdown, Robert.
In regards to #1, the best way to debug isn't always by taking it back to the Desktop environment. Have you enabled INFO or at least WARNING/SEVERE messages on the GP task? Is it a Python error, or GP runtime error? Have you tried this in an OOTB application with an OOTB widget like the WAB and GP widget?
For #2, I don't work much with JS, but a geoprocessing feature set would inherit the spatial extent information that was used to define the template for the feature set.
For the last point, a feature class and a feature set on the web are both JSON based on geometry objects. This allows GP tasks to work against feature services. The fields are also going to be defined by the template you set for the feature set. If the template resides in an FGDB or SDE database, then the fields will honor the requirements of that workspace, (all caps OBJECTID, etc).
Is there a sample script you've worked with that works in DT but fails to run when it's a service? Using the very simple example script below, I see no problems using feature sets or arcpy.da.SearchCursor:
import arcpy, arcpy.da
inFeatures = arcpy.GetParameter(0)
arcpy.AddMessage("In feature fields:")
fields = arcpy.ListFields(inFeatures)
for field in fields:
arcpy.AddMessage(" " + field.name,)
arcpy.AddMessage("In feature records:")
with arcpy.da.SearchCursor(inFeatures,["*"]) as cursor:
for row in cursor:
arcpy.AddMessage(" " + str(row))
arcpy.Buffer_analysis(inFeatures,"in_memory/outBuffer","50 Meters")
arcpy.AddMessage("Out feature fields:")
fields = arcpy.ListFields("in_memory/outBuffer")
for field in fields:
arcpy.AddMessage(" " + field.name,)
arcpy.AddMessage("Out feature records:")
with arcpy.da.SearchCursor("in_memory/outBuffer",["*"]) as cursor:
for row in cursor:
arcpy.AddMessage(" " + str(row))
arcpy.SetParameter(1,"in_memory/outBuffer")When run in DT:
When run in the WAB using the out of the box GP widget:
Input feature set:
{"geometryType":"esriGeometryPoint","features":[{"geometry":{"x":-10913414.138825795,"y":5223384.6259502,"spatialReference":{"wkid":102100}}},{"geometry":{"x":-11077295.127469169,"y":4753755.524166201,"spatialReference":{"wkid":102100}}},{"geometry":{"x":-10536732.463436546,"y":4922528.482619826,"spatialReference":{"wkid":102100}}},{"geometry":{"x":-10426663.142705921,"y":5267412.35424245,"spatialReference":{"wkid":102100}}},{"geometry":{"x":-10935428.00297192,"y":5551146.603236948,"spatialReference":{"wkid":102100}}}],"sr":{"wkid":102100}}
Output results:
{"jobId":"jee4650a66f2c4836a7bff7b2370b5bb7","jobStatus":"esriJobSucceeded","results":{"Output":{"paramUrl":"results/Output"}},"inputs":{"Input_Feature":{"paramUrl":"inputs/Input_Feature"}},"messages":[{"type":"esriJobMessageTypeInformative","description":"Executing (Feature Set Buffer): FeatureSetBuffer \"Feature Set\""},{"type":"esriJobMessageTypeInformative","description":"Start Time: Thu May 04 17:03:43 2017"},{"type":"esriJobMessageTypeInformative","description":"Executing (FeatureSetBuffer): FeatureSetBuffer \"Feature Set\""},{"type":"esriJobMessageTypeInformative","description":"Start Time: Thu May 04 17:03:43 2017"},{"type":"esriJobMessageTypeInformative","description":"Running script FeatureSetBuffer..."},{"type":"esriJobMessageTypeInformative","description":"In feature fields:"},{"type":"esriJobMessageTypeInformative","description":" OBJECTID"},{"type":"esriJobMessageTypeInformative","description":" SHAPE"},{"type":"esriJobMessageTypeInformative","description":"In feature records:"},{"type":"esriJobMessageTypeInformative","description":" (1, (-10913414.138825797, 5223384.62595021))"},{"type":"esriJobMessageTypeInformative","description":" (2, (-11077295.127469167, 4753755.5241662115))"},{"type":"esriJobMessageTypeInformative","description":" (3, (-10536732.463436548, 4922528.482619822))"},{"type":"esriJobMessageTypeInformative","description":" (4, (-10426663.142705921, 5267412.3542424515))"},{"type":"esriJobMessageTypeInformative","description":" (5, (-10935428.002971917, 5551146.603236951))"},{"type":"esriJobMessageTypeInformative","description":"Out feature fields:"},{"type":"esriJobMessageTypeInformative","description":" OBJECTID"},{"type":"esriJobMessageTypeInformative","description":" SHAPE"},{"type":"esriJobMessageTypeInformative","description":" BUFF_DIST"},{"type":"esriJobMessageTypeInformative","description":" ORIG_FID"},{"type":"esriJobMessageTypeInformative","description":"Out feature records:"},{"type":"esriJobMessageTypeInformative","description":" (1, (-10913414.1388, 5223384.626000001), 50.0, 1)"},{"type":"esriJobMessageTypeInformative","description":" (2, (-11077295.1275, 4753755.5242), 50.0, 2)"},{"type":"esriJobMessageTypeInformative","description":" (3, (-10536732.4634, 4922528.4826000035), 50.0, 3)"},{"type":"esriJobMessageTypeInformative","description":" (4, (-10426663.1427, 5267412.354199997), 50.0, 4)"},{"type":"esriJobMessageTypeInformative","description":" (5, (-10935428.003, 5551146.603200003), 50.0, 5)"},{"type":"esriJobMessageTypeInformative","description":"Completed script FeatureSetBuffer..."},{"type":"esriJobMessageTypeInformative","description":"Succeeded at Thu May 04 17:03:45 2017 (Elapsed Time: 1.87 seconds)"},{"type":"esriJobMessageTypeInformative","description":"Succeeded at Thu May 04 17:03:45 2017 (Elapsed Time: 1.89 seconds)"}]}
Of course this is a very simple example and you're likely doing something more complex but the underlying idea is that if it works in Desktop, in nearly all cases it will work exactly the same as a service.
I should add what the script tool parameters looks like:
I've set the input feature to be a feature set and defined the schema as a newly created point feature class.
When run in ArcMap, it gives me the ability to digitize a feature or browse to an existing feature:
Something that may help is including the original feature(s) in the service, so the input features are populated at Rest:
This does't mean it will only run with those features, but instead there's a default value. You can run the tool directly from the REST endpoint without needing to update any parameters:
