<div>Hi Antonio,</div>
<div> </div>
<div>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...</div>
<div> </div>
<div>Well, right now when I open a specific subdataset it gets only the raster band asociated to that dataset, but when I try to open the metadata (with GetMetadata() or GetMetadataItem()) from that subdataset it opens the metadata from all the groups (as expected) but it doesn't get the metadata asociated to that subdataset... Did I do something incorrectly when opening the metadata from the subdataset?</div>
<div> </div>
<div>
<div>The line suggested in the ticket:</div>
<div> ReadGlobalAttributes( TRUE );</div>
<div> </div>
<div>Was a way to get around the problem, but now that I'm sure that hdf5imagedataset doesn't need to read all the metadata, it's not a suitable solution to the defect...</div></div>
<div> </div>
<div>Right now I found another way to get the metadata from the subdataset, by getting the rasterband first, and then asking for the metadata asociated to that raster band ( it seems a overly convoluted to get the metadata asociated to that subdataset...) I'm guessing that the expected behavior is to get the information directly through GetMetadata() directly...</div>
<div> </div>
<div>regards</div>
<div><br> </div>
<div class="gmail_quote">2011/6/15 Antonio Valentino <span dir="ltr"><<a href="mailto:antonio.valentino@tiscali.it">antonio.valentino@tiscali.it</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Frank, hi Alex,<br><br>Il 15/06/2011 22:34, Frank Warmerdam ha scritto:<br>
<div class="im">> On 11-06-15 03:50 PM, Alex Mantaut wrote:<br>>> Hi Frank:<br>>> Thanks for the swift reply.<br>>> Right now it opens the metadata asociated to the root,<br>
>> and also<br>>> the metadata asociated with all the other groups, but it doesn't open the<br>>> metadata asociated to the specified element (bug?)<br>><br>> Alex,<br>><br>> It sounds like a defect to me, yes.<br>
><br>> I would suggest filing a ticket that carefully documents the<br>> problem with a supporting example file.<br>><br>> Best regards,<br><br></div>The current behavior looks fine to me.<br><br>If one opens a specific subdataset then only one "HDF5 dataset object"<br>
can be accessed and it is mapped on GDAL raster bans n. 1.<br>All other "HDF5 dataset object" in the h5 file are ignored by the<br>HDF5ImageDataset so there is no reason IMHO to make their metadata<br>available in some manner.<br>
<br>Metadata associated to all HDF5 groups (including the root one) are<br>available in any case and accessible via GDAL dataset metadata.<br><br>my two cents<br><br>--<br><font color="#888888">Antonio Valentino<br></font>
<div>
<div></div>
<div class="h5">_______________________________________________<br>gdal-dev mailing list<br><a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/gdal-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>--<br> Alex Mantaut<br>SUR Emprendimientos Tecnológicos<br><br>Perú 345 Piso 5to Oficina "B" (C1067AAG)<br>Ciudad de Buenos Aires, Argentina<br>
Tel. +54 (11) 4342-2976/84<br><a href="mailto:alexmantaut@suremptec.com.ar" target="_blank">alexmantaut@suremptec.com.ar</a><br><a href="http://www.suremptec.com/" target="_blank">www.suremptec.com</a><br>