AWIPS LDAD Interface

Notes: Spaces are used to separate the comma-separated values in the samples for readability and are not found in the actual files. In the following format files the descriptions i.e. (nnnn) are only used as an aid in estimating the size of the data records/files. The indication that the value is either a signed integer of signed floating point (i.e. (snn) or (sn.n)) is based on examination of the vendor documentation and in no way does is guarantee that the values that are not listed as signed are not in fact signed values. Again the inclusion of the sign is only used as an aid in estimating the size of the data records/files.

1. Required FTP directory:

The following directory structure must be available on each computer that LDAD data will be FTPed to:

/data/fxa/LDAD/preTmp

/data/fxa/LDAD/FTPdir

Data will be FTPed to /data/fxa/LDAD/FTPdir directory. After the FTP completes the file will be renamed, via FTP, to the /data/fxa/LDAD/preTmp directory. This will insure that the file transfer is complete before the file is available in the /data/fxa/LDAD/preTmp directory.

Note: In the event of a transmission failure a file or files may be left in the /data/fxa/LDAD/FTPdir directory, it is the responsible of the receiving system to clean-up this directory, recommend a cron job to delete all files older than 2 hours in this directory,

This is the only authorized directory structure for Linux/UNIX systems, i.e. the AWIPS data server, the RSA MARSS preprocessor, the Product Distributor, etc.

2. Lightning Data Product Transport

All lightning data products (CGLSS, LLPS, LDAR, LPLWS) are transported via LDM. There are two upstream hosts PPR-1/2 for the lightning data products to the Ingest server and AWIPS Data server, and the FTP server for NASA and PPR3. LDM is available from Unidata http://my.unidata.ucar.edu/content/software/ldm/index.html, we are currently using version 6.0.14. LDM is used to provide a real-time data distribution of the data sets.

3. File Format:

AssetID
DateTime(dd/mm/yyyy hh:mm:ss)
MeasurementID, InstrumentLevel, Measurement, QCFlag
…
MeasurementID, InstrumentLevel, Measurement, QCFlag

The first line of the file contains the AssetID, followed by one line that contains the Date Time record, to be followed by multiple lines of measurements. The definition of these fields follows:

AssetID (integer) (nnnn) Note: This value will be filled with leading zeros so that all values are 4 digits.

DateTime (string) (dd/mm/yyyy hh:mm:ss) – The DateTime is the time associated with the observation (data time).

MeasurementID (integer) (nnnn)

InstrumentLevel (floating point) (nn.n) in meters

Measurement (floating point/Integer/String) type depends on the actual measured value.

QCFlag: 0 - OK, 1 - Out of Range, 2 - Questionable, 3 - Not Tested, 4 – Missing data,

(note: With the addition of the QC flag 4 – Missing data, the ‘M’ will no longer be used. This will insure that all numeric fields will always contain numeric entries.)

[MFFG unique flags, First Guess unchanged, Auto or Manual mode]

5 - MFFG Auto Mode Algorithm good data, 6 - MFFG Manual Mode Algorithm good data Operator no action, 7 - MFFG Auto Mode Algorithm bad data, 8 - MFFG Manual Mode Algorithm bad data Operator no action, 10 - MFFG Manual Mode Algorithm good data Operator flagged as bad data, 12 - MFFG Manual Mode Manual Mode Algorithm bad data Operator flagged as bad data;

[MFFG unique flags, First Guess changed, Manual mode]

14 - MFFG Manual Mode Algorithm good data Operator no action, 16 - MFFG Manual Mode Algorithm bad data Operator no action, 18 - MFFG Manual Mode Algorithm good data Operator flagged as bad data, 20 - MFFG Manual Mode Manual Mode Algorithm bad data Operator flagged as bad data;

Note: If you subtract 8 from these (First Guess changed) values they are the same as the First Guess unchanged flags.

9, 11, 13, 15, 17, and 19 reserved for MFFG but not used.

RTAMPS Edit Flag: 0 – Unedited, 1 – Edited, 3 – Bad. The wind data is flagged with these values x 1, and the thermodynamic data will be flagged with these values x 10. Since there is only one QC flag and both wind and thermodynamic data occur in the same report, the range of values for the RTAMPS Edit Flag is 0 to 33. Examples: 0 both sets are unedited; 10 thermo edited and wind unedited; 30 wind unedited thermo bad; 3 wind bad and thermo unedited.

RTAMPS data and MFFG data are not processed (quality checked) by MARSS.

Note: Mini-Sodar, 915 MHz Profiler, 50 MHz Profiler consensus files, LDAR, LPLWS, and LLP/CGLSS data are the exceptions, in that they support data records, see below. The 50 MHz Profiler MFFG data does follow the single measurement standard.

4. Mini-Sodar

Mini-Sodar

The first line of a Mini-Sodar file contains the AssetID, followed by one line that contains the Date Time record of the data, followed by one line that contains the MeasurementID and the MXHEIGHT, followed by one line that contains the MeasurementID and the UNOISE, followed by one line that contains the MeasurementID and the VNOISE, followed by one line that contains the MeasurementID and the WNOISE, followed by one line that contains the MeasurementID and the NGATES, to be followed by n lines of measurements one for each gate.

File Format:

AssetID

DateTime

MeasurementID, MXHEIGHT

MeasurementID, UNOISE

MeasurementID, VNOISE

MeasurementID, WNOISE

