GDAL reports incorrect longitude coordinates in HDF5 files as GCPs

[jwderos]

In the HDF5 driver, GDAL just adds +180.0 to the longitude when reporting GCPs. This is causing some of our ASTER HDF files to have incorrect coordinates.

[jwderos]

I have example files if anyone wants them, but they are too large to upload.

[warmerdam]

Can you provide a pointer to where I could grab one?

I'm concerned about "interrupting" the GCPs for applications that are doing simple planar computations with them, so I'm 100% confident your solution is appropriate. I'd like to better understand the "incorrect coordinates" you are fixing.

[jwderos]

Here are three of them: ​https://hdds.usgs.gov/hdds2/pub/data/disaster/200908_Hurricane_Test/data/SATELLITE/NON_INGESTED/NAALSED

If you run: gdalinfo HDF5:"naalsed.v003.summer.38.-080.0001.h5":ASTER_GDEM/ASTGDEM

GCPs will report values like:

GCP[2999]: Id=, Info=

(957.5,990.5) -> (100.957954406738,37.0090103149414,0)

The "-080" in the filename is actually a longitude indicator. These are unusual files for me. All of our other HDF files are ASTER which seem to report UTM coordinates in meters.

[Even Rouault]

This ticket has been automatically closed because Trac is no longer used for GDAL bug tracking, since the project has migrated to GitHub. If you believe this ticket is still valid, you may file it to ​https://github.com/OSGeo/gdal/issues if it is not already reported there.