new Table B and D entries for interferometric radar data

[jbathegit]

Introduction

NASA and the U.S. Naval Research Laboratory (NRL) are requesting new BUFR Table B and D entries for reporting of interferometric radar data, for use in tracking meteor ionized trails as a way of measuring the intensity of winds in the mesosphere. This data is of interest and potential use by the wider international community, including the space weather community as well as meteorological NWP centers who may be looking to extend the height boundaries of their models beyond traditional previous limits.

Amendment details

Add a new BUFR Table D descriptor:

3-21-040 (Meteor radar high-altitude winds)

FXY	Description
3-01-150	WIGOS identifier
3-01-011	Year, Month, Day
3-01-012	Hour, Minute
2-07-003	Increase scale, reference value and data width
0-04-006	Second
2-07-000	Cancel increase scale, reference value and data width
3-01-022	Latitude/longitude (high accuracy), height of station
0-02-121	Mean frequency
0-02-125	Pulse repetition frequency
0-05-021	Bearing or azimuth
0-06-021	Distance
0-07-002	Height or altitude
0-10-080	Viewing zenith angle
0-21-022	Range bin offset
0-21-023	Range bin size
0-25-003	Number of integrated pulses
0-21-101	Number of vector ambiguities
0-08-023	First-order statistics
0-21-049	Amplitude of echo (digitizer counts)
0-08-023	First-order statistics
0-21-050	Decay time for echo to fall to half its peak amplitude
0-21-028	Differential phase
0-21-014	Doppler mean velocity (radial)
0-21-030	Signal to noise ratio
2-24-000	First-order statistical values follow
2-36-000	Define data-present bitmap
1-01-030	Repeat following value 30 times
0-31-031	Data present indicator
0-08-023	First-order statistics
2-24-255	First-order statistical values marker operator

For clarity, the initial occurrence of the first-order statistics is intended to report the maximum amplitude of the echo, whereas the second occurrence (via the marker operator) is intended to report the standard deviation of the mean radial velocity. The reason for the disparate approach is because in the former case there is only a maximum echo amplitude to be reported, whereas in the latter case there is both a mean radial velocity and a standard deviation of that mean radial velocity to be reported.

Add new BUFR Table B descriptors:

FXY	Element Name	Unit	Scale	Reference Value	Data Width
0-21-049	Amplitude of echo (digitizer counts)	Numeric	0	0	16
0-21-050	Decay time for echo to fall to half of its peak amplitude	s	3	0	16

Requestor(s)

Jeff Ator (NOAA/NWS) (@jbathegit)
David Kuhl (NRL) (@davidkuhl)
Jun Ma (NRL) (@junma86)
Diego Janches (NASA/GSFC) (@djanches)

Stakeholder(s)

No response

Expected impact of change

MEDIUM

Consultations

No response

Data exchange plans

No response

Comments

No response

[amilan17]

https://github.com/wmo-im/et-data/wiki/2025.04.30.et.data notes:
Jeff introduced the proposal; data exchange plans are unknown;

[jbathegit]

As noted during today's telecon, a contractor working with NRL is currently working to produce BUFR sample messages for validation, and according to the above proposal. Will keep you all posted as I/we hear further updates.

[jbathegit]

@davidkuhl @djanches @junma86 a question was also asked today by our international colleagues as to whether the BUFR data would be available for free and open exchange/use by the global met community, once the above proposal is fully validated and approved and actual data begins to be made available in real time? Or will there be any restrictions on who is/isn't allowed to see this data?

[davidkuhl]

It is our intention that all meteor radar data that is in the BUFR format will be available for free and open to exchange/use by the global met community. Our plan is to push the meteor radar BUFR files through the GTS system in real time to all of the operational centers, with the primary center that this project is interested in is the NAVY's FNMOC operational center. I will let @djanches give the information on what he thinks will be the initial observation locations that will be sent (about 8 stations operated by the Genesis company in Australia). But I should also add that we hope to add to this initial set as the years go on, including more from Genesis but hopefully from other companies as well.

[amilan17]

Our plan is to push the meteor radar BUFR files through the GTS system in real time to all of the operational centers,

@davidkuhl Thank you for the valuable information. Please note that the GTS is replaced by WIS 2.0. This is an overview page about WIS2 with links to relevant publications: https://community.wmo.int/en/activity-areas/wis and other information.

[amilan17]

As noted during today's telecon, a contractor working with NRL is currently working to produce BUFR sample messages for validation, and according to the above proposal. Will keep you all posted as I/we hear further updates.

@jbathegit Is this targeted for FT2025-2?

[jbathegit]

@jbathegit Is this targeted for FT2025-2?

That's what we're targeting, at least for now. But of course that will all depend on how soon sample messages can be made available to complete the validation process. If that slips, then this proposal can be correspondingly deferred to a later FT cycle.

[davidkuhl]

Our plan is to push the meteor radar BUFR files through the GTS system in real time to all of the operational centers,

@davidkuhl Thank you for the valuable information. Please note that the GTS is replaced by WIS 2.0. This is an overview page about WIS2 with links to relevant publications: https://community.wmo.int/en/activity-areas/wis and other information.

Yes, we are tracking this and our partners at NOAA who are helping us put it into the GTS feed are making sure it works with WIS 2.0. Thanks!

[davidkuhl]

What's the date we need the sample message made available or we risk deferral?

[jbathegit]

What's the date we need the sample message made available or we risk deferral?

I'll let @amilan17 or @marijanacrepulja correct me if I'm wrong, but I believe we'd have at least until early-mid July to complete the validation process in time for the next (November 2025) FT.

[davidkuhl]

What's the date we need the sample message made available or we risk deferral?

I'll let @amilan17 or @marijanacrepulja correct me if I'm wrong, but I believe we'd have at least until early-mid July to complete the validation process in time for the next (November 2025) FT.

Great, we'll shoot for June. Thanks!