Re: [gdal-dev] Motion: adopt RFC 66: OGR random layer read/write capabilities

2016-10-05 Thread Daniel Morissette
+1 Daniel On 2016-10-05 6:44 AM, Even Rouault wrote: Hi, I know that Howard has expressed some concerns regarding the potential confusion that this could add, but I'm not sure what better alternatives there would be to address the needs it tries to solve. So I move to adopt RFC 66: OGR random

Re: [gdal-dev] GPKG: Drop table but how to drop the rest?

2016-10-05 Thread Even Rouault
Le jeudi 29 septembre 2016 13:13:17, Even Rouault a écrit : > Hi Jukka, > > > I wonder if it could be possible to do something like "DROP CASCADING" in > > GeoPackage and delete the spatial index by the same. > > I will work in a short term on this (as well as renaming columns) Jukka, I wrote to

Re: [gdal-dev] Need suggestion on clipping vectors in batch

2016-10-05 Thread Even Rouault
Le mercredi 05 octobre 2016 11:29:43, Margherita Di Leo a écrit : > Hi, > > I need a suggestion on the use of ogr2ogr for clipping vector files > (points) in batch. For all them I need to reduce the spatial extent of a > certain quantity DX, DY, so it would be > > ymax = ymax_current - DY > ymin

Re: [gdal-dev] Need suggestion on clipping vectors in batch

2016-10-05 Thread David J. Bakeman
On 10/05/2016 02:29 AM, Margherita Di Leo wrote: Hi, I need a suggestion on the use of ogr2ogr for clipping vector files (points) in batch. For all them I need to reduce the spatial extent of a certain quantity DX, DY, s

Re: [gdal-dev] Motion: adopt RFC 66: OGR random layer read/write capabilities

2016-10-05 Thread jratike80
+1 -Jukka Rahkonen- Even Rouault-2 wrote > Hi, > > I know that Howard has expressed some concerns regarding the potential > confusion that this could add, but I'm not sure what better alternatives > there > would be to address the needs it tries to solve. > > So I move to adopt RFC 66: OGR r

Re: [gdal-dev] Motion: adopt RFC 66: OGR random layer read/write capabilities

2016-10-05 Thread Howard Butler
+1 I couldn't come up with anything better, and I was mostly lamenting the need to add more to the API surface. Howard > On Oct 5, 2016, at 5:53 AM, Tamas Szekeres wrote: > > +1 > > Tamas > > > > 2016-10-05 12:44 GMT+02:00 Even Rouault : > Hi, > > I know that Howard has expressed some co

Re: [gdal-dev] Need suggestion on clipping vectors in batch

2016-10-05 Thread Antonio Falciano
Il 05/10/2016 11:29, Margherita Di Leo ha scritto: Hi, I need a suggestion on the use of ogr2ogr for clipping vector files (points) in batch. For all them I need to reduce the spatial extent of a certain quantity DX, DY, so it would be ymax = ymax_current - DY ymin = ymin_current + DY xmax = xm

Re: [gdal-dev] Motion: adopt RFC 66: OGR random layer read/write capabilities

2016-10-05 Thread Tamas Szekeres
+1 Tamas 2016-10-05 12:44 GMT+02:00 Even Rouault : > Hi, > > I know that Howard has expressed some concerns regarding the potential > confusion that this could add, but I'm not sure what better alternatives > there > would be to address the needs it tries to solve. > > So I move to adopt RFC 6

[gdal-dev] Motion: adopt RFC 66: OGR random layer read/write capabilities

2016-10-05 Thread Even Rouault
Hi, I know that Howard has expressed some concerns regarding the potential confusion that this could add, but I'm not sure what better alternatives there would be to address the needs it tries to solve. So I move to adopt RFC 66: OGR random layer read/write capabilities https://trac.osgeo.org/

[gdal-dev] Need suggestion on clipping vectors in batch

2016-10-05 Thread Margherita Di Leo
Hi, I need a suggestion on the use of ogr2ogr for clipping vector files (points) in batch. For all them I need to reduce the spatial extent of a certain quantity DX, DY, so it would be ymax = ymax_current - DY ymin = ymin_current + DY xmax = xmax_current - DX xmin = xmin_current + DX I could cal