new C-5 entries for NOAA 22 and 23

[jbathegit]

Initial request

In preparation for the launch of the next NOAA JPSS satellites beginning in 2027, U.S. NESDIS is requesting new C-5 entries for these satellites.

Amendment details

COMMON CODE TABLE C-5: Satellite identifier

Code	Meaning
805	NOAA 22
806	NOAA 23

Comments

Note that we are requesting the above numbers in the 800-849 range of CCT C-5 for these future satellites, even though recent JPSS satellites such as NOAA 19, NOAA 20, NOAA 21, etc. were defined within the 200-299 range. This is because of the rule for C-5 which states that only even deciles should be used for polar orbiting satellites, and those deciles are now full within the 200-299 range, as well as within the 700-799 range which we also checked.

Requestor(s)

Jeff Ator (NOAA/NWS)
Lihang Zhou (NOAA/NESDIS)
Walter Wolf (NOAA/NESDIS)

Stakeholder(s)

Enter list of stakeholder(s).

Publication(s)

Example: Manual on Codes (WMO-No. 306), Volume I.2, Common Code Table C-5

Expected impact of change

None

Collaborators

No response

References

No response

Validation

No response

[amilan17]

https://github.com/wmo-im/tt-tdcf/wiki/2024.10.15.tt.tdcf notes:

• @SimonElliottEUM can you please bring this to CGMS as needed?

[amilan17]

https://github.com/wmo-im/et-data/wiki/2024.12.04.et.data notes:
waiting for feedback from @SimonElliottEUM

[SimonElliottEUM]

@amilan17 @jbathegit NOAA 22 and NOAA 23 will be in a polar orbit and so need an even decile. 746-749 are free, as are 760, 768 and 769. The proposal must use even deciles, which ever value we take. Can I propose NOAA 22 = 768 and NOAA 23 = 769 to the CGMS TG? Please Confirm

[jbathegit]

Wow, I can't believe I missed that! :-} I was aware of the even decile rule, and I'd even referred to it in the above comments when I first wrote up this issue. Yet for whatever reason when I went to pick the actual numbers, I somehow ended up using an odd decile. So definitely a brain fart on my part, and thanks for catching that Simon!

768 and 769 are fine with me, and I'll go ahead and update the above part of the proposal accordingly. Thanks again!

[jbathegit]

OK, I just remembered that 768 and 769 were already allocated during the recent FT2024-2, re: #195 So we can't use those numbers.

Furthermore, 746-749 are also already allocated for DMSP 1-4, as shown in https://github.com/wmo-im/CCT/blob/master/C05.csv

So bottom line, and unless I'm missing something, the only even decile entry left in the 700-799 range is 760. And we need two entries for this proposal, so is it OK if we leak into the 800 range and ask for, say, 805 and 806? I realize the entire 700-799 range had been allocated to the U.S., but it looks like we've now managed to fill up all of the polar entries in that range.

Please lmk - thanks!

[SimonElliottEUM]

@jbathegit A problem is that WMO's MS Github is just a working tool and the actual allocated number should be published by WMO somewhere sensible in a PDF type doc. I could find the FT 2024 II in the end but the DMSP satellites weren't in there. Pah! That said, your proposal to use 805 and 806 is sound. I will pass that on to CGMS TG.

[amilan17]

A problem is that WMO's MS Github is just a working tool and the actual allocated number should be published by WMO somewhere sensible in a PDF type doc

In this case, you can rely on the master branch to determine what is available.

[SimonElliottEUM]

@jbathegit @amilan17 CGMS TGSDC contacted. Confirmation will be by 18/01/2025