Skip to content

Commit 05a70ea

Browse files
committed
Doc: gtiff.rst: document GTIFF_READ_ANGULAR_PARAMS_IN_DEGREE / GTIFF_WRITE_ANGULAR_PARAMS_IN_DEGREE
1 parent f31d5fa commit 05a70ea

File tree

1 file changed

+28
-0
lines changed

1 file changed

+28
-0
lines changed

doc/source/drivers/raster/gtiff.rst

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1124,6 +1124,34 @@ the default behavior of the GTiff driver.
11241124
expected to be necessary, unless GDAL is incorrectly determining the disk
11251125
space available on the destination file system.
11261126

1127+
- .. config:: GTIFF_READ_ANGULAR_PARAMS_IN_DEGREE
1128+
:choices: YES, NO
1129+
:default: NO
1130+
:since: 3.9.1
1131+
1132+
Conformant GeoTIFF files should have the values of angular projection
1133+
parameters written in the unit of the GeogAngularUnitsGeoKey. But some
1134+
non-conformant implementations, such as GDAL <= 3.9.0, always wrote them
1135+
in degrees.
1136+
This option can be set to YES when reading such non-conformant GeoTIFF
1137+
files (typically using grads), to instruct GDAL (>= 3.9.1) that the projection
1138+
parameters are in degrees, instead of being expressed in the unit of the
1139+
GeogAngularUnitsGeoKey.
1140+
1141+
- .. config:: GTIFF_WRITE_ANGULAR_PARAMS_IN_DEGREE
1142+
:choices: YES, NO
1143+
:default: NO
1144+
:since: 3.9.1
1145+
1146+
Conformant GeoTIFF files should have the values of angular projection
1147+
parameters written in the unit of the GeogAngularUnitsGeoKey. But some
1148+
non-conformant implementations, such as GDAL >= 3.0 and <= 3.9.0, assumed
1149+
those values to be in degree.
1150+
This option can be set to YES to force writing such non-conformant GeoTIFF
1151+
files. It should *not* be nominally used, except to workaround interoperability
1152+
issues.
1153+
1154+
11271155
Codec Recommendations
11281156
---------------------
11291157

0 commit comments

Comments
 (0)