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

[Support #PJP-263468]: FW: Ligtning data



Hi Bryan,

re:
>We get a feed of lightning data here at JSC from Meteorlogix (the NLDN
>feed from Vaisala). We have a local decoder processing this data, but
>found out recently that the strike count may be increasing due to the
>inclusion of cloud-to-cloud and other flash data.

OK.

>We used 1 column per strike per hour in our McIDAS decoder, with a
>limit set at 40,000 per hour.  We have discovered that McIDAS does not
>permit more than 65536 columns in an MD file.

I use one column per flash.  The flashes are not organized into individual
hours by row.  Times increase by columns and wrap around when the maximum
number of columns is reached.  My scheme allows for up to 1 million flashes
per day.

>We were wondering if you are putting your lightning data into MD
>files, and if so, how you handle this limitation.   If you are not
>using an MD file, what storage format are you using?

I am using an MD file, and it is laid out as per my note above.  Here is the
output of the SCHEMA:

% see.k DCNLDN
"       NAME    VSN     DATE    ID      TEXTID
"       ----    ---     ----    --      ------
SCHEMA  NLDN    2       98337   0       "NLDN DATA OBS UNIDATA FORMAT

"KEY    SCALE   UNITS   DESCRIPTION
"---    -----   -----   -----------

ROWS    1000            "1000 ROWS EACH WITH 1000 COLS

DAY             CYD     "YEAR AND JULIAN DAY
TIME            HMS     "TIME OF FIRST OBSERVATION IN ROW
CMAX                    "LAST COLUMN CONTAINING DATA

COLUMNS 1000            "DEFAULT # OF COLS
DATA                    "START OF DATA SECTION

HMS             HMS     "ACTUAL TIME OF OBSERVATION
LAT     4       DEG     "LATITUDE (DECIMAL DEG)
LON     4       DEG     "LONGITUDE (DECIMAL DEG)
SGNL    1               "SIGNAL STRENGTH (150 measures ~ 30 kamps)
MULT                    "MULTIPLICITY

ENDSCHEMA
see.k: Done...EOF Encountered.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: PJP-263468
Department: Support McIDAS
Priority: Normal
Status: Closed


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.