On Thu, Sep 3, 2015 at 5:41 PM, Even Rouault
wrote:
> > Sure. The patch is for 1.11 branch. Should I generate the same for trunk
> > also?
>
> Yes please
>
> >
> > As we are on the subject of metadata in hdf5 dataset, there is Header
> too
> > long. .. Truncated warning appearing when type is d
increasing the limit of MAX_METADATA_LEN is acceptable?
On Tue, Sep 1, 2015 at 8:07 PM, Rashad M wrote:
>
>
> On Tue, Sep 1, 2015 at 5:08 PM, Even Rouault
> wrote:
>
>> Le mardi 01 septembre 2015 16:50:32, Rashad M a écrit :
>> > Hello all,
>> >
>>
Hello Even,
On Thu, Sep 3, 2015 at 5:13 PM, Even Rouault
wrote:
> Le jeudi 03 septembre 2015 16:58:34, Rashad M a écrit :
> > Hello all,
> >
> > I have an problem when reading metadata information of HDF5 dataset. some
> > of the values are not parsed properly by
Hello all,
I have an problem when reading metadata information of HDF5 dataset. some
of the values are not parsed properly by GDAL. Below is the relevant part
of output from gdalinfo
Azimuth_Processing_Number_of_Looks=
Bits_per_Sample=
S01_B001_Azimuth_Ramp_Code=
Sam
On Tue, Sep 1, 2015 at 5:08 PM, Even Rouault
wrote:
> Le mardi 01 septembre 2015 16:50:32, Rashad M a écrit :
> > Hello all,
> >
> > I have an the following warning from gdal when reading .h5 dataset
> >
> > Warning 2: Header data too long. Truncat
Hello all,
I have an the following warning from gdal when reading .h5 dataset
Warning 2: Header data too long. Truncated.
Looking at frmts/hdf5/hdf5dataset.cpp there is a define for
MAX_METADATA_LEN
#define MAX_METADATA_LEN 32768
and there is a check
if( CPLStrlcat(szValue, sz
On Sun, Aug 2, 2015 at 9:05 PM, Even Rouault
wrote:
> >
> > No API changes. it make building and configuring libkml easier!
> >
> > Correct me If I am wrong, I guess with a pkg-config would be easier to
> find
> > and configure libkml libs.
>
> Yes, that would probably be better. That said my exp
On Sun, Aug 2, 2015 at 8:12 PM, Even Rouault
wrote:
> Rashad,
>
> > Hello all,
> >
> > We have been working on a new fork of libkml library on github. The
> primary
> > interest to detach from google/libkml was that various modification in
> the
> > library are fragmented in the github forks and
Hello all,
We have been working on a new fork of libkml library on github. The primary
interest to detach from google/libkml was that various modification in the
library are fragmented in the github forks and nothing gets merged. There
is no activity or interest by original authors and all efforts
Hello Yuchen,
Isn't possible to update existing google libkml driver in GDAL with an
option for streaming.?
As Sebastiaan and Dimtry said, google libkml is highly inactive on both
googlecode.com and github.com/google/libkml.
For this reason we created libkml as new fork [1] hoping it will ease u
On Tue, Feb 3, 2015 at 9:47 AM, Even Rouault
wrote:
> Le mardi 03 février 2015 08:02:58, Rashad M a écrit :
> > Hello,
> >
> > Is it possible to use existing libz when building gdal on msvc. On linux
> I
> > can pass --with-libz= during configure. But on windows I c
Hello,
Is it possible to use existing libz when building gdal on msvc. On linux I
can pass --with-libz= during configure. But on windows I couldn't find any
options in the be-alike nmake.opt
Also in gdal/port/Makefile.vc there is zlib includes in EXTRAFLAGS which
points to internal zlib from frmt
Hello Chris,
On Mon, Nov 3, 2014 at 9:45 PM, Chris Hanson wrote:
> I'm wondering if anyone here has succeeded, attempted, or just
> investigated compiling GDAL (and PROJ4) via Emscripten into Javascript
> asm.js dialect to run in a browser? We're looking at some web/client side
> code that wou
On Sat, Aug 2, 2014 at 8:29 PM, Even Rouault
wrote:
> Le mercredi 30 juillet 2014 15:04:42, Rashad M a écrit :
> > Hello all,
> >
> >
> > Is it possible to read high dynamic range files using GDAL?
>
> Not currently. And HDR seems to refer more to a general tech
Hello all,
Is it possible to read high dynamic range files using GDAL?
$ gdalinfo ./memorial.hdr
ERROR 4: `./memorial.hdr' not recognised as a supported file format.
gdalinfo failed - unable to open './memorial.hdr'
gdal installed from standard Fedora 20 x86_64 repository
gdal-config --versi
15 matches
Mail list logo
