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 -260
> 570 310
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 -260
570 310 1050 -skipfailures
".\temp\nfdb_poly_20111223_21094F1A58AE467E\n
Le mercredi 07 mai 2014 20:30:45, scottm361 a écrit :
> I am a developer on an application that will potentially use ogr2ogr to
> re-project shapefiles (and potentially other ogr supported formats)
>
> What I am wondering about is the nature of geometry error handling in
> ogr2ogr. My assumption
I am a developer on an application that will potentially use ogr2ogr to
re-project shapefiles (and potentially other ogr supported formats)
What I am wondering about is the nature of geometry error handling in
ogr2ogr. My assumption is that geometry errors are quite common in user
supplied data,
