[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20041215: that pesky seam when combining images with IMGREMAP

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: 20041215: that pesky seam when combining images with IMGREMAP
  • Date: Thu, 16 Dec 2004 17:08:32 -0700
>From: "Owen Cooper" <address@hidden>
>Organization: NOAA
>Keywords: 200412151752.iBFHqalI029160 McIDAS IMGREMAP MERC MERGE

Hi Owen,

>I'm using IMGREMAP to combine GOES-WEST, GOES-EAST and METEOSAT images so
>that I get a panorama from California to Poland.

OK.  I looked at your email yesterday, and thought that your problem
might be related to the size of your GOES West 960x668 sector, but
that turns out to not be the case.

>But I get a seam of missing data (one pixel wide) where the images meet.
>The code I am using is listed below. 

>IMGREMAP ICARTT04/GW_IR MYDATA/IMAGES.135 DAY=%1 TIME=%4:%5 SMOOTH=YES 
>PRO=MERC 43 LATLON=43 50 SIZE=960 3568 RES=5

>IMGCOPY MYDATA/IMAGES.135 MYDATA/IMAGES.136 SIZE=960 668;

>IMGREMAP ICARTT04/GE_IR MYDATA/IMAGES.137 DAY=%1 TIME=%4:%6  SMOOTH=YES 
>PRO=MERC 43 LATLON=43 50 SIZE=960 3568 RES=5

>IMGREMAP MYDATA/IMAGES.136 MYDATA/IMAGES.137 SMOOTH=NO MERGE=YES PRO=DEST

>IMGCOPY  MYDATA/IMAGES.137 MYDATA/IMAGES.138 SIZE=960 2004;

>IMGDEL   MYDATA/IMAGES.135 136

>IMGREMAP ICARTT04/M7_IR MYDATA/IMAGES.135  DAY=%1 TIME=%4:%5  SMOOTH=YES 
>PRO=MERC 43 LATLON=43 50 SIZE=960 3568 RES=5

>IMGREMAP MYDATA/IMAGES.138 MYDATA/IMAGES.135 SMOOTH=NO MERGE=YES PRO=DEST

>SF 3; ERASE F;IMGDISP MYDATA/IMAGES.135 MAG=-2 -3 SU=IR_OC EU=IR_TEST ;  MAP

>I have attached a sample image showing the seams.
>Do you have any thoughts on how I can eliminate the seams?

I used your code modified to use the RTIMAGES dataset for input, left
off the Meteosat portion, and get the same results as you.  I have
played around with the west sector size and even the RES= value, all to
no avail.

I am led to believe that this is a bug since remapping into an
non-conical projection (like METEOSAT rotated so the center point is
over the center of the US) creates a composite that does not have the
missing pixel.

I will search the SSEC inquiry system to see if others have seen the
same problem.  If they have not, or if they have and there is no
resolution, I will submit an inquiry.

Sorry for the problems...

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.