Re: [gdal-dev] Motion: Adopt RFC 29: OGR Set Ignored Fields

2010-08-08 Thread Peter J Halls
Frank, Frank Warmerdam wrote: On Fri, Aug 6, 2010 at 10:48 AM, Tamas Szekeres wrote: +1 I assume that this feature will be utilized in the OGR sql query processor and not directly in the ogr2ogr application. Tamas, ogr2ogr has a -select switch to identify desired fields to be copied to the

Re: [gdal-dev] Re: How to retain double precision in GDAL?

2010-08-08 Thread Chaitanya kumar CH
Ole, This option is for the AAIGRID driver. So this option is valid any time the format is handled. In a python script you set the option you need to set this option during the call to gdal.Open() to set a specific datatype. Refer to http://trac.osgeo.org/gdal/browser/trunk/autotest/gdrivers/aaig

[gdal-dev] Re: How to retain double precision in GDAL?

2010-08-08 Thread Ole Nielsen
Thanks for fixing the precision loss so quickly. "you now can set the configuration option AAIGRID_DATATYPE to Float64 to force Float64 being used to avoid the loss of precision." I am not exactly sure whether this option relates to the gdal_translate command line utility or the Python binding (

Re: [gdal-dev] vsizip & vsigzip on Win

2010-08-08 Thread Joaquim Luis
Sorry for the noise. I found that the correct syntax is gdalinfo /vsizip/c:\m_gmt_so\tmp\N37W008.hgt.zip\N37W008.hgt and like that it works fine. Joaquim Hi, I'm trying to access ziped files on Windows using the /vsizip but it fails most of times According to docs, this should work no? g

[gdal-dev] vsizip & vsigzip on Win

2010-08-08 Thread Joaquim Luis
Hi, I'm trying to access ziped files on Windows using the /vsizip but it fails most of times According to docs, this should work no? gdalinfo c:/vsizip/m_gmt_so/tmp/N37W008.hgt.zip/N37W008.hgt but it doesn't. I get ERROR 4: `c:/vsizip/m_gmt_so/tmp/N37W008.hgt.zip/N37W008.hgt' does not exist

[gdal-dev] Maintenance report for Jun 17, 2010 to Aug 07, 2010

2010-08-08 Thread Chaitanya kumar CH
Frank, Please find the attached maintenance report for the work done by me. Same can be found at http://trac.osgeo.org/gdal/wiki/MaintenanceReportsByChaitanya#Jun172010toAug072010 -- Best regards, Chaitanya kumar CH. /tʃaɪθənjə/ /kʊmɑr/ +91-9494447584 17.2416N 80.1426E GDAL Maintenance Reports

Re: [gdal-dev] wrong in LINESTRING

2010-08-08 Thread Even Rouault
2 errors : 1) The WKT is incorrect. You don't need 2 open & closing parenthesis for a LINESTRING. Just one is enough : "LINESTRING(33.0 41.0 0,33.5 42.5 0, 33.9 41.9 0,33.0 41.0 0)" 2) Provided you use GDAL >= 1.7.0, you shouldn't use the Geometry(int eGeometryType, String wkt, byte[] wkb, Stri

[gdal-dev] wrong in LINESTRING

2010-08-08 Thread ahmet temiz
hello I was wondering what I did wrong in the following code ? Geometry line2=new Geometry(1,"LINESTRING((33.0 41.0 0,33.5 42.5 0, 33.9 41.9 0,33.0 41.0 0))", null, null); Feature feature = new Feature(layerDefinition); feature.SetFID(0);

Re: [gdal-dev] Motion: Adopt RFC 29: OGR Set Ignored Fields

2010-08-08 Thread Even Rouault
+ 0 I'm not sure which approach DesiredFields vs IgnoredFields is the best one. Both have their pros and cons. IgnoredFields will be a bit awkward to use, but the main argument for this approach (avoid dropping any special fields) makes sense. I also think that a layer capability can be useful