[gdal-dev] AREA_OR_POINT vs GDALMD_AREA_OR_POINT

[jluis at ualg.pt]

Hi,

I made GMT respect as far as possible the AREA_OR_POINT GeoTiff key  
for read/write, but ...

The following was silently ignored (GMT uses the MEM driver)

GDALSetMetadataItem(hDstDS, "AREA_OR_POINT", "Point", NULL);

so digging here and there I found about GDALMD_AREA_OR_POINT, and in  
fact this one is now taken into consideration

GDALSetMetadataItem(hDstDS, "GDALMD_AREA_OR_POINT", "Point", NULL);


However, this implies that on reading I have now to test for both

GDALGetMetadataItem(hDataset, "AREA_OR_POINT", NULL)

  ---- AND ----

GDALGetMetadataItem(hDataset, "GDALMD_AREA_OR_POINT", NULL)

This means that other codes that pay attention to the AREA vs POINT  
thing will have to do both tests as well and if they do only the first  
one, GeoTiffs created by GDAL will have the problem ignored, and quite  
likely an error in coordinates will follow.

So the question is, why this name duplication (AREA_OR_POINT vs  
GDALMD_AREA_OR_POINT) and why GDALSetMetadataItem() ignores the  
AREA_OR_POINT key?

Thanks
Joaquim

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.