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/frmts/gtiff/gt_wkt_srs.cpp b/frmts/gtiff/gt_wkt_srs.cpp
index 22eabfcd38..5a089142f8 100644
--- a/frmts/gtiff/gt_wkt_srs.cpp
+++ b/frmts/gtiff/gt_wkt_srs.cpp
@@ -2213,7 +2213,8 @@ int GTIFSetFromOGISDefnEx(GTIF *psGTIF,
OGRSpatialReferenceH hSRS,
GTIFKeySet(psGTIF, ProjectedCSTypeGeoKey, TYPE_SHORT, 1,
nPCS);
}
}
- else if (poSRSCompatibleOfWKT1->IsGeocentric())
+
+ if (poSRSCompatibleOfWKT1->IsGeocentric())
{
GTIFKeySet(psGTIF, GTModelTypeGeoKey, TYPE_SHORT, 1,
ModelTypeGeocentric);
Even
--
http://www.spatialys.com
My software is free, but my time generally not.
Butcher of all kinds of standards, open or closed formats. At the end, this is
just about bytes.
Mood of the day: "Bien entendu, on peut sauter sur sa chaise comme un cabri en
disant : les standards ! les standards ! les standards ! Mais ça n’aboutit à rien et ça
ne signifie rien." ~ dixit De Gaulle
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
