Advanced
Offsets in Coordinate System Units
- Yes – The coordinate system offsets stored in the GeoTIFF file will be interpreted as being in the linear units of the projection; this is correct according to the GeoTIFF specification.
- No – The coordinate system offsets will be interpreted as being in meters; this is what is actually done in practice by many software packages.
ProjLinearUnitsInterpCorrectGeoKey flag), and the Prefer File Coordinate System Units parameter is set to Yes, this option is ignored. Write Projected Coordinate System as EPSG Code
The projected coordinate system in GeoTIFF may be stored either by specifying an EPSG code or by marking the coordinate system as user-defined.
Some software packages may have better compatibility with one of these methods over the other.
- Yes (default) – Write an EPSG code if possible.
- No – Mark the projection as user-defined.
Write Geographic Coordinate System as EPSG Code
The projected coordinate system in GeoTIFF may be stored either by specifying an EPSG code or by marking the coordinate system as user-defined.
Some software packages may have better compatibility with one of these methods over the other.
- Yes (default) – Write an EPSG code if possible.
- No – Mark the projection as user-defined.
Write Geographic Keys for Projected Coordinate Systems
Specifies whether GeoTIFF geographic coordinate system keys (for example, GeographicTypeGeoKey, GeogCitationGeoKey, etc.) should be written for projected coordinate systems.
The default is Yes, since it is not harmful to write these keys; however, some standards may require that these keys be omitted for projected coordinate systems.
Write Esri-Compatible Coordinate System
This option attempts to adjust some coordinate system geokeys to ensure better compatibility with Esri applications.
- Yes – Adjust coordinate system geokeys to improve compatibility with Esri products.
- No (default) – Write typical geokeys.
Ignore Raster Type Key
GeoTIFF contains a “raster type” key which specifies whether each pixel in the file represents an area (PixelIsArea) or a point (PixelIsPoint).
When reading PixelIsPoint data, by default, the raster extents is shifted up and left by half a pixel when transformed to the FME georeferencing model. Setting this value to Yes prevents this adjustment from happening.