[gdal-dev] GML / NAS code redundancy

Even Rouault even.rouault at mines-paris.org
Sun Apr 6 04:05:25 PDT 2014


Le dimanche 06 avril 2014 13:00:33, Martin Landa a écrit :
> Hi,
> 
> 2014-04-06 12:52 GMT+02:00 Even Rouault <even.rouault at mines-paris.org>:
> > The "fix" would be more in ogr2ogr that currently has the following logic :
> >   does the output driver support multiple geometry fields ?
> >   
> >         - yes : does the source layer has several geometry fields ?
> >         
> >                 - yes : use CreateGeomField() API, and pass wkbNone to
> >                 CreateLayer() - no: pass the geometry type to
> >                 CreateLayer()
> >         
> >         - no : pass the geometry type of the first geometry column to
> > 
> > CreateLayer()
> 
> yes, but it will not influence user scripts, eg. python code which is
> using CopyLayer()...

I've just checked that CopyLayer() should have the same behaviour as the 
algorithm in ogr2ogr.

> 
> Martin

-- 
Geospatial professional services
http://even.rouault.free.fr/services.html


More information about the gdal-dev mailing list