Re: [gdal-dev] hdf5image metadata problems
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.org/gdal/ticket/4121#comment:4 Regards 2011/6/21 Alex Mantaut alexmant...@suremptec.com.ar: 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 antonio.valent...@tiscali.it 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 ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 alexmant...@suremptec.com.ar www.suremptec.com -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 alexmant...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 antonio.valent...@tiscali.it 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 ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 alexmant...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 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? The line suggested in the ticket: ReadGlobalAttributes( TRUE ); 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... 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... regards 2011/6/15 Antonio Valentino antonio.valent...@tiscali.it 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 groups, but it doesn't open the metadata asociated to the specified element (bug?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, The current behavior looks fine to me. If one opens a specific subdataset then only one HDF5 dataset object can be accessed and it is mapped on GDAL raster bans n. 1. All other HDF5 dataset object in the h5 file are ignored by the HDF5ImageDataset so there is no reason IMHO to make their metadata available in some manner. Metadata associated to all HDF5 groups (including the root one) are available in any case and accessible via GDAL dataset metadata. my two cents -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 alexmant...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
Hi Alex, Il giorno Thu, 16 Jun 2011 10:05:42 -0300 Alex Mantaut alexmant...@suremptec.com.ar 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 sure untill you confirmated... 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? The line suggested in the ticket: ReadGlobalAttributes( TRUE ); 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... 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... regards Well, IMHO it is not convoluted. Associating HDF5 dataset metadata tho the GDAL raster band just reflects the original HDF5 structure. Even if HDF5 and GDAL data model are quite different we can assume, IMHO, the following correspondence: HDF5 file-- GDAL dataset (HDF5Dataset class) HDF5 Group -- None (metadata are associated to GDAL dataset) HDF5 Dataset -- GDAL Raster Band HDF5 file can contain several datasets (with arbitrary shape) so the GDAL subdataset mechanism is used to tell to the HDF5ImageDataset class which is the HDF5 dataset the have to be mapped onto the GDAL raster band. I hope this is not too much confusing, with my poor english I'm not able to explain it better :). regards 2011/6/15 Antonio Valentino antonio.valent...@tiscali.it 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 groups, but it doesn't open the metadata asociated to the specified element (bug?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, The current behavior looks fine to me. If one opens a specific subdataset then only one HDF5 dataset object can be accessed and it is mapped on GDAL raster bans n. 1. All other HDF5 dataset object in the h5 file are ignored by the HDF5ImageDataset so there is no reason IMHO to make their metadata available in some manner. Metadata associated to all HDF5 groups (including the root one) are available in any case and accessible via GDAL dataset metadata. my two cents -- Antonio Valentino -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 GetMetadata() returns the metadata asociated to the all the subdatasets without need to explicitally ask for the raster band, but in hdf5imagedataset you have to explicitally ask for the raster band in order to get the metadata... IMHO the interface should be the same in both cases, in that case hdf5imagedataset should retrieve the metadata asociated to the subdataset directly via GetMetadata()... regards PS: Your english is fine, i hope you can understand my lousy english... If you can't explain something in english you can also write in italian to my mail, the we can send a translated message with the conclusions to the list 2011/6/16 Antonio Valentino antonio.valent...@tiscali.it Hi Alex, Il giorno Thu, 16 Jun 2011 10:05:42 -0300 Alex Mantaut alexmant...@suremptec.com.ar 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 sure untill you confirmated... 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? The line suggested in the ticket: ReadGlobalAttributes( TRUE ); 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... 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... regards Well, IMHO it is not convoluted. Associating HDF5 dataset metadata tho the GDAL raster band just reflects the original HDF5 structure. Even if HDF5 and GDAL data model are quite different we can assume, IMHO, the following correspondence: HDF5 file-- GDAL dataset (HDF5Dataset class) HDF5 Group -- None (metadata are associated to GDAL dataset) HDF5 Dataset -- GDAL Raster Band HDF5 file can contain several datasets (with arbitrary shape) so the GDAL subdataset mechanism is used to tell to the HDF5ImageDataset class which is the HDF5 dataset the have to be mapped onto the GDAL raster band. I hope this is not too much confusing, with my poor english I'm not able to explain it better :). regards 2011/6/15 Antonio Valentino antonio.valent...@tiscali.it 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 groups, but it doesn't open the metadata asociated to the specified element (bug?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, The current behavior looks fine to me. If one opens a specific subdataset then only one HDF5 dataset object can be accessed and it is mapped on GDAL raster bans n. 1. All other HDF5 dataset object in the h5 file are ignored by the HDF5ImageDataset so there is no reason IMHO to make their metadata available in some manner. Metadata associated to all HDF5 groups (including the root one) are available in any case and accessible via GDAL dataset metadata. my two cents -- Antonio Valentino -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 alexmant...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
Hi Alex, Il giorno Thu, 16 Jun 2011 11:51:48 -0300 Alex Mantaut alexmant...@suremptec.com.ar 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 the interface to get metadata from hdf5dataset and hdf5imagedataset... In hdf5dataset GetMetadata() returns the metadata asociated to the all the subdatasets without need to explicitally ask for the raster band, but in hdf5imagedataset you have to explicitally ask for the raster band in order to get the metadata... IMHO the interface should be the same in both cases, in that case hdf5imagedataset should retrieve the metadata asociated to the subdataset directly via GetMetadata()... Umh, I don't know. I've always considered HDF5Dataset and HDF5ImageDataset as quite different things: the index and the chapters. But I have to admit that yours is a good point. 2011/6/16 Antonio Valentino antonio.valent...@tiscali.it Hi Alex, Il giorno Thu, 16 Jun 2011 10:05:42 -0300 Alex Mantaut alexmant...@suremptec.com.ar 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 sure untill you confirmated... 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? The line suggested in the ticket: ReadGlobalAttributes( TRUE ); 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... 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... regards Well, IMHO it is not convoluted. Associating HDF5 dataset metadata tho the GDAL raster band just reflects the original HDF5 structure. Even if HDF5 and GDAL data model are quite different we can assume, IMHO, the following correspondence: HDF5 file-- GDAL dataset (HDF5Dataset class) HDF5 Group -- None (metadata are associated to GDAL dataset) HDF5 Dataset -- GDAL Raster Band HDF5 file can contain several datasets (with arbitrary shape) so the GDAL subdataset mechanism is used to tell to the HDF5ImageDataset class which is the HDF5 dataset the have to be mapped onto the GDAL raster band. I hope this is not too much confusing, with my poor english I'm not able to explain it better :). regards 2011/6/15 Antonio Valentino antonio.valent...@tiscali.it 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 groups, but it doesn't open the metadata asociated to the specified element (bug?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, The current behavior looks fine to me. If one opens a specific subdataset then only one HDF5 dataset object can be accessed and it is mapped on GDAL raster bans n. 1. All other HDF5 dataset object in the h5 file are ignored by the HDF5ImageDataset so there is no reason IMHO to make their metadata available in some manner. Metadata associated to all HDF5 groups (including the root one) are available in any case and accessible via GDAL dataset metadata. my two cents -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 antonio.valent...@tiscali.it Hi Alex, Il giorno Thu, 16 Jun 2011 11:51:48 -0300 Alex Mantaut alexmant...@suremptec.com.ar 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 the interface to get metadata from hdf5dataset and hdf5imagedataset... In hdf5dataset GetMetadata() returns the metadata asociated to the all the subdatasets without need to explicitally ask for the raster band, but in hdf5imagedataset you have to explicitally ask for the raster band in order to get the metadata... IMHO the interface should be the same in both cases, in that case hdf5imagedataset should retrieve the metadata asociated to the subdataset directly via GetMetadata()... Umh, I don't know. I've always considered HDF5Dataset and HDF5ImageDataset as quite different things: the index and the chapters. But I have to admit that yours is a good point. 2011/6/16 Antonio Valentino antonio.valent...@tiscali.it Hi Alex, Il giorno Thu, 16 Jun 2011 10:05:42 -0300 Alex Mantaut alexmant...@suremptec.com.ar 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 sure untill you confirmated... 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? The line suggested in the ticket: ReadGlobalAttributes( TRUE ); 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... 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... regards Well, IMHO it is not convoluted. Associating HDF5 dataset metadata tho the GDAL raster band just reflects the original HDF5 structure. Even if HDF5 and GDAL data model are quite different we can assume, IMHO, the following correspondence: HDF5 file-- GDAL dataset (HDF5Dataset class) HDF5 Group -- None (metadata are associated to GDAL dataset) HDF5 Dataset -- GDAL Raster Band HDF5 file can contain several datasets (with arbitrary shape) so the GDAL subdataset mechanism is used to tell to the HDF5ImageDataset class which is the HDF5 dataset the have to be mapped onto the GDAL raster band. I hope this is not too much confusing, with my poor english I'm not able to explain it better :). regards 2011/6/15 Antonio Valentino antonio.valent...@tiscali.it 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 groups, but it doesn't open the metadata asociated to the specified element (bug?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, The current behavior looks fine to me. If one opens a specific subdataset then only one HDF5 dataset object can be accessed and it is mapped on GDAL raster bans n. 1. All other HDF5 dataset object in the h5 file are ignored by the HDF5ImageDataset so there is no reason IMHO to make their metadata available in some manner. Metadata associated to all HDF5 groups (including the root one) are available in any case and accessible via GDAL dataset metadata. my two cents -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org
Re: [gdal-dev] hdf5image metadata problems
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 the file by specifying the subdataset name to GDALOpen() and then ask for the metadata it returns the metadata asociated to all groups but none of the subdatasets... I looked a bit into the hdf5dataset code and realized that this difference emerges from the fact that when GDAL opens the file specifying only the filename it uses hdf5dataset to open the file, but when I specify the subdataset to GDALOpen() it uses hdf5imagedataset instead, and it loads the metadata in a different way. I'm not sure of what the expected behavior is on hdf5image for loading metadata... It should load all the metadata of the file? Just the metadata asociated to the subdataset? Or should the application ask for the subdataset in some other way and then ask for the metadata? Alex, I'm not sure of the details of the metadata handling, but to the extent possible I think opening a subdataset should return metadata specific to that subdataset and any root metadata that applies to everything in the .hdf file. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 warmer...@pobox.com 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 the file by specifying the subdataset name to GDALOpen() and then ask for the metadata it returns the metadata asociated to all groups but none of the subdatasets... I looked a bit into the hdf5dataset code and realized that this difference emerges from the fact that when GDAL opens the file specifying only the filename it uses hdf5dataset to open the file, but when I specify the subdataset to GDALOpen() it uses hdf5imagedataset instead, and it loads the metadata in a different way. I'm not sure of what the expected behavior is on hdf5image for loading metadata... It should load all the metadata of the file? Just the metadata asociated to the subdataset? Or should the application ask for the subdataset in some other way and then ask for the metadata? Alex, I'm not sure of the details of the metadata handling, but to the extent possible I think opening a subdataset should return metadata specific to that subdataset and any root metadata that applies to everything in the .hdf file. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 javierur...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 warmer...@pobox.com 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?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, -- ---+-- I set the clouds in motion - turn up | Frank Warmerdam, warmer...@pobox.com light and sound - activate the windows | http://pobox.com/~warmerdam and watch the world go round - Rush| Geospatial Programmer for Rent ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev -- -- Alex Mantaut SUR Emprendimientos Tecnológicos Perú 345 Piso 5to Oficina B (C1067AAG) Ciudad de Buenos Aires, Argentina Tel. +54 (11) 4342-2976/84 alexmant...@suremptec.com.ar www.suremptec.com ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
Re: [gdal-dev] hdf5image metadata problems
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 groups, but it doesn't open the metadata asociated to the specified element (bug?) Alex, It sounds like a defect to me, yes. I would suggest filing a ticket that carefully documents the problem with a supporting example file. Best regards, The current behavior looks fine to me. If one opens a specific subdataset then only one HDF5 dataset object can be accessed and it is mapped on GDAL raster bans n. 1. All other HDF5 dataset object in the h5 file are ignored by the HDF5ImageDataset so there is no reason IMHO to make their metadata available in some manner. Metadata associated to all HDF5 groups (including the root one) are available in any case and accessible via GDAL dataset metadata. my two cents -- Antonio Valentino ___ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
