Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new entry to Common Code Table C-8 for SWIM instrument on CFOSAT #67

Closed
SimonElliottEUM opened this issue Oct 1, 2021 · 6 comments · Fixed by #78
Closed

Add new entry to Common Code Table C-8 for SWIM instrument on CFOSAT #67

SimonElliottEUM opened this issue Oct 1, 2021 · 6 comments · Fixed by #78
Assignees
Milestone

Comments

@SimonElliottEUM
Copy link
Contributor

SimonElliottEUM commented Oct 1, 2021

Branch

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

Summary and purpose

Data from the SWIM instrument on the CFOSAT satellite are being converted into BUFR for international exchange. A suitable entry for the instrument is needed. Entry number 63 is available and would be appropriate.

Action proposed

Allocate entry 63 in Common Code Table C-8 for SWIM

Discussions

Standard request for new entry in common code table

Detailed proposal

The entry should be as follows ...
Code: 63
Agency: CNES
Type: Rotating multi-beam altimeter
Instrument short name: SWIM
Instrument long name: Surface Waves Investigation and Monitoring

@amilan17 amilan17 added this to the FT2022-1 milestone Oct 5, 2021
@amilan17
Copy link
Member

amilan17 commented Oct 5, 2021

36 or 63?

@SimonElliottEUM
Copy link
Contributor Author

@amilan17 In fact it would work with either 63 or 36, but I request 63 (sixty three) in this case. I regret the wrong typing, but I was talking in German and writing in English, and we say the numbers the opposite way around.

@SimonElliottEUM
Copy link
Contributor Author

@jitsukoh @amilan17 This branch is ready for the next step

@amilan17
Copy link
Member

@SimonElliottEUM - please update the branch

SimonElliottEUM added a commit that referenced this issue Nov 10, 2021
@SimonElliottEUM
Copy link
Contributor Author

@jitsukoh @amilan17 This branch is now really ready for the next step - sorry for false alarm on 09/11/2021

@jitsukoh
Copy link

@SimonElliottEUM @amilan17 I confirm that the branch is updated and this issue was moved to the validated status.

@amilan17 amilan17 linked a pull request Nov 11, 2021 that will close this issue
@amilan17 amilan17 closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants