| Re: BSQ to BIL [message #69576] |
Sat, 06 February 2010 13:00  |
Maxwell Peck
Messages: 61
Registered: February 2010
|
Member |
|
|
> a=isis_write, r_fid,filename + '_bil.cub'
Hi,
I'm not sure where ISIS_WRITE comes from (it's not an ENVI function as
far as i know), or what your actual error is, but it is unlikely it
will accept the r_fid keyword. You will probably need to use the
ENVI_GET_DATA function to put the band in an IDL variable and output
it from that. If there is a lot of data you may need to use tiling
(all in the ENVI Programmers guide).
Max
|
|
|
|
|
|
| Re: BSQ to BIL [message #69757 is a reply to message #69576] |
Mon, 08 February 2010 12:53  |
penteado
Messages: 866
Registered: February 2018
|
Senior Member
Administrator |
|
|
On Feb 6, 7:00 pm, Maxwell Peck <maxjp...@gmail.com> wrote:
>> a=isis_write, r_fid,filename + '_bil.cub'
>
> Hi,
>
> I'm not sure where ISIS_WRITE comes from (it's not an ENVI function as
> far as i know), or what your actual error is, but it is unlikely it
> will accept the r_fid keyword. You will probably need to use the
> ENVI_GET_DATA function to put the band in an IDL variable and output
> it from that. If there is a lot of data you may need to use tiling
> (all in the ENVI Programmers guide).
>
> Max
This is not directly related to the original question, but if anyone
is interested, I have a reader and writer for ISIS cubes. The main
reasons I wrote them are the awkward interface of the ISIS routines,
their lack of ability to do more complicated things than just reading
or writing core bands, and to not need to install ISIS just to read
and write cubes from IDL. However, my routines presently only support
BSQ.
|
|
|
|
| Re: BSQ to BIL [message #69764 is a reply to message #69576] |
Mon, 08 February 2010 08:01 |
jtmcahill
Messages: 26
Registered: October 2007
|
Junior Member |
|
|
On Feb 6, 4:00 pm, Maxwell Peck <maxjp...@gmail.com> wrote:
>> a=isis_write, r_fid,filename + '_bil.cub'
>
> Hi,
>
> I'm not sure where ISIS_WRITE comes from (it's not an ENVI function as
> far as i know), or what your actual error is, but it is unlikely it
> will accept the r_fid keyword. You will probably need to use the
> ENVI_GET_DATA function to put the band in an IDL variable and output
> it from that. If there is a lot of data you may need to use tiling
> (all in the ENVI Programmers guide).
>
> Max
David and Max,
I confess that I definitely got the syntax wrong with the Isis_write
command. By the way, "isis_write" is a command that the USGS provides
for making ".cub" files from IDL compatible with their mapping
software program (ISIS). They have several commands help accommodate
those of us that like aspects of both IDL and ISIS. In this
particular case, I'm looking to format this file for import into ISIS
but I've never had to do a BSQ to BIL conversion.
Anyway, I'm more concerned with converting the file to BIL format
first. I can worry about writing the .cub file later (which I've done
before I'm just a bit rusty, obviously). What I don't understand is
the above code (with the isis_write command commented out) makes a
file that ENVI says is a BIL when opened and provides a small header
file with basic information. How can verify that this is true. I'm
worried it may have only changed some info in the header to appease
me. I've tried verifying this by loading it into ISIS with a RAW2ISIS
procedure but it gives me a pretty messed up image so either it isn't
writing out the header info correctly for me to enter into ISIS or it
hasn't made the conversion at all. It looks beautiful in ENVI and
says it is a BIL but that is one step short of where I need to go.
Any thoughts?
Josh
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