MeasurementID, NGATES

MeasurementID, GateNum, HT, QCFLAG, SPD, QCFLAG, DIR, QCFLAG, GSPD, QCFLAG, GDIR, QCFLAG, W, QCFLAG, SDW, QCFLAG, NW, QCFLAG, IW, QCFLAG, SNRW, QCFLAG, U, QCFLAG, SDU, QCFLAG, NU, QCFLAG, IU, QCFLAG, SNRU, QCFLAG, V, QCFLAG, SDV, QCFLAG, NV, QCFLAG, IV, QCFLAG, SNRV, QCFLAG, SDW5, QCFLAG, SDW10, QCFLAG

…

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

MXHEIGHT – Mixing Height in meters (int) (nnn) [ID 0001]

UNOISE – Noise level of the U measurement in millivolts (int) (nnnn) [ID 0002}

VNOISE – Noise level of the V measurement in millivolts (int) (nnnn) [ID 0003]

WNOISE – Noise level of the W measurement in millivolts (int) (nnnn) [ID 0004]

NGATES – Number of Gates in this file (integer) (nn) [ID 0005]

MeasurementID (integer) (nnnn) in this case 0006 [SodarGateRecord]

GateNum – The number of this gate (integer) (nn)

HT – Sample height in meters (integer) (nnn)

SPD – Speed in meters per second (floating point) (nn.nn)

DIR – Direction in degrees (integer) (nnn)

GSPD – Gust speed in meters per second (floating point) (nn.nn)

GDIR – Gust Direction in degrees (integer) (nnn)

W – Vertical wind component in meters per second (signed floating point) (sn.nn)

SDW – 1 minute Standard deviation of W in meters per second (floating point) (nn.nn)

NW – Number of W observations in the sample (integer) (nn)

IW – Signal return intensity in milivolts (integer) (nnnn)

SNRW – Signal to Noise Ratio of the W component no units (integer) (nnnn)

U – East West wind component in meters per second (signed floating point) (snn.nn)

SDU – Standard deviation of U in meters per second (floating point) (nn.nn)

NU – Number of U observations in the sample (integer) (nn)

IU – Signal return intensity in milivolts (integer) (nnnn)

SNRU – Signal to Noise Ratio of the U component no units (integer) (nnnn)

V – North South wind component in meters per second (signed floating point) (snn.nn)

SDV – Standard deviation of V in meters per second (floating point) (nn.nn)

NV – Number of V observations in the sample (integer) (nn)

IV – Signal return intensity in milivolts (integer) (nnnn)

SNRV – Signal to Noise Ratio of the V component no units (integer) (nnnn)

QCFLAG –QC Flag (integer range 0 to 4) (n)

SDW5 – 5 minute Standard deviation of W in meters per second (floating point) (nn.nn)

SDW10 – 10 minute Standard deviation of W in meters per second (floating point) (nn.nn)

5. Profiler Temperature Consensus Data

Profiler Temperature Consensus Data

The first line of each 50 MHz and 915 MHz Profiler Temperature Consensus file contains the AssetID, followed by one line that contains the Date Time record of the data, followed by one line that contains the MeasurementID and NGATES, followed by n lines of measurements, one for each gate.

File Format:

AssetID

DateTime

MeasurementID, NGATES

MeasurementID, GateNum, HT, QCFLAG, T, QCFLAG, Tc, QCFLAG, W, QCFLAG, SNRT, QCFLAG, SNRTc, QCFLAG, SNRW, QCFLAG, CNT-T, QCFLAG, CNT-Tc, QCFLAG, CNT-W, QCFLAG

…

MeasurementID, GateNum, HT, QCFLAG, T, QCFLAG, Tc, QCFLAG, W, QCFLAG, SNRT, QCFLAG, SNRTc, QCFLAG, SNRW, QCFLAG, CNT-T, QCFLAG, CNT-Tc, QCFLAG, CNT-W, QCFLAG

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

NGATES – Number of Gates in this file (integer) (nn) [ID 2001]

MeasurementID (integer) (nnnn) in this case 2003 [TemperatureGateRecord]

GateNum – The number of this gate (integer) (nn)

HT – Sample height in Kilometers (floating point) (nn.nnn)

T – Temperature in degrees Celsius (signed floating point) (snn.n)

Tc – Corrected Temperature in degrees Celsius (signed floating point) (snn.n)

W - Vertical wind component in meters per second (signed floating point) (snn.n)

SNRT - Signal to Noise Ratio of T in dB (signed integer) (snn)

SNRTc - Signal to Noise Ratio of Tc in dB (signed integer) (snn)

SNRW - Signal to Noise Ratio of the W component in dB (signed integer) (snn)

CNT-T – Number of Temperature observations in this consensus (integer) (nn)

CNT-Tc - Number of Corrected Temperature observations in this consensus (integer) (nn)

CNT-W – Number of W observations in this consensus (integer) (nn)

QCFLAG - QC Flag (integer range 0 to 4) (n)

6. Profiler Wind Consensus Data

Profiler Wind Consensus Data

The first line of each 50 MHz and 915 MHz Profiler wind consensus file contains the AssetID, followed by one line that contains the Date Time record of the data, followed by one line that contains the MeasurementID, NGATES, followed by one line that contains the MeasurementID, NRADIALS, followed by n lines of measurements, one for each gate.

