Hi,
I posted a patch to solve this issue... It fecthes the metadata
from the subdaset opened (it keeps the global metadata and it adds the
subdaset metadata to it) I tested it and it is working... Please
review it to see it isn' disruptive with the rest of the driver's
logic.
http://trac.osgeo.
Hi all, I updated the ticket with what was discussed with Antonio...
http://trac.osgeo.org/gdal/ticket/4121#comment:3
The defect is still there
Regards
Alex
PS:Sorry for the delay but the weekend was a national holyday...
2011/6/18 Antonio Valentino
> Hi Alex,
>
> Il 16/06/2011 17:27, Al
Hi Alex,
Il 16/06/2011 17:27, Alex Mantaut ha scritto:
> Then, to keep consistency, the fact that hdf5imagedataset isn't consistent
> with the hdf5dataset is a defect, right?
> May I summarize the conclusions and update the ticket?
OK
--
Antonio Valentino
___
Then, to keep consistency, the fact that hdf5imagedataset isn't consistent
with the hdf5dataset is a defect, right?
May I summarize the conclusions and update the ticket?
thanks for your patience Antonio
2011/6/16 Antonio Valentino
> Hi Alex,
>
> Il giorno Thu, 16 Jun 2011 11:51:48 -0300
> Alex
Hi Alex,
Il giorno Thu, 16 Jun 2011 11:51:48 -0300
Alex Mantaut ha scritto:
> Antonio,
>Ok, I understand the asociation between the raster band
> and the metadata, but if you have to explicitally ask for the raster
> band in order to get the metadata there is an inconsistency between
Antonio,
Ok, I understand the asociation between the raster band and the
metadata, but if you have to explicitally ask for the raster band in order
to get the metadata there is an inconsistency between the interface to get
metadata from hdf5dataset and hdf5imagedataset... In hdf5dataset
Hi Alex,
Il giorno Thu, 16 Jun 2011 10:05:42 -0300
Alex Mantaut ha scritto:
> Hi Antonio,
>
> For what I discussed with Frank it seemed that the expected behavior
> was to get the only the data asociated to that subdataset (plus some
> aditional data from root and the other groups) I wasn't sur
Hi Antonio,
For what I discussed with Frank it seemed that the expected behavior was to
get the only the data asociated to that subdataset (plus some aditional data
from root and the other groups) I wasn't sure untill you confirmated...
Well, right now when I open a specific subdataset it gets on
Hi Frank, hi Alex,
Il 15/06/2011 22:34, Frank Warmerdam ha scritto:
> On 11-06-15 03:50 PM, Alex Mantaut wrote:
>> Hi Frank:
>> Thanks for the swift reply.
>> Right now it opens the metadata asociated to the root,
>> and also
>> the metadata asociated with all the other
Frank:
I opened a new defect ticket, and suggested a way around the
problem (I'm not sure if it's the best solution)
http://trac.osgeo.org/gdal/ticket/4121
Regards
2011/6/15 Frank Warmerdam
> On 11-06-15 03:50 PM, Alex Mantaut wrote:
>
>> Hi Frank:
>> Thanks for the swif
On 11-06-15 03:50 PM, Alex Mantaut wrote:
Hi Frank:
Thanks for the swift reply.
Right now it opens the metadata asociated to the root, and also
the metadata asociated with all the other groups, but it doesn't open the
metadata asociated to the specified element (bug?)
Hi Frank:
Thanks for the swift reply.
Right now it opens the metadata asociated to the root, and also
the metadata asociated with all the other groups, but it doesn't open the
metadata asociated to the specified element (bug?)
regards
2011/6/15 Frank Warmerdam
> On 11-06
On 11-06-15 03:19 PM, Alex Mantaut wrote:
Hi all,
I'm trying to open the metadata from a subdataset of an HDF5 file...
When I open the file by it's filename and then ask for the metadata it
returns the metadata asociated to the root and all the subdatasets But when
I open th
Hi all,
I'm trying to open the metadata from a subdataset of an HDF5 file...
When I open the file by it's filename and then ask for the metadata
it returns the metadata asociated to the root and all the subdatasets
But when I open the file by specifying the subdataset name to
14 matches
Mail list logo
