comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: ENVI's codes
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: ENVI's codes [message #68719] Sun, 22 November 2009 16:18 Go to next message
Jiek is currently offline  Jiek
Messages: 2
Registered: November 2009
Junior Member
On Nov 23, 5:35 am, Hassan <hkhav...@gmail.com> wrote:
> I used the following code to display the image:
> image=read_tiff(file)
> imagesize=[62,488,290]
> DEVICE, DECOMPOSED = 0
> LOADCT, 38
> WINDOW, 0, XSIZE = imageSize[1], YSIZE = imageSize[2]
> TV, Image(0,*,*), 0
>
> but there are two problems: first it's displayed upside-down and
> second the way it shows the image is quite different with other
> softwares like ENVI, it's more like the image is shown in 256-color
> table or something like that.

I found a function to read ENVI image and it work well.As follows:
pro read_envi_image, infile, img, xs, ys, type, offset, mapinfo

;
; Copyright (c) 2003,Institute of Photogrammetry and Remote Sensing, ;
(IPF),
; Technical University of Vienna. Unauthorised reproduction
prohibited.
;
;+
; NAME:
; read_envi_file
;
; PURPOSE:
; IDL program, which reads standard ENVI image files (*.img).
;
;
; CATEGORY:
; Input_Output
;
; CALLING SEQUENCE:
; read_envi_file, infile, img, xs, ys, type,offset
;
; INPUTS:
; infile - input file name
;
; OPTIONAL INPUTS:
; None
;
; KEYWORD PARAMETERS:
; None
;
; OUTPUTS:
; img - ENVI image file, 2D array
; xs - number of samples
; ys - number of lines
; type - image data type
; offset - headeroffset
; mapinfo - information on spatial resolution (spacing) and
coordinates
; of upper left corner (ulx, uly)
;
;
; OPTIONAL OUTPUTS:
; None
;
; COMMON BLOCKS:
; none
;
; SIDE EFFECTS:
;
; RESTRICTIONS:
; None
;
; PROCEDURE:
;
; EXAMPLE:
;
; REMARKS
; None
;
; MODIFICATION HISTORY:
; Written by: Carsten Pathe, cp@ipf.tuwien.ac.at
; Date: 25.08.2003
;
;-

image = infile

header = strsplit(infile,'.',/extract)
header = header(n_elements(header)-2)+'.hdr'

openr, unit, header, /get_lun

header_line = ''

while not eof(unit) do begin

readf, unit, header_line
tmp = strsplit(header_line(0), '=', /extract)
header_keyword = strsplit(tmp(0), ' ', /extract)

print, header_keyword

if header_keyword(0) eq 'samples' then xs = long(tmp(1))
if header_keyword(0) eq 'lines' then ys = long(tmp(1))
if header_keyword(0) eq 'header' then offset = long(tmp(1))
if header_keyword(0) eq 'data' then type = long(tmp(1))

if header_keyword(0) eq 'map' then begin

mapinfo_tmp=strsplit(tmp(1),'{',/extract)
mapinfo_tmp=strsplit(mapinfo_tmp(1),',',/extract)

mapinfo={ulx:0.,uly:0.,spacing:0.}
mapinfo.ulx=mapinfo_tmp(3)
mapinfo.uly=mapinfo_tmp(4)
mapinfo.spacing=mapinfo_tmp(5)

endif

endwhile

close,unit & free_lun, unit
print, xs, ys

if type eq 1 then img=bytarr(xs, ys)
if type eq 2 then img=intarr(xs, ys)
if type eq 4 then img=fltarr(xs, ys)
if type eq 12 then img=uintarr(xs, ys)

openr, unit,image, /get_lun
point_lun, unit, offset
readu, unit, img
close, unit & free_lun, unit

end
Re: ENVI's codes [message #68721 is a reply to message #68719] Sun, 22 November 2009 13:35 Go to previous messageGo to next message
Hassan is currently offline  Hassan
Messages: 48
Registered: October 2009
Member
I used the following code to display the image:
image=read_tiff(file)
imagesize=[62,488,290]
DEVICE, DECOMPOSED = 0
LOADCT, 38
WINDOW, 0, XSIZE = imageSize[1], YSIZE = imageSize[2]
TV, Image(0,*,*), 0

but there are two problems: first it's displayed upside-down and
second the way it shows the image is quite different with other
softwares like ENVI, it's more like the image is shown in 256-color
table or something like that.
Re: ENVI's codes [message #68723 is a reply to message #68721] Sun, 22 November 2009 10:41 Go to previous messageGo to next message
Hassan is currently offline  Hassan
Messages: 48
Registered: October 2009
Member
I used the following code to read an ENVI file into IDL:


