topic Max number of features in an input FeatureSet? in ArcGIS Enterprise Questions

Max number of features in an input FeatureSet?

ToddBryan — Fri, 11 Apr 2014 15:30:01 GMT

We have a geoprocessing service with the following signature:

Parameter: Features 
Data Type: GPMultiValue:GPFeatureRecordSetLayer 
Display Name Features 
Description: Input feature set. 
Direction: esriGPParameterDirectionInput 
Default Value: 
Parameter Type: esriGPParameterTypeRequired 
Category: 

Parameter: Output 
Data Type: GPDataFile 
Display Name Output 
Description: 
Direction: esriGPParameterDirectionOutput 
Default Value: 
Parameter Type: esriGPParameterTypeDerived 
Category:

This GP service converts all the FeatureSets in the input to one shapefile. The actual Python code for the service is dead-simple:

import sys, os, arcpy

features = arcpy.GetParameter(0)
output = os.path.join(arcpy.env.scratchWorkspace, "ssexport.shp")    
arcpy.CopyFeatures_management(features, output)    
arcpy.SetParameter(1, output)

We are calling this service with an array of one FeatureSet. That FeatureSet has N features. The service runs properly when N <= 2000, but when the number of features in the FeatureSet exceeds 2000, the GP script fails with "The workspace is not connected."

There seems to be a limit of 2000 on the number of features in an input feature set. Note that this IS NOT the well-known 1000 feature output limit. Our research in the docs and online reveals no mention of such an input limit, and our careful search of the entire ArcGIS Server configuration directory reveals no server setting for this input limit.

Can someone speak to the existence of this limit and suggest a way to change or circumvent it?

Many thanks -

Todd

Re: Max number of features in an input FeatureSet?

RalfSchmidt — Wed, 13 Sep 2017 07:49:42 GMT

Just in case someone else also visits this page: A few days ago I had the very same problem and it turned out to be a bug in ArcGIS Server, still present in 10.5.1.
Esri Inc. now records this as

BUG-000107968 -- Running geoprocessing service with more than 2000 output features causes geoprocessing failure with the error message "The workspace is not connected".

Please note that the text is not completely correct: It's the number of input features – not the number of output features – that causes problem.

Re: Max number of features in an input FeatureSet?

RebeccaStrauch__GISP — Wed, 13 Sep 2017 15:24:15 GMT

I converted the thread from a discussion to a question, which typically gets more views/response. I will mark Ralf's answer as the correct answer since he listed the bug (and it still exists).

trbryan if you are still having issues and/or found a workaround, a summary would be helpful for others (and you can change the correct-answer selection if needed).

Re: Max number of features in an input FeatureSet?

JonathanQuinn — Wed, 13 Sep 2017 21:23:42 GMT

Are you running this through REST or SOAP? The bug details seem to imply that REST works, but SOAP is the problem.