[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GEMPAK #HFP-442517]: Problem decoding TOR/SVR from previous month

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [GEMPAK #HFP-442517]: Problem decoding TOR/SVR from previous month
  • Date: Fri, 18 Jul 2008 13:35:27 -0600
Hi Dan-

> Ok that helps, I see that if I use the "current" time, it ends up
> decoded into the proper YYYYMMDDHH_warn.gem file. I modified my program
> to strip the VTEC start time from the warning and use that as the
> "current" time, so far so good. 

Glad that works for you.

> Also, I was wondering if you could tell me if there is a gempak program
> that will decode SVS statements that are used to update TOR/SVR
> warnings. SVS's also have polygon coordinates and with the advent of
> polygon warnings, they seem to be used more and more to cancel portions
> of counties while leaving other portions intact. Using dcwarn to decode
> the initial coordinates of the warning is great, but is there a way I
> can continue to keep track of the warning as it progresses through time?

There is no decoder for the SVS statements that I see.  Sorry.

Don Murray

Ticket Details
===================
Ticket ID: HFP-442517
Department: Support GEMPAK
Priority: Normal
Status: Open