Closed francbartoli closed 4 years ago
However, no exceptions have been thrown when the error happened. This is strange because we have called
gdal.UseExceptions()
in the current code. The result, if the errors are not printed, has all the non-geometrical values null. I think we could mitigate this by throwing an exception if all the values are None and catching it to return a response with a code 500.
Description Working with this dataset:
some features that have geojson output bigger than the default
OGR_GEOJSON_MAX_OBJ_SIZE=200MB
fail with several error messages like:Steps to Reproduce Steps to reproduce the behavior:
For example Indonesia with
adm0_id=272
curl -XGET http://localhost:5000/collections/countries/items/272
Expected behavior It is expected the correct geojson payload of the response. This can be mitigated in GDAL version 3.0.2 and above by setting this environment variable:
However the error happening in the code is not handled properly
Screenshots/Tracebacks If applicable, add screenshots to help explain your problem.
Environment
Additional context Add any other context about the problem here.