Re: [gdal-dev] Fwd: Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread Jukka Rahkonen
ridgewang gmail.com> writes: > 3. The tiff file I created is in tiled formation with block size 256x256. So what does the single stripsize means? This means that something has gone wrong. Your sample was not tiled but the blocks were made of single scanlines from left to right. Check with gdalin

Re: [gdal-dev] Fwd: Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread Jukka Rahkonen
ridgewang gmail.com> writes: > > ok. There are also some questions I want to clarified: > 1. The app I developed is an 32bit app, and it is complex to convert it to 64bit. So I cannot link to the 64bit > gdal dll. > 2. Can I download the 32bit gdal dll from gdal website instead of the 32bit vers

Re: [gdal-dev] Fwd: Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread ridgewang
ok. There are also some questions I want to clarified: 1. The app I developed is an 32bit app, and it is complex to convert it to 64bit. So I cannot link to the 64bit gdal dll. 2. Can I download the 32bit gdal dll from gdal website instead of the 32bit version build myself to solve this question?

[gdal-dev] Bus Error (memory error)

2014-02-28 Thread Gpetr
Hello, I was trying to process a raster image via Gdal when it's happened an unexpected error. A Bus Error. After that, QGIS can not start. Also I recieve the same error when I'm trying to execute any of the GDAL commands via terminal. I know that this error happens when a process is trying to acc

Re: [gdal-dev] Fwd: Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread Even Rouault
OK, problem reproduced and fixed. It was specific to 32 bit builds, and with TIFF files made of a single strip of more than 2 GB. (note that your file is a classical "big" TIFF, but not a "BigTIFF") Le vendredi 28 février 2014 18:07:53, ridge wang a écrit : > -- Forwarded message ---

[gdal-dev] Fwd: Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread ridge wang
-- Forwarded message -- From: ridge wang Date: Sat, Mar 1, 2014 at 1:06 AM Subject: Re: [gdal-dev] Can not open bigtiff file using gdal1.10 API saved by photoshop cs6 To: Even Rouault I working on Windows 7 64bit OS, Build the gdal 1.10 32bit version with microsoft visual studio

Re: [gdal-dev] gdal get geolocation array in HDF5 dataset

2014-02-28 Thread Heather QC
Laura, Did you ever sort this out? I am having the same problem with both HDF4 and HDF5. I can open the geolocation datasets if I know the name, but I would like to be able to list them to extract the name and automate. Thanks! Heather -- View this message in context: http://osgeo-org.1560

Re: [gdal-dev] Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread Jean-Claude Repetto
On 28/02/2014 14:04, Jukka Rahkonen wrote: I downloaded the failing tiff http://trac.osgeo.org/gdal/raw-attachment/ticket/5403/1041up_1075down-938-960_spts-740-769-820-922_0.5-782-794_0.5_spts-935-1020_0.5_spts-cut2_spts.zip Gdalinfo and gdal_translate had no troubles at all (Windows 7 64-bit,

Re: [gdal-dev] Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread Even Rouault
Selon ridgewang : > Ps, sometimes it creates bigtiff file without any error reports by gdal 1.10 > api, but can not open the tiff file by gdal api and reports zero stripsize. > anyway, the photoshop cs6 can open the tiff file correctly. for tips that > the file is created and save in a usb mobile

Re: [gdal-dev] Can not open bigtiff file using gdal1.10 API saved by photoshop cs6

2014-02-28 Thread Jukka Rahkonen
ridge wang gmail.com> writes: > > > > Even, > Sorry for reply so late. I create a tickets as http://trac.osgeo.org/gdal/ticket/5403. I attached 2 tiff files, one can opend by gdal and the other cannot. But they all can opend by photoshop correctly. Both of these two original tiff file are

Re: [gdal-dev] cpppcheck warning in ogr_core.h

2014-02-28 Thread Even Rouault
Selon Olivier BARTHELEMY : > Hi, > Cppcheck reports a redundant condition "MaxZ>=other.MaxZ in > OGREnvelope3D::contains() > Isn't it a copy paste error, and isn't the condition MinZ<=other.MinZ > missing? Indeed !, thanks. I've just committed the fix. > > -- > [image: Geovariances] > > Olivier

[gdal-dev] cpppcheck warning in ogr_core.h

2014-02-28 Thread Olivier BARTHELEMY
Hi, Cppcheck reports a redundant condition "MaxZ>=other.MaxZ in OGREnvelope3D::contains() Isn't it a copy paste error, and isn't the condition MinZ<=other.MinZ missing? -- [image: Geovariances] Olivier BARTHELEMY *Software development engineer* Geovariances, 49bis avenue Franklin Roosevelt - 772

Re: [gdal-dev] Cannot compile GDAL 1.10.1 for iOS with spatialite (2, 3 or 4)

2014-02-28 Thread Even Rouault
Selon Nik Sands : > For reference, when I add: > > LDFLAGS="-liconv -lsqlite3" > > And configure says that spatialite is going to be included OK, I eventually > get the error: > > libtool: link: /Applications/Xcode.app/Contents/Developer/usr/bin/g++ -arch > i386 -isysroot > /Applications/Xco

Re: [gdal-dev] Who really owns the OGRFeatureDefn returned by OGRLayer::GetLayerDefn()

2014-02-28 Thread Vincent Mora
On 28/02/2014 10:54, Even Rouault wrote: Hi Vincent, Hi, OGRLayer::GetLayerDefn() doc says "The returned OGRFeatureDefn is owned by the OGRLayer, and should not be modified or freed by the application." Yes, a OGRFeatureDefn created by a layer should not be modified outside of the driver, oth

Re: [gdal-dev] Cannot compile GDAL 1.10.1 for iOS with spatialite (2, 3 or 4)

2014-02-28 Thread Nik Sands
For reference, when I add: LDFLAGS="-liconv -lsqlite3" And configure says that spatialite is going to be included OK, I eventually get the error: libtool: link: /Applications/Xcode.app/Contents/Developer/usr/bin/g++ -arch i386 -isysroot /Applications/Xcode.app/Contents/Developer/Platf

Re: [gdal-dev] Who really owns the OGRFeatureDefn returned by OGRLayer::GetLayerDefn()

2014-02-28 Thread Even Rouault
Hi Vincent, > Hi, > > OGRLayer::GetLayerDefn() doc says "The returned OGRFeatureDefn is owned by > the OGRLayer, > and should not be modified or freed by the application." Yes, a OGRFeatureDefn created by a layer should not be modified outside of the driver, otherwise chaos will happen. > > But

[gdal-dev] Who really owns the OGRFeatureDefn returned by OGRLayer::GetLayerDefn()

2014-02-28 Thread Vincent Mora
Hi, OGRLayer::GetLayerDefn() doc says "The returned OGRFeatureDefn is owned by the OGRLayer, and should not be modified or freed by the application." But in alg/contour.cpp, in OGRContourWriter, the return value ofGetLayerDefn is used to create a feature that apparently takes ownership of the