New regional EARS-MERSI service to be available soon

Regional EARS-MERSI data will be available on EUMETCast from 22 April.

Thursday, 16 April 2020

The new EARS-MERSI service will provide the 1 km resolution product of the MERSI-2 (Medium Resolution Spectral Imager – 2) instruments onboard the CMA’s FY-3 satellite series, starting with FY-3D which is the first satellite of the FY-3 series carrying the MERSI-2 instrument.

MERSI-2 is a combination of the MERSI-1 (20 channels) and the VIRR (Visible and Infra-Red Radiometer) (five channels) instruments onboard FY-3A, -3B and -3C, so has 25 channels in total. It has 2048 pixels across-track and ~400 lines in a 1-minute segment.

The EARS-MERSI service will include data from the Athens, Kangerlussuaq, Lannion, Maspalomas and Svalbard stations.

The data will be processed to level-1 using the processing package (FY3_IPP) provided by CMA. As with the AVHRR and VIIRS regional services, we will provide 1-minute segments removing overlaps between stations. There are 2 files per 1-minute segment.

NOTE: For some parameters, the values may exceed the range which is specified by the valid range attribute of these parameters. This could lead to reading problems with HDF-readers that use the valid range attribute to check the validity of the data (e.g. some pytroll routines). The issue is being investigated with CMA.

The data will be distributed on EUMETCast Europe, on the High Volume Service, Transponder 1 (HVS-1):

Channel: E1H-RDS-2
Multicast address: 224.223.223.2
PID: 601

Filename convention:

FY3D_<startDate>_<startTime>_<endTime>_<orbitNumber>_MERSI_1000M_L1B.HDF (for the scientific data)
FY3D_<startDate>_<startTime>_<endTime>_<orbitNumber>_MERSI_GEO1K_L1B.HDF (for the geolocation data)

Example filenames:

FY3D_20200217_111100_111200_7786_MERSI_1000M_L1B.HDF
FY3D_20200217_111100_111200_7786_MERSI_GEO1K_L1B.HDF

There will be ~250 files/day for each file type.
Total volume: ~5 GB/day

Users wishing to receive the EARS-MERSI data should register via our Earth Observation Portal (EOP).

For more information, contact our User Service Helpdesk.

 
We use essential cookies to ensure that we give you the best experience on our website. To analyse website traffic we also use third-party performance cookies. If you are ok with the use of essential as well as non-essential cookies, please select Accept & Continue. Instructions on how to prevent the use of non-essential cookies are available under our Terms Of Use, or simply select Decline Cookies.