Opened 7 years ago
Closed 6 years ago
#507 closed enhancement (fixed)
Allow BUFR reader/writer to handle GRACE-FO profiles
Reported by: | Ian Culverwell | Owned by: | Ian Culverwell |
---|---|---|---|
Priority: | normal | Milestone: | 9.1 |
Component: | ropp_io | Version: | 9.0 |
Keywords: | GRACE-FO, BUFR | Cc: |
Description
We should probably make arrangements for this satellite. An email from Harald Anlauf on 1/5/2018 suggests some codes:
Dear colleagues, after discussing matters, DWD is preparing a proposal for the next IPET-CM meeting taking place in Offenbach at the end of May. The current proposal is to assign the following codes: Table C-5: Satellite-ID Name 802 GRACE-C (GRACE-FO) 803 GRACE-D (GRACE-FO) Alternative proposals would include GRACE-FO-A and GRACE-FO-B, GRACE-F1 and GRACE-F2, or similar. If nobody objects, I'd prefer to stay with the shortest variant above. Table C-8: (Instrument ID) Code Agency Shortname Longname 104 NASA Tri-G Triple-G (GPS, Galileo, GLONASS) The code (104) has been suggested by Doug and is still available. The other information would make the entry also agree with the current OSCAR entry, except that I have shortened the shortname from "Tri-G (GRACE-FO)". With BUFR messages, both satellite ID and instrument ID are provided. If it is considered important, we will propose the longer version of the shortname to appear in the document http://www.wmo.int/pages/prog/www/WMOCodes/WMO306_vI2/LatestVERSION/WMO306_vI2_CommonTable_en.pdf pages 33ff. I'd appreciate your feedback - or rather approval :) - soon, so that the proposal will be ready in time for the meeting. Thanks, Harald
We could use these provisionally. Code and BUFR document would need updating.
Note:
See TracTickets
for help on using tickets.
After checking with Harald, these suggestions were amended:
These proposed GRACE FO codes were incorporated in the ic_gnos branch at r5553 and r5554. See #377 for results of testing.