imagesize=[488,290,62]
refImage = READ_BINARY(file, DATA_DIMS = imageSize)
DEVICE, DECOMPOSED = 0
LOADCT, 38
WINDOW, 0, XSIZE = imageSize[0], YSIZE = imageSize[1]
TV, refImage, 0

but the resulting display was strange. I don't know how to put an
image here since it's easier to explain. anyway, the resulting display
seems to show a superimposed of the features. for example if in the
original image there are 2 features which are a bit far from each
other but when I want to display it in the IDL those two features are
overlaid.
Re: ENVI's codes [message #68724 is a reply to message #68723] Sat, 21 November 2009 15:26 Go to previous messageGo to next message
rogass is currently offline  rogass
Messages: 200
Registered: April 2008
Senior Member
On 22 Nov., 00:23, Michael Galloy <mgal...@gmail.com> wrote:
> Hassan wrote:
>> I wonder if we can have an access to source code of ENVI functions?
>> I need to export some images from ENVI to IDL, I can use the export-
>> varaible-to-idl function in ENVI but I want to know how I can do this
>> without using ENVI.
>
> No, ENVI is not open source.
>
> Do you just want to be able to read some ENVI files in IDL? That is
> fairly straight-forward; the data file is just a binary file which the
> associated header file describes.
>
> Mike
> --www.michaelgalloy.com
> Research Mathematician
> Tech-X Corporation

You can also try to export your envi-data as geotiff which can be
imported to idl by read_tiff with the geotiff flag. Give it a try. If
this won't work for you, just think about what Michael said...

Regards

CR
Re: ENVI's codes [message #68725 is a reply to message #68724] Sat, 21 November 2009 15:23 Go to previous messageGo to next message
Michael Galloy is currently offline  Michael Galloy
Messages: 1114
Registered: April 2006
Senior Member
Hassan wrote:
> I wonder if we can have an access to source code of ENVI functions?
> I need to export some images from ENVI to IDL, I can use the export-
> varaible-to-idl function in ENVI but I want to know how I can do this
> without using ENVI.

No, ENVI is not open source.

Do you just want to be able to read some ENVI files in IDL? That is
fairly straight-forward; the data file is just a binary file which the
associated header file describes.

Mike
--
www.michaelgalloy.com
Research Mathematician
Tech-X Corporation
Re: ENVI's codes [message #68843 is a reply to message #68719] Wed, 25 November 2009 03:55 Go to previous message
Hassan is currently offline  Hassan
Messages: 48
Registered: October 2009
Member
On Nov 23, 12:18 am, Jiek <676215...@qq.com> wrote:
> On Nov 23, 5:35 am, Hassan <hkhav...@gmail.com> wrote:
>
>> I used the following code to display the image:
>> image=read_tiff(file)
>> imagesize=[62,488,290]
>> DEVICE, DECOMPOSED = 0
>> LOADCT, 38
>> WINDOW, 0, XSIZE = imageSize[1], YSIZE = imageSize[2]
>> TV, Image(0,*,*), 0
>
>> but there are two problems: first it's displayed upside-down and
>> second the way it shows the image is quite different with other
>> softwares like ENVI, it's more like the image is shown in 256-color
>> table or something like that.
>
> I found a function to read ENVI image and it work well.As follows:
> pro read_envi_image, infile, img, xs, ys, type, offset, mapinfo
>
> ;
> ; Copyright (c) 2003,Institute of Photogrammetry and Remote Sensing, ;
> (IPF),
> ; Technical University of Vienna. Unauthorised reproduction
> prohibited.
> ;
> ;+
> ; NAME:
> ; read_envi_file
> ;
> ; PURPOSE:
> ; IDL program, which reads standard ENVI image files (*.img).
> ;
> ;
> ; CATEGORY:
> ; Input_Output
> ;
> ; CALLING SEQUENCE:
> ; read_envi_file, infile, img, xs, ys, type,offset
> ;
> ; INPUTS:
> ; infile - input file name
> ;
> ; OPTIONAL INPUTS:
> ; None
> ;
> ; KEYWORD PARAMETERS:
> ; None
> ;
> ; OUTPUTS:
> ; img - ENVI image file, 2D array
> ; xs - number of samples
> ; ys - number of lines
> ; type - image data type
> ; offset - headeroffset
> ; mapinfo - information on spatial resolution (spacing) and
> coordinates
> ; of upper left corner (ulx, uly)
> ;
> ;
> ; OPTIONAL OUTPUTS:
> ; None
> ;
> ; COMMON BLOCKS:
> ; none
> ;
> ; SIDE EFFECTS:
> ;
> ; RESTRICTIONS:
> ; None
> ;
> ; PROCEDURE:
> ;
> ; EXAMPLE:
> ;
> ; REMARKS
> ; None
> ;
> ; MODIFICATION HISTORY:
> ; Written by: Carsten Pathe, c...@ipf.tuwien.ac.at
> ; Date: 25.08.2003
> ;
> ;-
>
> image = infile
>
> header = strsplit(infile,'.',/extract)
> header = header(n_elements(header)-2)+'.hdr'
>
> openr, unit, header, /get_lun
>
> header_line = ''
>
> while not eof(unit) do begin
>
> readf, unit, header_line
> tmp = strsplit(header_line(0), '=', /extract)
> header_keyword = strsplit(tmp(0), ' ', /extract)
>
> print, header_keyword
>
> if header_keyword(0) eq 'samples' then xs = long(tmp(1))
> if header_keyword(0) eq 'lines' then ys = long(tmp(1))
> if header_keyword(0) eq 'header' then offset = long(tmp(1))
> if header_keyword(0) eq 'data' then type = long(tmp(1))
>
> if header_keyword(0) eq 'map' then begin
>
> mapinfo_tmp=strsplit(tmp(1),'{',/extract)
> mapinfo_tmp=strsplit(mapinfo_tmp(1),',',/extract)
>
> mapinfo={ulx:0.,uly:0.,spacing:0.}
> mapinfo.ulx=mapinfo_tmp(3)
> mapinfo.uly=mapinfo_tmp(4)
> mapinfo.spacing=mapinfo_tmp(5)
>
> endif
>
> endwhile
>
> close,unit & free_lun, unit
> print, xs, ys
>
> if type eq 1 then img=bytarr(xs, ys)
> if type eq 2 then img=intarr(xs, ys)
> if type eq 4 then img=fltarr(xs, ys)
> if type eq 12 then img=uintarr(xs, ys)
>
> openr, unit,image, /get_lun
> point_lun, unit, offset
> readu, unit, img
> close, unit & free_lun, unit
>
> end

it's really useful code, thanks for that. although after running the
code, it doesnt ask me for input file and it should be defined into
the code but it should be straightforward to do that.
Re: ENVI's codes [message #68860 is a reply to message #68723] Mon, 23 November 2009 07:20 Go to previous message
jeanh is currently offline  jeanh
Messages: 79
Registered: November 2009
Member
Hassan wrote:
> I used the following code to read an ENVI file into IDL:
>
> refImage = READ_BINARY(file, DATA_DIMS = imageSize)
>
> [...]anyway, the resulting display
> seems to show a superimposed of the features.

Hi,

this is a typical data type problem.
By default, read_binary reads byte data. If you have floats or else,
this superimposition would occur (though I always witness it the other
way around, when saving a float declared as byte in IDL and opening the
image in Envi). See the DATA_TYPE keywork for read_binary

Jean
Re: ENVI's codes [message #68864 is a reply to message #68719] Mon, 23 November 2009 05:20 Go to previous message
Hassan is currently offline  Hassan
Messages: 48
Registered: October 2009
Member
On Nov 23, 12:18 am, Jiek <676215...@qq.com> wrote:
> On Nov 23, 5:35 am, Hassan <hkhav...@gmail.com> wrote:
>
>> I used the following code to display the image:
>> image=read_tiff(file)
>> imagesize=[62,488,290]
>> DEVICE, DECOMPOSED = 0
>> LOADCT, 38
>> WINDOW, 0, XSIZE = imageSize[1], YSIZE = imageSize[2]
>> TV, Image(0,*,*), 0
>
>> but there are two problems: first it's displayed upside-down and
>> second the way it shows the image is quite different with other
>> softwares like ENVI, it's more like the image is shown in 256-color
>> table or something like that.
>
> I found a function to read ENVI image and it work well.As follows:
> pro read_envi_image, infile, img, xs, ys, type, offset, mapinfo
>
> ;
> ; Copyright (c) 2003,Institute of Photogrammetry and Remote Sensing, ;
> (IPF),
> ; Technical University of Vienna. Unauthorised reproduction
> prohibited.
> ;
> ;+
> ; NAME:
> ; read_envi_file
> ;
> ; PURPOSE:
> ; IDL program, which reads standard ENVI image files (*.img).
> ;
> ;
> ; CATEGORY:
> ; Input_Output
> ;
> ; CALLING SEQUENCE:
> ; read_envi_file, infile, img, xs, ys, type,offset
> ;
> ; INPUTS:
> ; infile - input file name
> ;
> ; OPTIONAL INPUTS:
> ; None
> ;
> ; KEYWORD PARAMETERS:
> ; None
> ;
> ; OUTPUTS:
> ; img - ENVI image file, 2D array
> ; xs - number of samples
> ; ys - number of lines
> ; type - image data type
> ; offset - headeroffset
> ; mapinfo - information on spatial resolution (spacing) and
> coordinates
> ; of upper left corner (ulx, uly)
> ;
> ;
> ; OPTIONAL OUTPUTS:
> ; None
> ;
> ; COMMON BLOCKS:
> ; none
> ;
> ; SIDE EFFECTS:
> ;
> ; RESTRICTIONS:
> ; None
> ;
> ; PROCEDURE:
> ;
> ; EXAMPLE:
> ;
> ; REMARKS
> ; None
> ;
> ; MODIFICATION HISTORY:
> ; Written by: Carsten Pathe, c...@ipf.tuwien.ac.at
> ; Date: 25.08.2003
> ;
> ;-
>
> image = infile
>
> header = strsplit(infile,'.',/extract)
> header = header(n_elements(header)-2)+'.hdr'
>
> openr, unit, header, /get_lun
>
> header_line = ''
>
> while not eof(unit) do begin
>
> readf, unit, header_line
> tmp = strsplit(header_line(0), '=', /extract)
> header_keyword = strsplit(tmp(0), ' ', /extract)
>
> print, header_keyword
>
> if header_keyword(0) eq 'samples' then xs = long(tmp(1))
> if header_keyword(0) eq 'lines' then ys = long(tmp(1))
> if header_keyword(0) eq 'header' then offset = long(tmp(1))
> if header_keyword(0) eq 'data' then type = long(tmp(1))
>
> if header_keyword(0) eq 'map' then begin
>
> mapinfo_tmp=strsplit(tmp(1),'{',/extract)
> mapinfo_tmp=strsplit(mapinfo_tmp(1),',',/extract)
>
> mapinfo={ulx:0.,uly:0.,spacing:0.}
> mapinfo.ulx=mapinfo_tmp(3)
> mapinfo.uly=mapinfo_tmp(4)
> mapinfo.spacing=mapinfo_tmp(5)
>
> endif
>
> endwhile
>
> close,unit & free_lun, unit
> print, xs, ys
>
> if type eq 1 then img=bytarr(xs, ys)
> if type eq 2 then img=intarr(xs, ys)
> if type eq 4 then img=fltarr(xs, ys)
> if type eq 12 then img=uintarr(xs, ys)
>
> openr, unit,image, /get_lun
> point_lun, unit, offset
> readu, unit, img
> close, unit & free_lun, unit
>
> end

