DownloadEstimator request failed

[techworldthink]

When I try to export a dataset with the "Crop dataset to current viewport" option enabled, I get an error like this:

"DownloadEstimator request failed which means that exported file exceeds configured server limits. Try to change download options or add filter to your layer and try again."

How to increase server limits?

[EHJ-52n]

I had the same problem. The nginx, django and celery server logs do not provide any hints, which service limits need adjustment. It seems to be an GeoServer limit, because there is a POST request executed. In the ends, it is the wps download plugin of the GeoServer, hence its limits needs to be adjusted. The according documentation can be found here:

https://docs.geoserver.org/2.19.x/en/user/extensions/wps-download/index.html

On this page, you can find the documentation regarding the limits, we are talking about:

https://docs.geoserver.org/2.19.x/en/user/extensions/wps-download/index.html#configuring-the-limits

I watched my GeoServer logs and received a useful error message:

geoserver_NN_geonode  | 20 Sep 11:33:16 ERROR [gs.download] - MaxFeatures limit exceeded. 224810 > 100000

I increase the according limit in the download.properties and the download is working like a charm.

I would recommend to add the GeoServer log message to the response of the DownloadEstimator process response. That would enable GeoNode to provide better error messages. Or at least provide the link to the documentation about the downloader plugin and its limit configuration.

[ridoo]

Nice to add that the geoserver logs are a bit hidden:

docker-compose exec geoserver tail -f /geoserver_data/data/logs/geoserver.log

Not sure, why this is not streamed to the Docker stdout.

[EHJ-52n]

Interesting, my set-up did it. I just followed the logs with docker compose logs -f --tail=0 geoserver just before executing the export request.

[saxas13]

@EHJ-52n We have a similar problem only with cropping data downloads ... while there is no problem to download a whole tiff or whole vector dataset (after adjusting the WPS download properties), cropping to "visible" extent throws an instant error and the download gets aborted instantly. We can filter the data and download filtered datasets, but as soon as we want to use the current extent it will just not work. The Limits seem not to be the problem here, as a whole dataset should be larger/more features/pixel than a subset. I tested it also with the stable version, where this also happens. Regarding the response preview, the ROI seems not to be used and therefor the "current extent" is not possible to be used. Payload from test request: Preview from request:

This happens, even if only one object would be in the final dataset

[massoudhamad]

I have the same problem regarding the same issue, Is there anyone who gets the solution?

[EHJ-52n]

@massoudhamad Did you follow all steps in detail that I mentioned in my previous comment?