Hurricane City Hurricane TV CaneTalk Logo
CaneTalk Forum | Search Messages | Post a New Message | Member Map

| HurricaneCity | Tropical Atlantic | Chat Room | Board Rules




NHC soliciting public comments on changing Reconnaissance Vortex Data Message format for 2018

Posted by Chris in Tampa on 4/26/2017, 8:19 pm

This is going to be fun to code, while still allowing all old messages to be decoded properly. At least I'll have a year. Looks like I will either need to look for the year or test the message, like the coordinates, to see if it is in the new or old format once they decide on the new format.

Though I do like the changes. Only having the fields for the wind inbound to the center doesn't make sense when you can simply update the vortex. (Previously outbound winds were just added to remarks section, which at times could be hard for my site to automatically decode.) Post the vortex message with inbound wind after the plane passes through the center. Then post an updated vortex on the outbound leg from the center when the plane gets the highest outbound wind.





NOUS41 KNHC 241611
PNSNHC

Public Information Statement
NWS National Hurricane Center Miami FL
1210 PM EDT Mon Apr 24 2017

To:      Subscribers:
        -NOAA Weather Wire Service
        -Emergency Managers Weather Information Network
        -NOAAPORT
        Other NWS Partners, Users and Employees

From:    James Franklin
        Branch Chief, Hurricane Specialist Unit
        NCEP/National Hurricane Center

Subject: Soliciting Public Comments through
        May 26, 2017 on Changing the
        Reconnaissance Vortex Data Message Format

The Office of the Federal Coordinator for Meteorology Working Group
for Hurricane and Winter Storm Operations and Research (WG/HWSOR),
at the 2017 Interdepartmental Hurricane Conference, has proposed to
change the reconnaissance Vortex Data Message format for the 2018
hurricane season.  This product is transmitted from NOAA and Air
Force hurricane hunter aircraft and issued under AWIPS header
MIAREPNT2 and WMO header URNT12 KNHC. The format changes below will
enhance the utility of the Vortex Message by including important
parameters previously not provided, or provided only optionally in
the comment section, and by improving the organization of the
message.  The NWS is seeking comments on these proposed changes
through May 26, 2017.

The primary changes and rationales are listed below, along with
examples of the current and proposed message format:

1.  The current format (see example) has a formal entry only for
inbound wind maxima, with any outbound wind maxima appearing in the
comment section.  In the proposed format, Items L through O comprise
a new outbound wind maxima section to simplify data decoding and to
ensure that no data are missed.  The new outbound wind maxima
section appears in a similar format to the inbound maxima data
(Items H through K).

2.  The latitude and longitude will be listed in decimal degrees
instead of degrees and minutes to better accommodate NHC and other
users' needs.

3.  The proposed message includes a new tropical cyclone center data
block section (Items C through G).  The surface wind reported by
dropsonde at the system's center is now given in Item E.  Center/eye
shape and size characteristic lines are moved up to Items F and G
from Items L and M.

4.  The current message lacks most wind observation times; the
proposed format appends the observation times to the bearing and
range location Items.

5.  To better collect similar data together, the inbound maximum
surface and flight-level wind block (Items E through G in the
current format) is shifted downward to Items H through K.

NWS and the WG/HWSOR will evaluate all comments to determine whether
to proceed with this change.


Send comments on this proposal to:

Jessica Schauer
NWS Marine, Tropical and Tsunami Services Branch
National Hurricane Center
Miami, FL  33165
jessica.schauer(at)noaa.gov

and

James Franklin
Hurricane Specialist Unit
National Hurricane Center
Miami, FL  33165
james.franklin(at)noaa.gov

National Public Information Statements are online at:
http://www.nws.noaa.gov/om/notif.htm


Current format example:

URNT12 KNHC 241133
VORTEX DATA MESSAGE   AL162016
A. 24/11:12:50Z
B. 10 deg 58 min N
 082 deg 46 min W
C. 700 mb 2927 m
D. 90 kt
E. 144 deg 5 nm
F. 253 deg 78 kt
G. 158 deg 8 nm
H. 977 mb
I. 10 C / 3042 m
J. 18 C / 3045 m
K. NA / NA
L. CLOSED
M. C20
N. 12345 / 7
O. 0.02 / 1 nm
P. AF301 0616A OTTO               OB 13
MAX OUTBOUND AND MAX FL WIND 108 KT 349 / 14 NM 11:17:00Z
CNTR DROPSONDE SFC WIND 210 / 11 KT