I run it but it seems it imports just one band, right? is the output
variable named 'img'?
Re: ENVI's codes [message #68865 is a reply to message #68721] Mon, 23 November 2009 03:27 Go to previous message
Carsten Lechte is currently offline  Carsten Lechte
Messages: 124
Registered: August 2006
Senior Member
Hassan wrote:
> but there are two problems: first it's displayed upside-down and
> second the way it shows the image is quite different with other
> softwares like ENVI, it's more like the image is shown in 256-color
> table or something like that.

The first can be fixed by using the /ORDER keyword to TV.

The second is how TV is supposed to work. Maybe the tvscale procedure
from http://www.dfanning.com/documents/programs.html can help (I do not
use it myself).


chl
Re: ENVI's codes [message #68868 is a reply to message #68721] Sun, 22 November 2009 16:27 Go to previous message
jeffnettles4870 is currently offline  jeffnettles4870
Messages: 111
Registered: October 2006
Senior Member
On Nov 22, 4:35 pm, Hassan <hkhav...@gmail.com> wrote:
> I used the following code to display the image:
> image=read_tiff(file)
> imagesize=[62,488,290]
> DEVICE, DECOMPOSED = 0
> LOADCT, 38
> WINDOW, 0, XSIZE = imageSize[1], YSIZE = imageSize[2]
> TV, Image(0,*,*), 0
>
> but there are two problems: first it's displayed upside-down and
> second the way it shows the image is quite different with other
> softwares like ENVI, it's more like the image is shown in 256-color
> table or something like that.

The upside-down part I can help you with at least. With ENVI the
pixel origin is in the upper left corner of the image. With IDL the
origin is the lower left corner. So add a reverse and you should be
ok:

image = reverse(image,2)

put that aright after you call read_tiff.

As for how its displaying, i'm not sure i understand your description
of the problem, so i'll leave that to smarter folks than me :)
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Create smooth lines in IDL
Next Topic: Regression with NaN's

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 13:32:39 PDT 2025

Total time taken to generate the page: 0.00666 seconds