[Xastir] USGS DRG maps again

[J. Lance Cotton]

Here's more info:

I recompiled libproj, libtiff, and libgeotiff in that order. No change.

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?

-Lance

On Tuesday 06 May 2003 09:51, Curt Mills, WE7U wrote:
> On Tue, 6 May 2003, J. Lance Cotton wrote:
> > Yeah, xv, display, gimp, gqview... Opens them fine (just takes a few
> > minutes). These are the same files, in the same directory as the last
> > time I had drg problems, though I've re-indexed the maps since then a few
> > times.
> >
> > I'm not sure what's happening. I compiled libgeotiff, libtiff, proj, in
> > the correct order, according to README.1ST. I shall try to compile them
> > again, as maybe I didn't do it right...
>
> Just to make sure that nothing broke, I deleted my map_index file
> and restarted Xastir, then displayed the various types of topo maps.
> They indexed just fine and displayed fine.
>
> I suspect it's some interaction (or non-interaction) between your
> libproj and libgeotiff libraries.

-- 
J. Lance Cotton, KJ5O
joe at lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the 
cookies.