In general, from my point-of-view limiting the growth of utility code,
which is not available to bindings, or making some of that code
available to bindings is a good thing.
Ari
On 11/23/2011 12:57 AM, Even Rouault wrote:
Hm, after some thinking I think the best approach is to construct the
o
>
> Hm, after some thinking I think the best approach is to construct the
> original SQL to assign XML-valid column names. The same change
> can/should be done in for the WFS DescribeFeature response. The the
> CopyLayer method should work ok (seems so after initial tests).
My initial thought was
On 11/21/2011 08:57 PM, Even Rouault wrote:
Le lundi 21 novembre 2011 11:20:33, Ari Jolma a écrit :
Hi,
I'm making a new GML layer from an existing layer. For some reason the
CopyLayer method leaves adjusted fields out but CreateField,
CreateFeature sequence does not. I guess they should be ide
> Hi,
>
> another thing I noticed while using CopyDataSource, which might be
> related to CopyLayer, that's why I am posting this here: the driver is
> lost, don't know if this is intentional ... see the short code example below
Frank,
No, this is not intentional. CopyDataSource() should assign
Am 21.11.2011 19:57, schrieb Even Rouault:
Le lundi 21 novembre 2011 11:20:33, Ari Jolma a écrit :
Hi,
I'm making a new GML layer from an existing layer. For some reason the
CopyLayer method leaves adjusted fields out but CreateField,
CreateFeature sequence does not. I guess they should be iden
Le lundi 21 novembre 2011 11:20:33, Ari Jolma a écrit :
> Hi,
>
> I'm making a new GML layer from an existing layer. For some reason the
> CopyLayer method leaves adjusted fields out but CreateField,
> CreateFeature sequence does not. I guess they should be identical?
>
> i.e.
>
> my $datasource
Hi,
I'm making a new GML layer from an existing layer. For some reason the
CopyLayer method leaves adjusted fields out but CreateField,
CreateFeature sequence does not. I guess they should be identical?
i.e.
my $datasource = Geo::OGR::Open('Pg:...');
my $l = $datasource->ExecuteSQL('...');
m
