Q: How is GeoTIFF supported?

A: GeoTIFF is a complex format, and we are always amazed with the ways different software vendors pack .tiff files.

QuakeMap opens GeoTIFF files with a little help from "listgeo" program - which is part of FWTools distribution. To troubleshoot problems, you may want to install complete latest FWTools package, or just use binaries from "C:\Program Files\VitalBytes\QuakeMap\FWTools". Another useful package is LibTiff, which has installable Win32 binaries here. Use "tiffinfo" command to print tags directly.

To be sure that you are not dealing with a problem that has been already fixed, please download the latest QuakeMap Beta here. The Beta is updated often and contains the latest bug fixes.

Run listgeo in the command line; a healthy readable file would produce something like:

C:\ProjectsData\_GeoTiff\ca>listgeo -d o41121a1.tif
Geotiff_Information:
   Version: 1
   Key_Revision: 1.0
   Tagged_Information:
      ModelTiepointTag (2,3):
         0                0                0
         -94792.8635      345921.978       0
      ModelPixelScaleTag (1,3):
         1.52842474       1.52842474       0
      End_Of_Tags.
   Keyed_Information:
      GTModelTypeGeoKey (Short,1): ModelTypeProjected
      GTRasterTypeGeoKey (Short,1): RasterPixelIsPoint
      GTCitationGeoKey (Ascii,218): "IMAGINE GeoTIFF Support\nCopyright 199
001 by ERDAS, Inc. All Rights Reserved\n@(#)$RCSfile: egtf.c $ $Revision: 1
4 $ $Date: 2002/01/24 16:43:13Z $\nProjection Name = Custom\nUnits = meters
TIFF Units = meters"
      GeographicTypeGeoKey (Short,1): GCS_NAD83
      ProjectedCSTypeGeoKey (Short,1): User-Defined
      PCSCitationGeoKey (Ascii,194): "IMAGINE GeoTIFF Support\nCopyright 19
2001 by ERDAS, Inc. All Rights Reserved\n@(#)$RCSfile: egtf.c $ $Revision:
.4 $ $Date: 2002/01/24 16:43:13Z $\nProjection = Albers Conical Equal Area"
      ProjectionGeoKey (Short,1): User-Defined
      ProjCoordTransGeoKey (Short,1): CT_AlbersEqualArea
      ProjLinearUnitsGeoKey (Short,1): Linear_Meter
      ProjStdParallel1GeoKey (Double,1): 34
      ProjStdParallel2GeoKey (Double,1): 40.5
      ProjNatOriginLatGeoKey (Double,1): 0
      ProjFalseEastingGeoKey (Double,1): 0
      ProjFalseNorthingGeoKey (Double,1): -4000000
      ProjCenterLongGeoKey (Double,1): -120
      End_Of_Keys.
   End_Of_Geotiff.
 
Projection Method: CT_AlbersEqualArea
   ProjStdParallel1GeoKey: 34.000000 ( 34d 0' 0.00"N)
   ProjStdParallel2GeoKey: 40.500000 ( 40d30' 0.00"N)
   ProjNatOriginLatGeoKey: 0.000000 (  0d 0' 0.00"N)
   ProjNatOriginLongGeoKey: -120.000000 (120d 0' 0.00"W)
   ProjFalseEastingGeoKey: 0.000000 m
   ProjFalseNorthingGeoKey: -4000000.000000 m
GCS: 4269/NAD83
Datum: 6269/North American Datum 1983
Ellipsoid: 7019/GRS 1980 (6378137.00,6356752.31)
Prime Meridian: 8901/Greenwich (0.000000/  0d 0' 0.00"E)
Projection Linear Units: 9001/metre (1.000000m)
 
Corner Coordinates:
Upper Left    (  -94792.864,  345921.978)  (-121.1280281W,  41.1248543N)         <- two sets of parenthesis here!
Lower Left    (  -94792.864,  331932.306)  (-121.1260509W,  40.9988127N)
Upper Right   (  -84124.459,  345921.978)  (-121.0010849W,  41.1259337N)
Lower Right   (  -84124.459,  331932.306)  (-120.9993302W,  40.9998900N)
Center        (  -89458.661,  338927.142)  (-121.0636232W,  41.0623867N)
 

• Files that produce listgeo output without decimal long/lat in the second pair of parenthesis for corners. It looks like listgeo just doesn't produce the coordinates if something in the tags is missing.
• Files that rely on ModelTransformationTag. We will probably start interpreting that tag at a certain point; for now QuakeMap just displays a warning (and the corners will likely to be misplaced grossly).
• Files that are packed with non-Intel byte ordering. The bottom line is that if you double-click on the file in Windows, and it does not show up nicely in standard Image Viewer, you are dealing with bad image formatting.

If you are dealing with one of the issues listed above, please try to convert your files to something readable. In any case, PLEASE report the problem to slg@quakemap.com. Please allow us access to the offending file (if more than 1MB in size, DO NOT attach to email - use web or ftp host instead!)

In your e-mail please specify processor speed, RAM, OS and Internet connection type (example: 2.4GHz, 256Mb, Windows XP, cable). The program keeps a log of all activity in C:\Program Files\VitalBytes\QuakeMap\bin\trace.txt - please attach this file too.