Re: ENVI File Question [message #55920 is a reply to message #55796] |
Thu, 13 September 2007 09:57   |
Paul.Bowyer@gmail.com
Messages: 7 Registered: September 2007
|
Junior Member |
|
|
On Sep 13, 5:15 pm, David Fanning <da...@dfanning.com> wrote:
> David Fanning writes:
>> Sorry for all the ENVI questions, but the documentation is
>> wonderful in that it leaves so much for the imagination to
>> fill out. :-)
>
> Oh, forget it. I'm not asking anymore ENVI questions.
>
> (Well, that's not true, since asking the questions reveals
> the answer--usually something dumb I've done--in the shortest
> amount of time. But it would serve my purpose just as much
> to send these questions to alt.sex.fetish instead of bothering
> you good people.)
>
> Cheers,
>
> David
> --
> David Fanning, Ph.D.
> Fanning Software Consulting, Inc.
> Coyote's Guide to IDL Programming:http://www.dfanning.com/
Hi David,
Couple of suggestions. Do you hard code the header filename into your
program?
1.You list the header file as
ENVI Header Filename: /home/fanning/b2.img.hdr
*Normally*, envi_write_envi_file, will create a header file which has
the same stem filename as the .img file, but substitutes the .img
extension for .hdr, so that your header file would be b2.hdr not
b2.img.hdr. Perhaps this is enough to confuse ENVI, and result in you
not seeing the map info displayed, because it is looking for a file it
can't find.
2. The difference between ENVI_SELECT and ENVI_PICKFILE, not updating
the available bands list, I can't explain exactly, but just for info,
there is a /NO_OPEN keyword that may be set in ENVI_WRITE_ENVI_FILE,
so I would guess that this was why you get the different results, one
uses it the other doesn't?
3. Do you really need to be writing ENVI images, ENVI can perfectly
well handle GeoTIFFs?
|
|
|