BUFR Table D 10, New BUFR template for satellite reflectance

[marijanacrepulja]

Initial request

Proposal for the new BUFR template for representation of MSG4 SEVIRI Level 1.5 and GOES ABI Level 1b observations. This is to support assimilation of the reflectances.

Amendment details

3 xx xxx		Satellite reflectance	Note
	001007	SATELLITE IDENTIFIER
	002019	SATELLITE INSTRUMENTS
	002020	SATELLITE CLASSIFICATION
	001033	IDENTIFICATION OF ORIGINATING/GENERATING CENTRE
	001034	IDENTIFICATION OF ORIGINATING/GENERATING SUB-CENTRE
	005001	LATITUDE
	006001	LONGITUDE
	114000	Delayed replication of 14 descriptors
	031001	Delayed descriptor replication factor
	005042	CHANNEL NUMBER
	301011	YEAR, MONTH, DAY
	301013	HOUR,MINUTE, SECOND
	002153	SATELLITE CHANNEL CENTRE FREQUENCY
	202127	CHANGE SCALE
	002154	SATELLITE CHANNEL BAND WIDTH
	202127	CHANGE SCALE	CANCEL
	007024	SATELLITE ZENITH ANGLE
	005021	BEARING OR AZIMUTH
	007025	SOLAR ZENITH ANGLE
	005022	SOLAR AZIMUTH
	033003	QUALITY INFORMATION
	014044	CHANNEL RADIANCE
	015042	REFLECTANCE

Comments

No response

Requestor(s)

Enter list of requestors.

Stakeholder(s)

Marijana Crepulja, Volkan Firat, Angela Benedetti, Cristina Lupu, Chris Burrows (all from ECMWF)

Publication(s)

Example: Manual on Codes (WMO-No. 306), Volume I.2, BUFR table D

Expected impact of change

MEDIUM

Collaborators

No response

References

No response

Validation

No response

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.2%263May.2023 notes:
@antoinemerle will ask if EUMETSAT is aware of this data and should make this proposal instead. It's possible that EUMETSAT doesn't have a requirement to disseminate this in BUFR. ECMWF is converting to BUFR to support the DestinE project.

Quick EDIT from Antoine : correcting name from Destiny to DestinE

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.2&3May.2023 notes:

similar conversation to #159 about who should propose this;
@amilan17 will ask about WMO regulations
@SimonElliottEUM, @antoinemerle will ask if there is any official position from EUMETSAT.

[amilan17]

https://github.com/wmo-im/CCT/wiki/16.May.2023.satellite.issue notes:
Marijana explained the background of the this proposal; ECMWF is retrieving this data from EUMETSAT as NetCDF; They were told that EUMETSAT is not planning on creating BUFR and therefore decided to make a proposal; (Christina) explained that they are also interested in reflectance in DWD and would appreciate wider sharing before proposing; (Marijana) ECMWF will focus on collaborating more up front, but noting that the development of this proposal is very new; (Tony) EUMETSAT is generally in using the data as quickly as possible and we are happy to help with generating BUFR data but cannot wait for decisions to be made; (Simon) It's important to get the sequences right and this sometimes takes time; We should find a new way of working in this new agile way; assumed that proposals added here were final and maybe realize that this is closer to the beginning of the process than before; Also note that CGMS is a resource; (Tony) will put procedures on the agenda for [GODEX] conference. (Anna) it could be helpful to have some best practices when proposing new amendments and ...(Marijana) ... (Sibylle) everyone has a lot of work to do and it would be good to get specialists involved earlier if possible and this team provides the technical expertise; (Simon) I agree that the work on developing the proposal is developed with experts BEFORE is important and this makes the workload easier for TT-TDCF; (Christina) agree with Simon and Sibylle, but what is the fastest way to get the right people included up front? (Marijana) the scientists in ECMWF have a lot of discussions in advance and then come to Marijana for requesting the BUFR format; And is not aware to what extent the scientific conversations happen before it comes to her (Sibylle) Do you send the sequence back to the original proposals within ECMWF for comments? (Marijana) the scientists come to Marijana with the requirements and look at the sample data based on their requirements and is happy to circulate earlier before bringing to this group (Simon) In response to Christina's question, there is CGMS WGI Task Group on Satellite Data and Codes and their terms of reference specifically state that they are supporting this group;

[amilan17]

https://github.com/wmo-im/CCT/wiki/16.May.2023.satellite.issue notes:
Questions from Christina:

• Can this sequence be used for other satellites? (Marijana) it's not fixed, it's just what's being used for texting, noting that the name is generic and this open for discussion with the team;
• Is this geostationary only or for polar orbiting too?
• Latitude/longitude, it would be useful to have the image location too.
• Why is time included in the replication for each channel? (Marijana) each channel can have it's own time.
• Can you add calibration methods and factors?

@marijanacrepulja will circulate an email for further discussions with Christina, Angela, Simon and Jeff.

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.6.7.June.2023 notes:
still under discussion, may need to be postponed to next FT cycle

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.13.July.2023 notes:

moved to FT2024-1

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.17.18.October.2023 notes:

Marijana will double check with colleagues on this request

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.21.22.November.2023 notes:
ready for validation

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.15.December.2023 notes:

moved to FT2024-2

[amilan17]

https://github.com/wmo-im/CCT/wiki/Teleconference.16.May.2024 notes:
Simon suggested adding WIGOS identifier in front; team decised to delay this proposal to a future fast-track.

[SimonElliottEUM]

Concerning WIGOS Station identifiers for satellites: These are of the form 0-20009-0-. So, for MSG4 for example, 0-20009-0-70 and for GOES-18 0-20009-0-272

[amilan17]

@marijanacrepulja is this now for FT2024-2?