Le jeudi 08 mai 2014 00:54:50, scottm361 a écrit : > Hi Even > > Thanks for the reply. > > the command I am using does use clipping, but not spatial filtering: > > gdal\apps\ogr2ogr.exe -overwrite -t_srs > "layers\NFI_MODIS250m_kNN_Structure_Stand_Age_v0.prj" -clipdst -2600000 > 5700000 3100000 10500000 -skipfailures > ".\temp\nfdb_poly_20111223_21094F1A58AE467E\nfdb_poly_20111223_21094F1A58AE > 467E.shp" "layers\fire\nfdb_poly_20111223.shp" > > Is there an alternative way to do this that I should use?
No, that's fine. Looking at the code, when the GEOS errors occur, it is likely that the feature whose intersection with the clip bounding box causes the error will not be written. -skipfailures is not really taken into account in that matter (the GEOS error does not count as a failure for ogr2ogr, but is considered as a null intersection) With some efforts, you could try to extract the feature that cause the issue and analyze if the GEOS error is logical or if it is a bug. > > Scott > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/ogr2ogr-error-handling-tp5139067p51391 > 15.html Sent from the GDAL - Dev mailing list archive at Nabble.com. > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev -- Geospatial professional services http://even.rouault.free.fr/services.html _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
