Hi Jukka, > My first vote as PSC member: > > +1
I didn't call yet for the formal vote, but thanks for your support. > > No doubt the feature will be useful and I trust that RFC is technically > sound. > > I wonder why the list of affected drivers does not include any of the > JPEG2000 drivers. Don't they need changes or is metadata handling in > JPEG2000 special in some way? I guess that the format itself (JPX) can store > metadata from whatever domains. The JPEG2000 drivers don't need to implement the new virtual method since they actively set their metadata with SetMetadata() (that goes to the oMDMD member of GDALMajorObject) instead of lazying loading them through a specialized GetMetadata()/GetMetadataItem(). A specialized implementation of the new virtual method is only needed in the case of lazy loading. In other cases such as the JPEG2000 driver the base implementation in GDALMajorObject::GetMetadataDomainList() will do the job. Regarding the JPEG2000 drivers, they can potentially expose the xml:XMP metadata domain. From the code, I see that JP2KAK can also expose GML metadata in xml:XXXX metadata domains (probably the GML geo-registration where XXXX="gml.root-instance", as well as other XML JP2 boxes where XXXX will be BOX_YYYY and YYYY a sequential number). Even _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