Even though data elements are shown for the maximum number of radials (beams) the data records will only be populated for the number of radials indicated by NRADIALS.

For example if NRADIALS = 2 then the AZ/EL measurement will be in the form:

2013, AZ-1, EL-1, AZ-2, EL-2

File Format:

AssetID

DateTime

MeasurementID, NGATES

MeasurementID, NRADIALS

MeasurementID, AZ-1, EL-1, AZ-2, EL-2, AZ-3, EL-3, AZ-4, EL-4, AZ-5, EL-5

MeasurementID, GateNum, HT, QCFLAG, SPD, QCFLAG, DIR, QCFLAG, VEL-1, QCFLAG, OBS-1, QCFLAG, SNR-1, QCFLAG, VEL-2, QCFLAG, OBS-2, QCFLAG, SNR-2, QCFLAG, VEL-3, QCFLAG, OBS-3, QCFLAG, SNR-3, QCFLAG, VEL-4, QCFLAG, OBS-4, QCFLAG, SNR-4, QCFLAG, VEL-5, QCFLAG, OBS-5, QCFLAG, SNR-5, QCFLAG

…

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

NGATES – Number of Gates in this file (integer) (nnn) [ID 2003]

NRADIALS – Number of Radials (beams) in each of the gates (integer) (n) [ID 2004]

MeasurementID (integer) (nnnn) in this case 2014 [WindAzEl]

AZ-1 … AZ-5 – Azimuth of radial (beam) 1 – 5 (float) (nnn.n)

EL-1 … EL-5 – Elevation of radial (beam) 1 – 5 (float) (nn.n)

MeasurementID (integer) (nnnn) in this case 2005 [WindGateRecord]

GateNum – The number of this gate (integer) (nnn)

HT – Sample height in Kilometers (floating point) (nnn.nnn)

SPD – Sample speed in meters per second (floating point) (nn.n)

DIR – Sample direction in degrees (integer) (nnn)

VEL-1 – Velocity of radial (beam) 1 in meters per second (signed floating point) (snn.n)

OBS-1 – Number of observations in the radial (beam) 1 consensus (integer) (nn)

SNR-1 – Signal to Noise Ratio of radial (beam) 1 in dB (signed integer) (snn)

VEL-2 – Velocity of radial (beam) 2 in meters per second (signed floating point) (snn.n)

OBS-2 – Number of observations in the radial (beam) 2 consensus (integer) (nn)

SNR-2 – Signal to Noise Ratio of radial (beam) 2 in dB (signed integer) (snn)

VEL-3 – Velocity of radial (beam) 3 in meters per second (signed floating point) (snn.n)

OBS-3 – Number of observations in the radial (beam) 3 consensus (integer) (nn)

SNR-3 – Signal to Noise Ratio of radial (beam) 3 in dB (integer) (snn)

VEL-4 – Velocity of radial (beam) 4 in meters per second (signed floating point) (snn.n)

OBS-4 – Number of observations in the radial (beam) 4 consensus (integer) (nn)

SNR-4 – Signal to Noise Ratio of radial (beam) 4 in dB (integer) (snn)

VEL-5 – Velocity of radial (beam) 5 in meters per second (signed floating point) (snn.n)

OBS-5 – Number of observations in the radial (beam) 5 consensus (integer) (nn)

SNR-5 - Signal to Noise Ratio of radial (beam) 5 in dB (integer) (snn)

QCFLAG - QC Flag (integer range 0 to 4) (n)

7. LDAR Data Record

LDAR Data Record

The first line of each LDAR contains the AssetID, followed by one line that contains the Date Time record of the bin (the time of the first measurement) and the bin length (in seconds), to be followed by n lines of measurements (events).

File Format:

AssetID

DateTime, BinLength

MeasurementID, EventTime, X measurement, Y measurement, Z measurement

…

MeasurementID, EventTime, X measurement, Y measurement, Z measurement

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

BinLength (integer) (seconds, range 0 to 999) (nnn) 0 indicates no data heartbeat only

Each measurement has the following format:

MeasurementID, EventTime, X measurement, Y measurement, Z measurement

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 0500 [LdarDataRecord]

EventTime (string) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

X, Y, Z measurements (location in meters (integer) from the central site) (nnnnn)

8. LPLWS Data Records

LPLWS Data Records

Three data sets are produced by the LPLWS system: Field Mill Grid data, Field Mill Value Table data, and Field Mill Center of Charge data.

Field Mill Grid Data

The first line of each LPLWS Field Mill Grid file contains the AssetID, followed by one line that contains the Date Time record of the product (produced at a 5 minute rate) followed by a line which contains the number of rows followed by a line which contains the number of columns, to be followed by n lines of measurements.

File Format:

AssetID

DateTime

MeasurementID, NumRows

MeasurementID, NumColumns

MeasurementID, LatOfOrigin, LonOfOrigin

MeasurementID, Xspacing

MeasurementID, Yspacing

MeasurementID, RowNum, ColVal-1, ColVal-2, …, ColVal-<NumColumns>

…

MeasurementID, RowNum, ColVal-1, ColVal-2, …, ColVal-<NumColumns>

The definition of these fields follows:

AssetID (integer) (nnnn) in this case 350

DateTime (string) (dd/mm/yyyy hh:mm:ss) [measurement time]

MeasurementID (integer) (nnnn) in this case 1053 [NumRows]

NumRows - Number of rows in the grid

