Changes between Version 6 and Version 7 of ticket/261/TicketSummary/DescriptionAmv


Ignore:
Timestamp:
Feb 26, 2016 3:34:35 PM (3 years ago)
Author:
Jin Lee
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ticket/261/TicketSummary/DescriptionAmv

    v6 v7  
    1515|| || || || ||
    1616|| amv160 || NESDIS || GOES-E, GOES-W, Aqua/MODIS, locally generated AMV's from MTSAT-2 || The originating centre for the loally generated AMV's from MTSAT-1R, MTSAT-2 and Himawari-8 is ???. [[BR]][[BR]] Note also that the expected error values are converted to QI values to allow OPS to process them as if they are JMA-supplied winds. [[BR]][[BR]] Q. Is Himawari-8 given the satellite ID of 173 in the Bufr file? ||
    17 || amv254 || EUMETSAT Operation Centre || contains METEOSAT First Generation || ||
    18 || amv254msg || EUMETSAT Operation Centre || contains METEOSAT Second Generation || ||
    19 || amv34 || JMA || MTSAT-1R, MTSAT-2 and Himawari-8 || ||
     17|| amv254 || EUMETSAT Operation Centre || METEOSAT First Generation: METEOSAT-7 || ||
     18|| amv254msg || EUMETSAT Operation Centre || METEOSAT Second Generation: METEOSAT-8, -9, -10 || ||
     19|| amv34 || JMA || MTSAT-2 (and Himawari-8????) || ||
    2020
    2121Note 1. AMV's from Himawari-8 were not assimilated for the trial period (Q. even JMA-generated AMS's?)