[gdal-dev] Re: can ogr2ogr split polygons that cross 180 degree longitude

Even Rouault even.rouault at mines-paris.org
Tue Sep 29 17:43:51 EDT 2009


Selon Mateusz Loskot <mateusz at loskot.net>:

The output message doesn't enable us to know where the crash occurs : in GEOS or
in GDAL. If it was in GDAL, I've tried in r17712 + r17713 to be more robust if
both intersections are NULL and hopefully avoid it. No warranty, I couldn't
reproduce your precise issue. If it still persists, attaching a debugger and
reporting the stack trace when it segfaults might be helpful.

> Hermann Peifer wrote:
> >> What does geos-config --version say?
> >
> > Before, it said: 3.0.0rc1, I now upgraded to 3.1.1
> >
> > The upgrade improved the situation somewhat: "ERROR 6: GEOS support not
> > enabled." is gone now.
>
> Good.
>
> > However, ogr2ogr -wrapdateline -t_srs EPSG:4326
> > ... results now into:
> >
> > ERROR 1: TopologyException: found non-noded intersection between 268.426
> > 48.093, 268.537 48.0578 and 269.967 48.0697, 237.581 48.0657 268.5 48.0695
> > ERROR 1: TopologyException: found non-noded intersection between 268.426
> > 48.093, 268.537 48.0578 and 269.967 48.0697, 237.581 48.0657 268.5 48.0695
> > Segmentation fault
>
> I can only confirm that this error comes from GEOS library and
> usually indicates invalid data
>
> http://trac.osgeo.org/geos/ticket/155
> http://trac.osgeo.org/geos/ticket/253
> http://trac.osgeo.org/geos/ticket/275
>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
> Charter Member of OSGeo, http://osgeo.org
>




More information about the gdal-dev mailing list