[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20001127: imgremap vs aamap
- Subject: 20001127: imgremap vs aamap
- Date: Tue, 28 Nov 2000 09:30:35 -0700
- >date: Mon, 27 Nov 2000 22:26:38 +0000 (GMT)
- >from: "David J. Vollaro" <address@hidden>
- >keywords: 200011272229.eARMTUo07711 McIDAS-X IMGREMAP AAMAP
- >organization: UCAR/Unidata
- >to: address@hidden (mcidas users-forum)
Hi,
I have found some old remapped images that were created using AAMAP. I
was wondering what the difference between AAMAP and the newer IMGREMAP
command was. I am trying to add recently found images to this older
remapped database and can only use IMGREMAP now. I want to have the
old and new remapped images be consistant and I am trying to create an
IMGREMAP command that will duplicate the AAMAP.
EX. (AAMAP sarea darea frame proj clat clon res line ele BAND=)
AAMAP 2696 9696 1 MERC 17.3 78 8 400 880 BAND=4
I tried the following...
IMGREMAP MYDATA/IMAGES.2696 MYDATA/IMAGES.9696 BAND=4 LAT=17.3 78 PRO=MERC
RES=8 SIZ=400 880
However, these grids are not the same...(I checked by using PC C lat
lon and then used "D" to get info at that pixel.)
The original image has a sampling res of 4km in Y and 8km in X. I am
remapping the image to an 8kmx8km resolution. Should I use a SPLine
factor?
Also why does the sampling res of the AAMAP image = 8x8km while the one
created using IMGREMAP = 1x1?(see below)
thanks,
dave
------------------------------------------------------------------------------
An IMGLIST of the image created using AAMAP gives:
Image file directory listing for:MYDATA/IMAGES
Pos Satellite/ Date Time Center Res (km) Image_Size
sensor Lat Lon Lat Lon
--- ------------- ------------ -------- ---- ---- ----- ----- ------------
9696 G-8 IMG 5 SEP 99248 21:15:00 17 78
Band: 4 10.7 um Surface temp; longwave window 8.0 8.0 400 x 880
proj: 0 created: 2000332 200657 memo: RT GVAR
type:VISR cal type:BRIT
offsets: data= 2816 navigation= 256 calibration= 0 auxillary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 0 avg-smp: N
start yyddd: 1999248 start time:211515 start scan: 351
lcor: 6444 ecor: 6480 bytes per pixel: 1 ss: 70
Image Center Point Res (derived) Lat: 7.63 (km) Lon: 7.63 (km)
------------------------------------------------------------
An IMGLIST of the image created using IMGREMAP gives:
Image file directory listing for:MYDATA/IMAGES
Pos Satellite/ Date Time Center Res (km) Image_Size
sensor Lat Lon Lat Lon
--- ------------- ------------ -------- ---- ---- ----- ----- ------------
9696 G-8 IMG 5 SEP 99248 21:15:00 17 78
Band: 4 10.7 um Surface temp; longwave window 1.0 1.0 400 x 880
proj: 0 created: 2000332 220559 memo: RT GVAR
type:VISR cal type:BRIT
offsets: data= 2816 navigation= 256 calibration= 0 auxillary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 0 avg-smp: N
start yyddd: 1999248 start time:211515 start scan: 351
lcor: 9557 ecor: 9561 bytes per pixel: 1 ss: 70
Image Center Point Res (derived) Lat: 7.63 (km) Lon: 7.64 (km)
------------------------------------------------------------
The IMGLIST of the original untransformed image gives:
Image file directory listing for:MYDATA/IMAGES
Pos Satellite/ Date Time Center Res (km) Image_Size
sensor Lat Lon Lat Lon
--- ------------- ------------ -------- ---- ---- ----- ----- ------------
8696 G-8 IMG 5 SEP 99248 21:15:00 22 71
Band: 4 10.7 um Surface temp; longwave window 8.0 16.0 500 x 872
proj: 0 created: 1999248 214518 memo: RT GVAR
type:VISR cal type:BRIT
offsets: data= 2816 navigation= 256 calibration= 0 auxillary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 0 avg-smp: N
start yyddd: 1999248 start time:211515 start scan: 351
lcor: 3677 ecor: 9041 bytes per pixel: 1 ss: 70
Image Center Point Res (derived) Lat: 9.08 (km) Lon: 9.32 (km)
======================================================================
| Dave Vollaro address@hidden |
| SUNYA Atmospheric Science Phone: (518) 442-4273 |
| Earth Science Bldg Rm 226 |
| 1400 Washington Ave |
| Albany, NY 12222 |
======================================================================
From: Chris Sisko <address@hidden>
Date: Tue, 28 Nov 2000 09:41:56 -0500
Organization: National Hurricane Center
Subject: Re: imgremap vs aamap
Hello Dave,
In response to your question on the resolution difference you noted
when using IMGREMAP, we have also seen the exact same "1.0 X 1.0 Res"
when we used the IMGREMAP command - only when running McIDAS 7.7 on a
HPUX 11.x OS - an unsupported OS but under future consideration to be
supported by McIDAS. See the examples provided below.
What platform / OS are you currently using? Has anyone else seen this
before?
-- Chris Sisko
-----------
EXAMPES
-----------
(running McIDAS 7.7, HPUX OS 11.x) HP L-Class Server
==================================
Pos Satellite/ Date Time Center Res (km)
Image_Size
sensor Lat Lon Lat Lon
--- ------------- ------------ -------- ---- ---- ----- -----
------------
2 G-8 IMG 8 NOV 00313 18:15:00 20 75
Band: 1 0.65 um Visible - Cloud Cover 1.0 1.0 2500
x 4000
proj: 0 created: 2000313 182612 memo: RT IMGR VIS
type:VISR cal type:BRIT
offsets: data= 768 navigation= 256 calibration= 0
auxillary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 1 avg-smp: N
lcor: 8183 ecor: 8001 bytes per pixel: 1 ss: 70
Image Center Point Res (derived) Lat: 3.76 (km) Lon: 3.76
(km)
** note resolution is 1.0 X 1.0 km (Resolution info incorrect)
(running McIDAS 7.701 fast-track, LINUX RedHat 6.2) Dell PowerEdge
Server
===================================================
Pos Satellite/ Date Time Center Res (km)
Image_Size
sensor Lat Lon Lat Lon
--- ------------- ------------ -------- ---- ---- ----- -----
------------
imglist.k: ERROR: Unable to read LW file SATANNOT
2 8 NOV 00313 18:15:00 20 75
Band: 1 4.0 4.0 2500
x 4000
proj: 0 created: 2000313 192548 memo: RT IMGR VIS
type:VISR cal type:BRIT
offsets: data= 768 navigation= 256 calibration= 0
auxillary= 0
doc length: 0 cal length: 0 lev length: 0 PREFIX= 0
valcod: 0 zcor: 1 avg-smp: N
lcor: 8183 ecor: 8001 bytes per pixel: 1 ss: 70
Image Center Point Res (derived) Lat: 3.76 (km) Lon: 3.76
(km)
** note resolution is 4.0 X 4.0 km (Good!, except for error reading the
SATANNOT file).
________________________________________________________________________________
Christopher Sisko, Meteorologist / Programmer
National Hurricane Center / Tropical Prediction Center (NOAA)
11691 SW 17th Street
Miami, FL 33165
Phone: (305) 229-4431 Fax: (305) 553-5495
e-mail: address@hidden
Web address: http://www.nhc.noaa.gov
________________________________________________________________________________
From: John Benson <address@hidden>
Date: Tue, 28 Nov 2000 08:43:58 -0600 (CST)
Subject: Re: imgremap vs aamap
To: address@hidden
This is not the sort of thing which would be at all dependant on
platform or OS.
--address@hidden
From: Rick Kohrs <address@hidden>
Date: Tue, 28 Nov 2000 09:16:25 -0600
Subject: Re: imgremap vs aamap
Hello Dave,
My guess is that your older images were created with a fairly old
version of McIDAS. Newer versions of McIDAS have corrections to the
mercator projection, because of this you may see some navigational
differences and the differences seen when using "D" key. If you have
the original satellite data (probably not the case), you could remap
them all with IMGREMAP. If you find that the data are shifted by a
fixed number of lines/elements, you can use the command IMGCHA to change
line and element correction to adjust the navigation.
McIDAS version 7.6+ now use a resolution of 1 for all 'products'. We
consider images that are remapped to be products. Following the rule
that the highest resolution for a data source is assigned a resolution
of 1, we needed to assign these new and unique products a resolution of
1. You can still get the geographical resolution with the command
IMGLIST ... FORM=EXP.
Let me know if you need further information.
Rick