[gdal-dev] Motion: Adopt RFC 41 : Support for multiple geometry fields in OGR

Hi, Motion: I move to adopt RFC 41 : Support for multiple geometry fields in OGR http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields I've made a few changes in the last few days. See the history : http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields?action=history

Re: [gdal-dev] Motion: Adopt RFC 41 : Support for multiple geometry fields in OGR

+1 Frank On Jul 29, 2013 4:14 AM, Even Rouault even.roua...@mines-paris.org wrote: Hi, Motion: I move to adopt RFC 41 : Support for multiple geometry fields in OGR http://trac.osgeo.org/gdal/wiki/rfc41_multiple_geometry_fields I've made a few changes in the last few days. See the

Re: [gdal-dev] Working with NTF files

Nikos Alexandris: I am trying to handle ntf files (NITF) as easy as possible -- working with some WorldView 01/02 and QuickBird imagery. [..] 2) A second, of less importance, question, is: how important are the warnings like: Warning 1: Unable to save auxilary information in

Re: [gdal-dev] [GRASS-user] Working with NTF files

Should I file for this a ticket in GRASS' trac first? Nikos --%--- 1) Markus Metz wrote: What says g.proj georef=your_geofile -p? Nikos Alexandris: g.proj -p georef=15JUN11IK0101000po_697515_pan_000.ntf Trying to open with OGR... ...succeeded. WARNING: Read of file

Re: [gdal-dev] Working with NTF files

A workaround to your 2nd question is to set the GDAL_PAM_PROXY_DIR environment variable, either permanently or on the commandline before you call gdalinfo. set GDAL_PAM_PROXY_DIR=%TEMP% gdalinfo -stats some.ntf -- View this message in context: