Add new entries to C-5 to identify HY-2D, FY-3E and FY-4B satellites of China

[Annie-FangZHAO]

Branch

https://github.com/wmo-im/CCT/tree/issue63

Summary and purpose

This document proposes new entries to Common Code Tables C-5 to identify HY-2D, FY-3E and FY-4B satellites of China.

Action proposed

The meeting is kindly invited to validate the proposed new entries to be included within the next update to the WMO Manual on Codes.

Discussions

HY-2D was launched in May this year. It is the fourth marine dynamic environment satellite of China. It integrates active and passive microwave sensors, and is one of the marine series satellites. It has high-precision orbit measurement and orbit determination capabilities, and has the ability to image global image under all weather conditions during day and night.

FY-3E was launched in July this year. It is the first early morning orbit meteorological satellite for civil use in the world. The main payloads onboard are Microwave Thermometer, Microwave Hygrometer, Infrared Hyperspectral Atmospheric Sounder, GPS Occultation Sounder and Dual-frequency Microwave Active Scattering Radar.

FY-4B was launched in June this year. It is the second of FY-4 geostationary meteorological satellite series of China aiming to serve as a operational satellite. The main payloads onboard are Advanced Geostationary Radiation Imager, Geostationary Interferometric Infrared Sounder, Geostationary High-speed Imager and Space Environment Package.

For the possible production of satellite products encoded in BUFR, we’d like to request new entries to Common Code Table C-5 to identify HY-2D, FY-3E and FY-4B.

Detailed proposal

Code figure for I6I6I6	Code figure for BUFR (Code table 0 01 007)	Code figure for GRIB Edition 2
505	505	505	Hai Yang 2D (HY-2D, SOA/NSOAS China)
524	524	524	FY-3E
531	531	531	FY-4B

[jitsukoh]

@Annie-FangZHAO can you update the branch?

[Annie-FangZHAO]

@jitsukoh @amilan17
The branch is updated. Thank you.

[jitsukoh]

@Annie-FangZHAO thank you for updating.
@amilan17 I confirm that the branch is updated and the issue was moved to the validated status.

[amilan17]

has PR