An explanation of the current format can be found at:
http://www.ofcm.gov/publications/nhop/FCM-P12-2016Change1.pdf
(see Figure 5-3, page 5-6).


Proposed format example:

URNT12 KNHC 241133
VORTEX DATA MESSAGE   AL162016
A. 24/11:12:50Z
B. 10.97 deg N 082.77 deg W
C. 700 mb 2927 m
D. 977 mb
E. 210 deg 11 kt
F. CLOSED
G. C20
H. 90 kt
I. 144 deg 5 nm 11:07:00Z
J. 253 deg 78 kt
K. 158 deg 8 nm 11:07:30Z
L. 95 kt
M. 314 deg 5 nm 11:17:00Z
N. 033 deg 108 kt
O. 349 deg 14 nm 11:17:30Z
P. 10 C / 3042 m
Q. 18 C / 3045 m
R. NA / NA
S. 12345 / 7
T. 0.02 / 1 nm
U. AF301 0616A OTTO OB 13
MAX FL WIND 108 KT 349 / 14 NM 11:17:00Z

The individual items in the proposed format are defined as follows:

A. Date and time of fix
B. Latitude and longitude of vortex center fix
C. Minimum height at standard atmospheric level
D. Minimum sea-level pressure from dropsonde or extrapolation
E. Dropsonde center wind speed and direction
F. Eye character
G. Eye shape/orientation/diameter
H. Estimate of maximum inbound surface wind observed
I. Bearing, range and time of wind observed in Item H
J. Maximum inbound flight-level wind
K. Bearing, range and time of wind observed in item J
L. Estimate of maximum outbound surface wind observed
M. Bearing, range and time of wind observed in item L
N. Maximum outbound flight-level wind
O. Bearing, range and time of wind observed in item N
P. Maximum flight-level temp/pressure altitude outside eye
Q. Maximum flight-level temp/pressure altitude inside eye
R. Dew point temperature/sea surface temperature inside eye
S. Fix determined by (codes for observation type)
T. Navigation fix accuracy/meteorological accuracy
U. Aircraft id, mission number, cyclone name, and observation number
End remarks include maximum flight-level wind, bearing, range and
time during mission

From: http://www.nhc.noaa.gov/text/MIAPNSNHC.shtml






Meanwhile, in other recon news...





I was trying to find information about when the NOAA hurricane hunters will move in (haven't seen anything and they had been shooting for May 1st I thought) and I happened to come across this article which I missed:

http://www.tampabay.com/news/military/macdill/noaa-to-scrap-one-orion-ahead-of-hurricane-hunters-move-to-lakeland/2312978
Looks like auction closed at $70,100:
https://gsaauctions.gov/gsaauctions/aucdsclnk?sl=91QSCI17083301

I've been doing recon stuff for over a decade and somehow I never knew there was a third P-3 that never flew into a storm nicknamed named Beaker! (Others are nicknamed Kermit and Miss Piggy, with Gonzo being the G-IV) Beaker was N44RF. (Other P-3's are N42RF and N43RF, Gonzo is N49RF)

110



In this thread:

NHC soliciting public comments on changing Reconnaissance Vortex Data Message format for 2018 - Chris in Tampa, 4/26/2017, 8:19 pm

< Return to message board



Post A Reply

Subject:


Message:

Add Smiley:

Add Image (Tutorial):
Image URL:
Add  


Embed Video or other Social Media:
Page URL of YouTube Video: Add
Page URL of Facebook post or image (not image URL): Add
Page URL of Twitter tweet: Add
Page URL of recorded Ustream Video: Add
Page URL of Vine Video: Add
If you prefer to embed something manually for any of these sites, you can also do that. For Ustream, you can only embed live videos manually rather than using the above feature. No other sites are currently supported.

If you embed something manually please be aware that due to the security restrictions on some browsers manually entering embedded code may not allow it to appear correctly when you view it. However, after you post the message it will work properly. This will not be a problem if you use the above feature to add embedded content.