Even,
Thank you very much, I'll test that out. As much as I like the idea of the
authority codes, I've seen enough examples where software has an incorrect
lookup of what the parameters are for a code or simply doesn't know the
code. It would be nice if they all leveraged Proj, but they don't. Even
Kirk,
Yes if there's an EPSG code for the CRS, GDAL avoids going through
defining all the parameters. That limits the risk of self-contradicting
definitions, and readers being confused by what is authoritative.
The following (untested (TM)) patch should accomplish what you want:
diff --git a
Javier,
I believe that example doesn't have all the parameters. Using 'listgeo'
(easier to see what the tags are), I see this for the Geotiff information
if I use the EPSG code to set the SRS:
Geotiff_Information:
Version: 1
Key_Revision: 1.0
Tagged_Information:
End_Of_Tags.
Keyed
GeoTIFF does not store any WKT inside. GDAL is converting the definition of
the CRS into the proper GeoTIFF tags.
With "tiffinfo" you can see them, for instance:
TIFF Directory at offset 0x8 (8)
Image Width: 306 Image Length: 175
Bits/Sample: 32
Sample Format: IEEE floating point
Compressi
Is there a way to tell GDAL to list the full set of projection parameters
in a GeoTiff? As much as I like the idea that you should just need the EPSG
code, I've run across too many software packages that either don't know the
code or have an incorrect interpretation of the code. I've tried supplyin
