Hi Even
On Sat, May 7, 2011 at 7:16 PM, Even Rouault
even.roua...@mines-paris.org wrote:
Hi,
I've written a new RFC to add the capability to delete fields, reorder fields
and alter field definitions, in OGR layer definitions.
On 5/9/2011 7:54 AM, Martin Dobias wrote:
Hi Even
On Sat, May 7, 2011 at 7:16 PM, Even Rouault
even.roua...@mines-paris.org wrote:
Hi,
I've written a new RFC to add the capability to delete fields, reorder fields
and alter field definitions, in OGR layer definitions.
Martin,
I have just two comments:
- is the alternation of hte field definition going to have some rules
how the existing data should be converted to the new type or will the
driver itself choose how to convert the data? The latter option is
surely the easier one, but it would be probably
I've updated http://trac.osgeo.org/gdal/wiki/rfc35_deletereorderalterfielddefn
to introduce OGRLayer::ReorderFields(), to reorder all the fields at once.
I've kept a (non-virtual) ReorderField() to be able to move easily a single
field. ReorderField() is just a wrapper that generates the
Hi,
I've written a new RFC to add the capability to delete fields, reorder fields
and alter field definitions, in OGR layer definitions.
http://trac.osgeo.org/gdal/wiki/rfc35_deletereorderalterfielddefn
Currently, an OGR layer definition can only be altered to add a new field
On 11-05-07 01:16 PM, Even Rouault wrote:
Hi,
I've written a new RFC to add the capability to delete fields, reorder fields
and alter field definitions, in OGR layer definitions.
http://trac.osgeo.org/gdal/wiki/rfc35_deletereorderalterfielddefn
Currently, an OGR layer definition can
I would like to see some description of the effect of ReorderField(). I
assume iOldFieldPos and iNewFieldPos have to both be existing fields, and
that intermediate fields will be shuffled along as needed to satisfy the
request - is that right?
Yes, exactly. iOldFieldPos and iNewFieldPos
