[Xastir] USGS DRG maps again

[J. Lance Cotton]

Curt Mills, WE7U wrote:

> On Tue, 6 May 2003, J. Lance Cotton wrote:
> 
> 
>>I recompiled libproj, libtiff, and libgeotiff in that order. No change.
> And re-comfigured I assume?  Particularly libgeotiff...

Yeah, deleted the source dirs, re-extracted the tarballs, 
reconfigure/recompile/reinstall.

>>Setting Xastir's debug level to 512 and deleting the index file causes the
>>following output (sample):
>>
>>/usr/local/xastir/maps/filled/usgs_drg/o30096d3.fgd
>>West Bounding:  -96.375000
>>East Bounding:  -96.250000
>>North Bounding: 30.500000
>>South Bounding: 30.375000
>>30.375000 30.500000 -96.375000 -96.250000
>>
>>This indicates that the fgd file is being read properly. Why isn't the map
>>index getting the right numbers? Is this in either the projection
>>translation? The xastir-coordinates translation?
> 
> 
> Yea, it looks like the .FGD file is getting read properly, but
> perhaps the geoTIFF tags in the map file itself are not correct.

According to the 'listgeo' program that is included with the libgeotiff 
package, a sample of my geotiff map is like:

jlc7944 at www:~/src/libgeotiff-1.1.4/bin> ./listgeo 
/usr/local/xastir/maps/filled/usgs_drg/o30096d3.tif
Geotiff_Information:
    Version: 1
    Key_Revision: 0.2
    Tagged_Information:
       ModelTiepointTag (2,3):
          0                0                0
          751164.128       3378008.64       0
       ModelPixelScaleTag (1,3):
          2.4384           2.4384           0
       End_Of_Tags.
    Keyed_Information:
       GTModelTypeGeoKey (Short,1): ModelTypeProjected
       GTRasterTypeGeoKey (Short,1): RasterPixelIsArea
       ProjectedCSTypeGeoKey (Short,1): PCS_NAD27_UTM_zone_14N
       PCSCitationGeoKey (Ascii,25): "UTM Zone 14 N with NAD27"
       End_Of_Keys.
    End_Of_Geotiff.

PCS = 26714 (NAD27 / UTM zone 14N)
Projection = 16014 (UTM zone 14N)
Projection Method: CT_TransverseMercator
    ProjNatOriginLatGeoKey: 0.000000 (  0d-2147483648' 0.00"N)
    ProjNatOriginLongGeoKey: 0.000000 (  0d 0' 0.00"E)
    ProjScaleAtNatOriginGeoKey: 597859448.000000
    ProjFalseEastingGeoKey: 0.000000 m
    ProjFalseNorthingGeoKey: 0.000000 m
GCS: 4267/NAD27
Datum: 6267/North American Datum 1927
Ellipsoid: 7008/Clarke 1866 (nan,-214748365.00)
Prime Meridian: 8901/Greenwich (0.000000/  0d 0' 0.00"E)
Projection Linear Units: 9001/metre (1.000000m)

Corner Coordinates:
Upper Left    ( 751164.128,3378008.642)
Lower Left    ( 751164.128,3361386.070)
Upper Right   ( 765084.954,3378008.642)
Lower Right   ( 765084.954,3361386.070)
Center        ( 758124.541,3369697.356)

Those coordinates look like UTM things. Am I right? I don't know for sure.

> Are all of your geoTIFF maps messed up, including ones that used to
> work, or is it just newer maps that don't work right?

All of my geoTIFF maps are like this, all of them have worked in that past. 
Since you say geoTIFFs work fine on your system, this yet may be unique to me.

-Lance

-- 
J. Lance Cotton, KJ5O
http://map.findu.com/kj5o-14
joe at lightningflash.net