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

[McIDAS #WGZ-508649]: MTSAT Data

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: [McIDAS #WGZ-508649]: MTSAT Data
  • Date: Thu, 31 Oct 2013 15:07:55 -0600
Hi Greg,

re:
> I found this page today while wandering around JMA site:
> 
> http://mscweb.kishou.go.jp/operation/status/mtsat.htm
> 
> Near the bottom is a table titled "Annual Schedule" which
> makes it look like they are swapping satellites with MTSAT-1R running most of 
> the time.
> Very odd. According to the schedule it looks like they just swapped back to 
> MTSAT 1R on
> October 22. They are supposed to switch to MTSAT 2 on Dec 19th.

OK, this fits with the insight that SSEC provided.  It looks like JMA website
indication that MTSAT-2 is the operational satellite is not quite correct.

re:
> My IMGLIST output for MTS looks like:
> 
> xtuser@lightning:~/mcidas$ imglist.k MTS/MTGLOB04I4.0 FORM=ALL
> Image file directory listing for:MTS/MTGLOB04I4
> Pos Satellite/         Date       Time      Center      Res (km)   Image_Size
> sensor                                 Lat  Lon    Lat   Lon
> --- -------------  ------------  --------  ---- ----  ----- ----- ------------
> 3  MTSAT-1R      31 OCT 13304  19:30:00     0 -140
> Band: 4    6.75 um IR Mid-level Water Vapor          4.02  3.99  2750 x 2752
> proj:    0 created: 2013304 195509  memo: MTSAT data from HRIT
> type:MTST     cal type:RAW
> offsets:  data=   28928 navigation=  256 calibration= 2816 auxiliary=    0
> doc length:   0   cal length:   0   lev length:   0 PREFIX=   0
> valcod:          0 zcor:  1 avg-smp: N
> start yyddd: 2013304  start time:193000  start scan:    0
> lcor:    1  ecor:     1  bytes per pixel: 2  ss: 84
> Resolution Factors (base=1):   Line=    4.0   Element=    4.0
> imglist.k: done

OK.  The fact that the central longitude is 140E shows that the image really
is from MTSAT-1R (according to the guidance we received from SSEC).  So, it
looks like everything is OK, no?

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: WGZ-508649
Department: Support McIDAS
Priority: Normal
Status: Closed