MeasurementID (integer) (nnnn) in this case 1054 [NumColumns]

NumColumns - Number of columns in the grid

MeasurementID (integer) (nnnn) in this case 1056 [GridOriginRecord]

LatOfOrigin (signed floating point) (snn.nnnnnn, degrees) +North reference frame.

LonOfOrigin (signed floating point) (snnn.nnnnnn, degrees) +East reference frame.

Note: The origin is the North West (upper left) corner of the grid

MeasurementID (integer) (nnnn) in this case 1057 [Xspacing]

Xspacing (int) (feet)

MeasurementID (integer) (nnnn) in this case 1058 [Yspacing]

Yspacing (int) (feet)

Each row has the following format:

MeasurementID (integer) (nnnn) in this case 1052 [GridDataRecord]

RowNum - The current row number 1 to NumRows

ColVal (signed int) (nnnnn, Volts/m) [one value for each column 1 to NumColumns]

9. Field Mill Value Table Data

Field Mill Value Table Data

The first line of each LPLWS Field Mill Value Table file contains the AssetID, followed by one line that contains the Date Time record of the product (produced at a 1 minute rate) followed by a line that contains the number of Field Mills included in this file, to be followed by n lines of measurements one for each Field Mill. If the Field Mill did not report there will be no entry for the instrument in the current sample period.

File Format:

AssetID

DateTime

MeasurementID, NumMills

MeasurementID, MillAssetId, Value, QCFLAG

…

MeasurementID, MillAssetId, Value, QCFLAG

The definition of these fields follows:

AssetID (integer) (nnnn) in this case 350

DateTime (string) (dd/mm/yyyy hh:mm:ss) [measurement time]

MeasurementID (integer) (nnnn) in this case 1055 [NumMills]

NumMills (integer) (range 0 to 99) (nn) The number of Field Mill observations in the file

Each measurement has the following format:

MeasurementID (integer) (nnnn) in this case 1050 [ValueDataRecord]

MillAssetId (integer) (nnn) The asset ID for the Field Mill Sensor (301 to 349)

Value (signed int) (nnnnn, Volts/m)

QCFLAG – (integer)(n) (0, 1 or 4)

According to page B-3 of the LPLWS-IDD007-051697, there are three possible status characters:

   ' ' = OK          mapped to 0 – OK
   '*' = invalid     mapped to 1 – Out of Range
   'X' = inactive    mapped to 4 – Missing data

10. Field Mill Center of Charge Data

Field Mill Center of Charge Data

The first line of each LPLWS Center of Charge (flash data) file contains the AssetID, followed by one line that contains the Date Time record of the bin (the time of the first measurement) and the bin length (in seconds), to be followed by n lines of measurements (events).

File Format:

AssetID

DateTime, BinLength

MeasurementID, EventTime, Latitude, Longitude

…

MeasurementID, EventTime, Latitude, Longitude

The definition of these fields follows:

AssetID (integer) (nnn) in this case 350

DateTime (string) (dd/mm/yyyy hh:mm:ss)

BinLength (integer) (seconds, range 0 to 999) (nnn) 0 indicates no data heartbeat only

Each measurement has the following format:

MeasurementID, EventTime, Latitude, Longitude

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 1051 [CenterOfChargeRecord]

EventTime (integer) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

Latitude (signed floating point) (snn.nnnnnn, degrees) +North reference frame.

Longitude (signed floating point) (snnn.nnnnnn, degrees) +East reference frame.

11. CGLSS Data Record

CGLSS Data Record

The first line of the CGLSS file contains the AssetID, followed by one line that contains the Date Time record of the bin (the time of the first measurement) and the bin length (in seconds), to be followed by n lines of measurements (events).

Example File:

AssetID

DateTime, BinLength

MeasurementID, EventTime, Latitude, Longitude, Strength, ReturnStrokes

…

MeasurementID, EventTime, Latitude, Longitude, Strength, ReturnStrokes

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

BinLength (integer) (seconds, range 0 to 999) (nnn) 0 indicates no data heartbeat only

Each measurement has the following format:

MeasurementID, EventTime, Latitude, Longitude, Strength, ReturnStrokes

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 2021 [CglssDataRecord]

EventTime (string) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

Latitude (floating point) (snnn.nnnnn, degrees) +North reference frame.

Longitude (floating point) (snnn.nnnnn, degrees) +East reference frame.

Strength in kilo Amps (signed integer) (snnn)

ReturnStrokes (integer) (nn) the value –99 shall be used to indicate missing data.

12. LLPS Data Record

LLPS Data Record

The first line of the LLPS file contains the AssetID, followed by one line that contains the Date Time record of the bin (the time of the first measurement) and the bin length (in seconds), to be followed by a line of CGLSS data followed by a line of LLPS data repeated n times for each of the measurements (events). Each of the line pairs will have the identical EventTime so that the LLPS extension to the basic CGLSS measurement can be correlated.

Example File:

AssetID

DateTime, BinLength

MeasurementID, EventTime, Latitude, Longitude, Strength, ReturnStrokes

MeasurementID, EventTime, CloudIndicator, ChiSquare, BearingAngle, SemiMajorAxis, SemiMinorAxis

…

MeasurementID, EventTime, Latitude, Longitude, Strength, ReturnStrokes

MeasurementID, EventTime, CloudIndicator, ChiSquare, BearingAngle, SemiMajorAxis, SemiMinorAxis

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

