You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This document proposes a new entry to Common Code Tables C5 in order to multiple Sentinel-3 satellites.
Action proposed
The meeting is requested to approve the contents for inclusion within the next update to the WMO Manual on Codes.
Discussions
EUMETSAT will produce atmospheric motion vectors using data from the SLSTR instrument (Sea and land surface temperature radiometer) on multiple Sentinel-3 satellites (initially Sentinel-3 A and Sentinel-3 B).
In order to be able to represent a combination of Sentinel-3 satellites, a new entry in Common Code Table C-5 is required. This entry must be in the range from 850 to 869 as this is to be used to indicate combinations of satellites.
Detailed proposal
Add the following elements to Common Code Table C5 Satellite identifier:
Code figure for I6I6I6
Code figure for BUFR (Code table 0 01 007)
Code figure for GRIB Edition 2
Meaning
856
856
856
Combination of Sentinel-3 satellites
The text was updated successfully, but these errors were encountered:
Summary and purpose
This document proposes a new entry to Common Code Tables C5 in order to multiple Sentinel-3 satellites.
Action proposed
The meeting is requested to approve the contents for inclusion within the next update to the WMO Manual on Codes.
Discussions
EUMETSAT will produce atmospheric motion vectors using data from the SLSTR instrument (Sea and land surface temperature radiometer) on multiple Sentinel-3 satellites (initially Sentinel-3 A and Sentinel-3 B).
In order to be able to represent a combination of Sentinel-3 satellites, a new entry in Common Code Table C-5 is required. This entry must be in the range from 850 to 869 as this is to be used to indicate combinations of satellites.
Detailed proposal
Add the following elements to Common Code Table C5 Satellite identifier:
The text was updated successfully, but these errors were encountered: