Changes between Version 6 and Version 7 of rfc33_gtiff_pixelispoint


Ignore:
Timestamp:
Nov 16, 2010, 6:54:26 AM (13 years ago)
Author:
warmerdam
Comment:

fix some typos.

Legend:

Unmodified
Added
Removed
Modified
  • rfc33_gtiff_pixelispoint

    v6 v7  
    2121Interpretation of the raster space from the GeoTIFF tie points will be offset by half a pixel in the !PixelIsPoint case in gdal/frmts/gtiff/geotiff.cpp.  This will impact the formation of the geotransform and the formation of GCPs when there are multiple tie points.  geotransmatrix conversion to geotransform will also be affected.
    2222
    23 Conversely if writing files with !PixelIsPoint (as driven by the "AREA_OR_PIXEL" metadata item being set to "POINT") the written raster space coordinates would be offset by half a pixel.
     23Conversely if writing files with !PixelIsPoint (as driven by the "AREA_OR_POINT" metadata item being set to "POINT") the written raster space coordinates would be offset by half a pixel.
    2424
    2525In trunk the above behavior may be disabled by setting the GTIFF_POINT_GEO_IGNORE configuration option to TRUE (it will default to FALSE). 
     
    3535== Reporting Extents ==
    3636
    37 Folks have at various points in the past requested that we report the extents differently for files with an AREA_OR_PIXEL value of PIXEL, must as listgeo does for GeoTIFF files that have a !PixelIsPoint interpretation.  I do *not* plan to do this, and for the purpose of GDAL the GCPs, RPCs and !GeoTransform will always be based on an area interpretation of pixels.  The AREA_OR_PIXEL will *only* be used to control setting of the !PixelIsPoint value in GeoTIFF files, and as metadata about the physical interpretation of pixels.
     37Folks have at various points in the past requested that we report the extents differently for files with an AREA_OR_POINT value of POINT, much as listgeo does for GeoTIFF files that have a !PixelIsPoint interpretation.  I do *not* plan to do this, and for the purpose of GDAL the GCPs, RPCs and !GeoTransform will always be based on an area interpretation of pixels.  The AREA_OR_POINT will *only* be used to control setting of the !PixelIsPoint value in GeoTIFF files, and as metadata about the physical interpretation of pixels.
    3838
    3939== World Files ==