[gdal-dev] Handle geojson bigger than 200MB

[Francesco Bartoli]

However, we are using both modules so how can we handle exceptions properly for both of them?

Using ogr.UseExceptions() the call https://github.com/geopython/pygeoapi/pull/372/files#diff-b105ae3f7a36059b16bdc16a08071016R361 gives the same result silently without any message to system output this time.

Thanks,
Francesco
Il 28 feb 2020, 15:19 +0100, Even Rouault <even.rouault at spatialys.com>, ha scritto:
> On vendredi 28 février 2020 15:10:46 CET Francesco Bartoli wrote:
> > Dear devs,
> >
> > In the pygeoapi project we are experiencing this
> > issue https://github.com/geopython/pygeoapi/issues/371. I've just started a
> > PR https://github.com/geopython/pygeoapi/pull/372 hich basically tries to
> > catch if all properties of the feature have null values and raise an
> > exception ourself. Catching null values is due because GDAL doesn't throw
> > the exception if OGR_GEOJSON_MAX_OBJ_SIZE has the default value. I'm
> > wondering if this is a bug or an expected behavior. If it is then I will
> > file an issue.
>
> Use ogr.UseExceptions() (instead of gdal.UseExceptions())
>
> Enabling exceptions is controlled separately in the 2 Python modules.
>
> Even
>
> --
> Spatialys - Geospatial professional services
> http://www.spatialys.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20200228/84a6d19e/attachment-0001.html>