I use ArcGIS Server 10 SP3. My question is, if this bug is fixed in SP3 for the REST SOE input parameters, did it fix also in the GeometryService? If not, is there something to do?
I think, the GeometryService has still this bug. This is why:
When I call Simplify (with a large geometry) operation of the geometryService, I got this error:
GeometryService service = new GeometryService(this.GeometryServiceUrl); service.SimplifyAsync(graphics);
It's sure, I could make my own SOE to do the same job but I would like to use the services deliveries by ESRI. If the Geometry service has the bug, do you know if QueryTask has also this bug.
I help would be very appreciate because I'm stuck with it and I must delivery my solution very soon.
This MaxJsonLength limit applies to Geometry service. The fix in 10.0 SP3 is specific to SOE's and GeoProcessing services.
The default limit for JSON is about 4MB. We are trying to understand use-cases where JSON larger than this limit is posted as input to service? Have you considered options such as generalizing the geometry using the MaxAllowableOffset parameter in query response.
Please let us know. You can contact ESRI Support and provide details about the application/use-case that requires this support.
I have SP3 installed and this does fix the issue with JSON Serializer on lengthy input geometries. The problem I am facing now is that the ESRI.ArcGIS.REST.SOE.SOERESTJsonFormatter.WriteJsonResponse bombs when trying to format a response that is larger than ~ 100,000 characters. The context here is a utility network trace that brings back roughly 500 - 600 features. The problem seems to occur when these features have a large number of attributes or vertices causing the response to exceed the JSON formatter.
It appears that responses coming from non-SOE operations (identify, query) surpass this limit and are formatted fine. It only occurs on the SOE REST JSON Formatter.