In order to encode RO data into BUFR, there needs to be a mapping between the satellite character code (usually a 4-chr string) in the UCAR or ROPP netCDF or dsc/dat GFZ files, and the numeric Satellite Identifier code in BUFR (and reverse on decode). The character code is also used when there is a need to process different satellites in different ways (e.g. in the ROPP pre-processor).

WMO have recently approved the BUFR codes for the COSMIC-2 constellation as follows:

From: Jeff Ator - NOAA Federal [mailto:jeff.ator@noaa.gov] 
Sent: 26 January 2015 14:40
To: dhunt@ucar.edu
Cc: Offiler, Dave; ector@ucar.edu; schrein@ucar.edu; William Kuo;
Lidia Cucurull - NOAA Affiliate; Bradley Mabe - NOAA Federal;
Shucai Guan - NOAA Federal
Subject: Re: Fwd: BUFR sat id code for COSMIC-2

Hi Everyone,

Just to close the loop on this, the following is what was approved
by the codes team during the December review period:

750  COSMIC-2 E1
751  COSMIC-2 E2
752  COSMIC-2 E3
753  COSMIC-2 E4
754  COSMIC-2 E5
755  COSMIC-2 E6

724  COSMIC-2 P1
725  COSMIC-2 P2
726  COSMIC-2 P3
727  COSMIC-2 P4
728  COSMIC-2 P5
729  COSMIC-2 P6
As you can surmise, "E" means equatorial and "P" means polar.
These new entries will get published in Common Code Table C-5 
in the next table update in early May.
-Jeff

In addition, UCAR confirm the character codes that they will included in their netCDF files:

From: Doug Hunt
Re: Fwd: BUFR sat id code for COSMIC-2	
Sent: Mon 26/01/2015 17:41
To: Offiler, Dave

Hi Dave:  You read my mind!  COSMIC-2 equatorial will be named

C2E1-6

We haven't got round to putting in the code for COSMIC-2 polar yet,
but I'm sure it will be C2P1-6 as well.

Take care,
   Doug

Hence the mappings:

Constellation  Orbit          netCDF          BUFR
-----------------------------------------------------
COSMIC-2 E1-6  Equatorial  'C2E1-C2E6' <--> 750-755
COSMIC-2 P1-6  Polar       'C2P1-C2P6' <--> 724-729

need to be included in ropp_io/bufr as new array entries in: (a) namelist file roppbufrcodes.nl (b) source code file convertcodes.f90 recalling that (a) has precedence over (b) which is a fall-back default list, so that should COSMIC-2 support be needed for ROPP-8, only a new namelist file need be given to users.

Attachments (1)

FW_Fwd_BUFR_sat_id_code_for_COSMIC-2.txt (6.8 KB ) - added by Ian Culverwell 10 years ago.
FW_Fwd_BUFR_sat_id_code_for_COSMIC-2.txt

Download all attachments as: .zip

Change history (5)

by Ian Culverwell, 10 years ago

FW_Fwd_BUFR_sat_id_code_for_COSMIC-2.txt

comment:1 by Ian Culverwell, 8 years ago

ropp_io/bufr/convertcodes.f90 has been updated at r4917.

comment:2 by Ian Culverwell, 8 years ago

ropp_io/bufr/roppbufrcodes.nl has been updated at r4918.

comment:3 by Ian Culverwell, 8 years ago

ropp_io/bufr/gtshdrs.f90 has been updated at r4919.

(According to Dave:

[T]his is optional; it's a copy from the current 
BUFR-24.0.2 package which supports a modified routing 
header intro string for NOAA (GB-GNSS), which isn't 
needed for RO. So keep the files in sync or just stick 
with the existing version.

We choose to keep in synch.)

comment:4 by Dave Offiler, 8 years ago

Cc: ian.culverwell@… added
Resolution: fixed
Status: newclosed

Have checked Ian's merge into ROPP90_protoype and all is well. Pudding proof will have to await real COSMIC-2 data from UCAR implementing the satid codes they promised.

Closing this Ticket.

Note: See TracTickets for help on using tickets.