BinLength (integer) (seconds, range 0 to 999) (nnn) 0 indicates no data heartbeat only

Each measurement has the following format:

MeasurementID, EventTime, Latitude, Longitude, Strength, ReturnStrokes

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 2021 [CGLSS data record]

EventTime (string) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

Latitude (floating point) (snnn.nnnnn) +North reference frame.

Longitude (floating point) (snnn.nnnnn) +East reference frame.

Strength in kilo Amps (signed integer –9999 to 9999) (snnnn)

ReturnStrokes (integer 0 to 99) (nn) <new line>

MeasurementID, EventTime, CloudIndicator, ChiSquare, BearingAngle, SemiMajorAxis, SemiMinorAxis

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 2020 [LLPS data record]

EventTime (string) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

CloudIndicator (integer 0 or 1, 0 = cloud, 1 = cloud-ground) (n)

ChiSquare (float 0 to 999.99) (nnn.nn)

BearingAngle (float 0 to 180.0 degrees from North) (nnn.n)

SemiMajorAxis (float 0 to 50.0 km) (nn.n)

SemiMinorAxis (float 0 to 50.0 km) (nn.n)

13. 4DLSS Data Record (Proposed)

4DLSS Data Record

The first line of the 4DLSS file contains the AssetID, followed by one line that contains the Date Time record of the bin (the time of the first measurement) and the bin length (in seconds), to be followed by a line of CGLSS data followed by a line of LLPS data repeated n times for each of the measurements (events). Each of the line pairs will have the identical EventTime so that the LLPS extension to the basic CGLSS measurement can be correlated.

Example File:

AssetID

DateTime, BinLength

MeasurementID, EventTime, Latitude, Longitude, Elevation, Strength, ReturnStrokes

MeasurementID, EventTime, CloudIndicator, ChiSquare, BearingAngle, SemiMajorAxis, SemiMinorAxis

…

MeasurementID, EventTime, Latitude, Longitude, Elevation, Strength, ReturnStrokes

MeasurementID, EventTime, CloudIndicator, ChiSquare, BearingAngle, SemiMajorAxis, SemiMinorAxis

The definition of these fields follows:

AssetID (integer) (nnnn)

DateTime (string) (dd/mm/yyyy hh:mm:ss)

BinLength (integer) (seconds, range 0 to 999) (nnn) 0 indicates no data heartbeat only

Each measurement has the following format:

MeasurementID, EventTime, Latitude, Longitude, Elevation, Strength, ReturnStrokes

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 2024 [4DLSS data record 1]

EventTime (string) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

Latitude (floating point) (snnn.nnnnn) +North reference frame.

Longitude (floating point) (snnn.nnnnn) +East reference frame.

Elevation in meters (floating point)

Strength in kilo Amps (signed integer –9999 to 9999) (snnnn)

ReturnStrokes (integer 0 to 99) (nn) <new line>

MeasurementID, EventTime, CloudIndicator, ChiSquare, BearingAngle, SemiMajorAxis, SemiMinorAxis

The definition of these fields follows:

MeasurementID (integer) (nnnn) in this case 2025 [4DLSS data record 2, identical to measurement 2020]

EventTime (string) (ddd hh:mm:ss.ssssss) Where ddd is the Julian date of the measurement.

CloudIndicator (integer 0 or 1, 0 = cloud, 1 = cloud-ground) (n)

ChiSquare (float 0 to 999.99) (nnn.nn)

BearingAngle (float 0 to 180.0 degrees from North) (nnn.n)

SemiMajorAxis (float 0 to 50.0 km) (nn.n)

SemiMinorAxis (float 0 to 50.0 km) (nn.n)

14. MARSS LAPS Data

The directories containing the LAPS analysis files are physically on the AWIPS data server:

/data/fxa/Grid/FSL/netCDF/LAPS_Grid/LAPS01 -> 10km files

/data/fxa/Grid/FSL/netCDF/LAPS_Grid/LAPS02 -> 3.3km files

/data/fxa/Grid/FSL/netCDF/LAPS_Grid/LAPS03 -> 1.1km files

15. MARSS MM5 Data

The forecast files are physically on the models cluster in these subdirectories:

/data/local/XXX/LAPS01/lapsprd/fsf/mm5 -> 10km surface forecasts

/data/local/XXX/LAPS01/lapsprd/fua/mm5 -> 10km upper-air forecasts

/data/local/XXX/LAPS02/lapsprd/fsf/mm5 -> 3.3km surface forecasts

/data/local/XXX/LAPS02/lapsprd/fua/mm5 -> 3.3km upper-air for

/data/local/XXX/LAPS03/lapsprd/fsf/mm5 -> 1.1km surface forecasts

/data/local/XXX/LAPS03/lapsprd/fua/mm5 -> 1.1km upper-air forecasts

Where XXX is either KSC or VDB for the eastern and western ranges, respectively.

16. EditMet Data

FTP the Editmet output files to the MARSS ppro1, ppro2, ppro3 in the /data/fxa/editmet directory. Stage the output files in /data/fxa/LDAD/FTPdir first.

17. File Naming Convention

The file naming convention is as follows:

TypeName.AssetID.datetime.csv - The datetime is the time associated with the observation (data time).

AssetID (integer) (nnnn)

datetime (string) (yyyymmddhhmmss)

Note: For RemoteObs the file extension will be metar verses csv.

For the WSR-74C image files the file extension will be tif verses csv.

TypeName	Data Type
Mini-SODAR	Mini-Sodar (DASS)
50ProfilerTempCNS	50 MHz profiler temperature consensus file data.
50ProfilerWindCNS	50 MHz profiler wind consensus file data.
915ProfilerTempCNS	915 MHz profiler temperature consensus file data.
915ProfilerWindCNS	915 MHz profiler wind consensus file data.
50ProfilerMFFG	50 MHz MFFG data
Asos	Airfield sensor data
MetTower	Met tower data
LLPS	LLPS lightning data (WR only)
CGLSS	CGLSS lightning data (ER only)
LPLWS-CC	Launch Pad Lightning Warning System (Field Mill) data – Center of Charge data
LPLWS-Grid	Launch Pad Lightning Warning System (Field Mill) data - Field Mill Grid data
LPLWS-FMVT	Launch Pad Lightning Warning System (Field Mill) data - Field Mill Value Table data
LDAR	Lightning Detection and Ranging System
RemoteObs	Manually entered surface observations at various range locations encoded in METAR format
4DLSS	Reserved for the SLRSC lightning system upgrade at the ER

The datetime will represent the time of the data observation.

Table 2 illustrates the relationship between ASSET_ID, ASSET_TYPE and ASSET_NM (Asset Name) for the Western Range and Table 3 illustrates the relationship for the Eastern Range.

6/26/01: The RTAMPS interface is BUFR encoded files.

The following is an extract from the RTAMPS Interface Document, version 3e, dated 18 June 2001. This document is maintained by SMC/CWV.

18. WSR-74C File Naming Convention

The naming convention is:

<hostname><YY><MM><DD><hh><mm><ss>.<Product><number>.tif

hostname: 6 characters representing the hostname of the computer that generated the product. Currently it is rwowsr.

YY:	2 digit year
MM:	2 digit month
DD:	2 digit day of month
hh:	2 digit hour of product in Zulu
mm:	2 digit minute of product in Zulu
ss:	2 digit seconds of product in Zulu
Product:	3 characters representing the type of product. Currently they are CAP, MAX, VIL, and VHR.
number:	4 digits sequence number

Example:

rwowsr050218162444.MAX0625.tif

19. RTAMPS File Naming Convention

Generic Filename

RTAMPS_N_ID1_ID2_YYYY_MM_DD_HH_MM_SS.bufr

RTAMPS_N_ID1_ID2_YYYY_MM_DD_HH_MM_SS.txt (see Note, below)

Example Filename

RTAMPS_72393_W12345H04522O1C_BIG5_2000_09_18_09_32_10.bufr
RTAMPS_72393_W12345H04522O1C_BIG5_2000_09_18_09_32_10.txt
       |___| |_____________| |__|
         N         ID1       ID2

(see Note, below)

File Name Field Description

“N” is the standard World Meteorological Organization assigned station identifier. In the case of the Western Range (KVBG) Balloon Release Facility this code is 72393. For the Eastern Range (KXMR) Balloon Release Facility this code is 74794. And for the Ascension (FHAW) Balloon Release Facility this code is 61902.

“ID1” is a fifteen-character field with the following characters:

Character	Options	Meaning
1-6		Six alphanumeric characters representing the operation number associated with this particular balloon flight.
7	H or L	Represents High or Low Resolution data
8-11	0001-9999	Four-digits representing the balloon release number for that year.
12	1 - 6	The specific AMPS SPS through which data was processed.
13	O or R or 1 - 9	One character representing the transmission iteration from AMPS. “O” is an original transmission from AMPS. “R” represents data that has been replayed from AMPS. Note that there is no feature within AMPS to uniquely identify data that has been replayed more than once. 1 – 9 indicate that this is the re-edit (1-9) of a previously released mission.
14	1 - 6	The AMPS/RTAMPS System Identifier 1 is WR #1 2 is WR #2 3 is ER #1 4 is ER #2 5 is Ascension #1 6 is Ascension #2
15	A - O	One alphanumeric character representing the balloon type used on this particular balloon flight. Specific balloon designations are: A - Latex 300g B - Latex 600g C - Latex 800g D - Latex 1000g E - Latex 1200g F - Stabilized 350g G - Stabilized 800g H - Stabilized 1000g I - Stabilized 1200g J - Clear Jimsphere O - Other

“ID2” is a four character alphanumeric field that can be:

Options	Meaning
005k, 010k, etc.	Partial files. The elevation shown represents the highest elevation reported within that file. Note that this highest elevation is approximate and may be higher than stated. The actual height reported within a given file is dependent on the quality of data at the maximum required reporting height for that segment. If the last point(s) within that segment are bad, RTAMPS will continue collecting data until acceptable data is obtained.
BIGx	Full files. The “x” is the 1-9^th archive file with “9” always being the final archive file. This includes the case where no archives were selected (first and only file will be “BIG9”).
RAOB	RAwinsonde OBservation (in synoptic file format) based on the BIG9 file.
ROBn	RAwinsonde OBservation (in synoptic file format) where n = 0 to 9, that are produced before the termination of the flight. ROB0 is always the 100mb observation.

“YYYY” is the year. “MM” is the month. “DD” is the day. “HH” is the hour. “MM” is the minute. “SS” is the second. All dates and times are based on Universal Coordinated Time (UTC). Time is the moment of first balloon motion as detected and reported by AMPS.

Note: Files with the suffix “*.txt” are in ASCII format and are generated only for internal RSA use prior to releasing the data to customers. Customers will use those files with the “*.bufr” suffix and should never see files with the “*.txt” suffix.

20. Table 1 – Measurement IDs

Table 1

Measurement ID (WDP_ID)	Measurement Name (WDP_NM)	Description (WDP_DESC)	Unit of Measure (UOM_CD)
	Mini-Sodar
1	sodar_MXHEIGHT		m
2	sodar_UNOISE		dB
3	sodar_VNOISE		dB
4	sodar_WNOISE		dB
5	sodar_NGATES		none
6	sodar_Gate_Record		See note
	LDAR
500	LDAR_data_record		See note
	ASOS
1000	asos_sky_condition_report		ASCII
1001	asos_visibility		S mi
1002	asos_tower_visibility		S mi
1003	asos_present_weather		ASCII
1004	asos_urgent_weather		ASCII
1005	asos_sea_level_pressure		mb
1007	asos_dew_point		F
1008	asos_relative_humidity		%
1009	asos_wind_direction		deg
1010	asos_wind_speed		kt
1011	asos_magnetic_wind_direction		deg
1012	asos_magnetic_wind_speed		kt
1013	asos_altimeter_pressure_setting		inHg
1014	asos_density_altitude		ft
1015	asos_pressure_altitude		ft
1016	asos_remark		ASCII
1018	asos_rain_rate	Note: 0 to 10” per hour	in/hr
1020	asos_temperature		F
	LPLWS
1050	Lplws_FM_value_data_record		See note
1051	Lplws_FM_center_of_charge_data_record		See note
1052	Lplws_FM_grid_data_record		See note
1053	Lplws_FM_NumRows	Number of rows in the grid	N/A
1054	Lplws_FM_NumColumns	Number of columns in the grid	N/A
1055	Lplws_FM_NumMills	Number of Field Mill sensors	N/A
1056	Lplws_FM_Grid_Origin_Record	Lat/Lon of the origin
1057	Lplws_FM_Grid_X_spacing		ft
1058	Lplws_FM_Grid_Y_spacing		ft
	915 MHz Profiler
2001	profiler_915_ Temperature _NGATES		N/A
2002	profiler_915_Temperature_Gate_Record	Consensus file data	See note
2003	profiler_915_Wind_NGATES		N/A
2004	profiler_915_Wind_NRADIALS		N/A
2005	profiler_915_Wind_Gate_Record	Consensus file data	See note
2014	Profiler_915_Wind_AZ-EL		degrees
	50 MHz Profiler
2006	profiler_50_MFFG_wind_speed		kt
2007	profiler_50_MFFG_wind_direction		deg
2008	profiler_50_ Temperature _NGATES		N/A
2009	profiler_50_Temperature_Gate_Record	Consensus file data	See note
2010	profiler_50_Wind_NGATES		N/A
2011	profiler_50_Wind_NRADIALS		N/A
2012	profiler_50_Wind_Gate_Record	Consensus file data	See note
2013	Profiler_50_Wind_AZ-EL		degrees
	LLP
2020	llps_data_record		See note
2021	cglss_data_record		See note
2024	4dlss_data_record_1		See note
2025	4dlss_data_record_2		See note
	Met Towers	Tower Ingest Codes
2070	tower_wind_ave_x (1 min ave)	2070(n) / 2071(s)	N/A
2072	tower_ave_temp_1_min	2072(n) / 2172(s)	C
2076	tower_ave_rel_hum_1_min	2076(n) / 2176(s)	%
2080	tower_ave_wind_speed_1_min	2080(n) / 2180(s)	m/s
2084	tower_ave_wind_dir_1_min	2084(n) / 2184(s)	deg
2088	tower_ave_gust_speed_1_min	2088(n) / 2188(s)	m/s
2092	tower_ave_gust_dir_1_min	2092(n) / 2192(s)	deg
2100	tower_ave_net_radiation_1_min	2100	W/m2
2112	tower_wind_ave_y (1 min ave)	2112(n) / 2113(s)	N/A
2104	tower_ave_soil_moisture_1_min	2104	%
2105	tower_10_minute_sigma_theta	2105	deg
2106	tower_30_minute_sigma_theta	2106	deg
2107	tower_60_minute_sigma_theta	2107	deg
2108	tower_5_minute_mean_speed	2108	m/s
2109	tower_10_minute_mean_speed	2109	m/s
2110	tower_5_minute_mean_direction	2110	deg
2111	tower_10_minute_mean_direction	2111	deg
2212	tower_barometric_pressue	2212 NOTE: Included for future sensor addition.	Pa
2300	tower_rain_rate_1_min	2300	mm/min
2301	tower_dewpoint_temperature_1_min	2301	C

Unit Of Measure	Description
W/m2	Watts per meter^2
F	degrees Fahrenheit
C	degrees Celsius
K	degrees Kelvin
%	percent
kt	knots
deg	degrees 0-360
Pa	Pascal
m	meters
m/s	meters per second
ft	feet
dB	decibels
mm	millimeter
mi	miles
S mi	Statute miles
N/A	Not Applicable

Notes:	We will only send North side codes. We will select either the North or South side to be sent. Barometric pressure is not currently sent from the towers. All lightning products are defined as data records not discrete measurements. The mini-Sodar and Profiler data sets also contain embedded data records. The tower sigma theta is the 1,5 or 10-minute standard deviation of the wind direction in degrees.

21. Table 2 - Western Range Assets

Table 3

Western Range Assets

ASSET_ID	ASSET_TYPE	FMT Number	ASSET_NM		AWIPS Display Name	ASSET_LAT	ASSET_LON	ASSET_HT (MSL Height in Ft.)
68	MET_TOWER	2	Tower_75			34.7327	-120.5338	460.21
69	MET_TOWER	2	Tower_72			34.8255	-120.5084	915.76
70	MET_TOWER	2	Tower_77			34.6086	-120.5252	1443.87
72	MET_TOWER	5	Tower_70			34.8824	-120.6368	88.03
73	MET_TOWER	5	Tower_71			34.8450	-120.5825	305.74
74	MET_TOWER	2	Tower_76			34.6073	-120.4645	309.31
75	MET_TOWER	2	Tower_51			34.7099	-120.5652	402.97
77	MET_TOWER	2	Tower_81			34.5566	-120.6119	89.85
78	MET_TOWER	10	Tower_54			34.6421	-120.5912	460.78
80	MET_TOWER	2	Tower_80			34.5825	-120.5620	2119.60
81	MET_TOWER	2	Tower_57			34.6669	-120.5893	296.19
82	MET_TOWER	2	Tower_58			34.6971	-120.5380	375.69
83	MET_TOWER	2	Tower_59			34.8021	-120.5810	225.99
84	MET_TOWER	4	Tower_60			34.8497	-120.5992	120.90
85	MET_TOWER	2	Tower_61			34.6424	-120.5557	505.08
86	MET_TOWER	2	Tower_64			34.6137	-120.5509	1202.22
87	MET_TOWER	11	Tower_65			34.5664	-120.4998	2055.48
88	MET_TOWER	2	Tower_66			34.6650	-120.5548	28.25
89	MET_TOWER	12	Tower_102			34.7582	-120.6216	217.01
91	MET_TOWER	13	Tower_300			34.6337	-120.6139	389.67
92	MET_TOWER	13	Tower_301			34.5801	-120.6325	384.65
93	MET_TOWER	4	Tower_74			34.7401	-120.6195	64.18
94	MET_TOWER	5	Tower_78			34.6009	-120.6292	346.88
95	MET_TOWER	2	Tower_79			34.5871	-120.5951	1540.76
96	MET_TOWER	3	Tower_73			34.7687	-120.5346	488.81
97	MET_TOWER	2	Tower_5			34.7535	-120.5711	330.0
410	LLPS	N/A	WR_ALDF_1			34.8772	-120.6264	360.40
411	LLPS	N/A	WR_ALDF_2			34.8969	-120.4525	238.12
412	LLPS	N/A	WR_ALDF_3			34.5572	-120.6117	97.76
413	LLPS	N/A	WR_ALDF_4			34.5306	-119.9861	4112.20
414	LLPS	N/A	LLPS data products			0	0	0
423	AMPS	N/A	AMPS_N_VAFB-1			34.7546	-120.5711	328.00
424	AMPS	N/A	AMPS_N_VAFB-2			34.7546	-120.5711	328.00
505	915MHz PROFILER	N/A	915_LF06		LF-06	34.8821	-120.6368	84.75
506	915MHz PROFILER	N/A	915_LF03		LF-03	34.8466	-120.5811	298.23
507	915MHz PROFILER	N/A	915_SLC2		SLC-2	34.7585	-120.6243	163.71
508	915MHz PROFILER	N/A	915_WST		WSIS	34.7689	-120.5341	493.35
509	915MHz PROFILER	N/A	915_SLC4		SLC-4	34.6358	-120.6162	308.89
510	915MHz PROFILER	N/A	915_DIOSA		Diosa Rd.	34.6005	-120.6292	348.70
				editmet ID
518	MINI-SODAR	N/A	DASS_LF06	DAS0	LF-06	34.8821	-120.6368	84.75
519	MINI-SODAR	N/A	DASS_LF03	DAS1	LF-03	34.8466	-120.5811	298.23
520	MINI-SODAR	N/A	DASS_SLC2	DAS2	SLC-2	34.7585	-120.6243	163.71
521	MINI-SODAR	N/A	DASS_WST	DAS3	WSIS	34.7689	-120.5341	493.35
522	MINI-SODAR	N/A	DASS_SLC4	DAS4	SLC-4	34.6358	-120.6162	308.89
523	MINI-SODAR	N/A	DASS_DIOSA	DAS5	Diosa Rd.	34.6005	-120.6292	348.70
525	50MHz PROFILER	N/A	50MHz_Profiler			34.7832	-120.5730	132.90
602	ASOS	N/A	ASOS_AIRFLD		Airfield	34.7275	-120.5781	326.75
603	ASOS	N/A	ASOS_SLC4		SLC-4	34.6358	-120.6161	306.87
604	ASOS	N/A	ASOS_MM		Minuteman	34.8456	-120.5814	301.20
~~760~~	~~RemoteObs~~	~~N/A~~	~~VAFB airfield observations~~		~~AF_OBS~~	~~34.7345~~	~~-120.5694~~	~~420.77~~

	Note: Latitude is defined as +N, Longitude is defined as +E.
	Tower Station Names: Tower_XX = Tower XX		<