**Volpe Center Acoustics Facility - Preferred Data File Formats**

To expedite Volpe Center validation of Certification processes,
applicants are encouraged to provide the required input data sets in the
Volpe Center's preferred data formats. All files should be MS-DOS ASCII
format, supplied on high-density 3.5" floppy disk. Each line should be
terminated with a linefeed/carriage-return combination, No tabs or other
formatting characters should be used. Specifications for these formats
follow:

**1. Raw, Third-Octave Spectral Time-Histories**

> Raw spectra, as output by the analyzer. File-naming convention:
> "**xxxx.SPC**". ("xxxx" = Event ID, up to 4 characters.) A separate
> file for each event is required. Events should be grouped in
> subdirectories by microphone site.

**Two-line header:**

[First line]{.underline} - FORTRAN format
(A1,2X,F7.5,1X,I2,1X,I2,1X,F6.3,4X,,F7.5):

1-Analysis averaging method. "L" for linear, "E" for exponential.

2 - Record length, SECONDS. ("0.5000" for half-second records.)

3 - Start time-of-day, HOUR

4 - Start time-of-day, MINUTE

5 - Start time-of-day, SECOND

6 - Dummy value -not used- set to "0.00000".

[Second line]{.underline} - FORTRAN format

(4X,F4.2,4X,F4.2,2X,I2,1X,I3):

1 - Dummy value - not used - set to "0.00".

2 - Dummy value - not used - set to "0.00".

3 - \# of first analysis record in file. (Usually "1")

4 - \# of last analysis record in file.

**Analysis records:**

Each represents a one-third-octave spectrum as generated by analyzer. 5
lines.

[First line]{.underline} - FORTRAN format (I3,2X,I2):

1 - Analysis record number

2 - "40" - ANSI band number of highest-frequency third-octave band in
analysis record. (See Table 1.)

[Second line]{.underline} - FORTRAN format (11(1X,F6.2)):

1-11 - Dummy values - not used - set to "0.00".

[Third line]{.underline} - (Same FORTRAN format as previous line):

1- 4 - Dummy values - not used - set to "0.00".

5 - 11 - Third-octave SPLs for ANSI bands 17-23

[Fourth line]{.underline} - (Same FORTRAN format as previous line):

1-11 - Third-octave SPLs for ANSI bands 24-34

[Fifth line]{.underline} - (Same FORTRAN format as previous line):

1-6 - Third-octave SPLs for ANSI bands 35-40

7-11 - Dummy values - not used - set to "0.00".

**2. General measurement & analysis information**

> Two files are used for general information about data contained in a
> single directory.
>
> **"INDEX":**

**12-line header:**

[First line]{.underline} - FORTRAN format (A50):

1- Directory name

[Second line]{.underline} - FORTRAN format (I2,1X,I2,1X,I2):

1 - Measurement date, MONTH

2 - Measurement date, DAY

3 - Measurement date, YEAR

[Third line]{.underline} - FORTRAN format (I2,1X,I2):

1 - General start time for measurements, HOUR

2 - General start time for measurements, MINUTE

[Fourth line]{.underline} - FORTRAN format (A50):

1 - Measurement site name

[Fifth line]{.underline} - FORTRAN format (I2,1X,I2,1X,I2):

1 - Analysis date, MONTH

2 - Analysis date, DAY

3 - Analysis date, YEAR

[Sixth line]{.underline} - FORTRAN format (I2,1X,I2,1X,I2):

1 - Analysis start time for directory, HOUR

2 - Analysis start time for directory, MINUTE

3 - Analysis start time for directory, SECOND

[Seventh line]{.underline} - FORTRAN format (I1,1X,I1,1X,I1):

1 - Analysis code, "9"

2 - Recorder code, "0" - Analog, "1" - Digital, "2" - FM

3 - Recorder channel \#

[Eighth line]{.underline} - FORTRAN format (F6.3,1X,F7.4,1X,A1):

1 - "2.000" - Number of analysis records per second

2 - Averaging time, SECONDS ( ".5000" for linear half-second
integrations, "2.0000" for slow-scale exponential averaging.)

3 - Averaging method code, "L" - linear, "E" - exponential

[Ninth line]{.underline} - FORTRAN format (F9.2):

1 - Calibrator nominal output level, dB SPL

[Tenth line]{.underline} - FORTRAN format (A50):

1 - Optional comment field

[Eleventh line]{.underline} - FORTRAN format (I3):

1 - Microphone number

[Twelfth line]{.underline} - FORTRAN format (F8.2):

1 - Microphone Y co-ordinate re: Centerline, FEET (See Figure 1.)

**Event records:**

[Each line]{.underline} - FORTRAN format
(A4,17X,I3,1X,F5.2,F6.2,1X,F5.2,1X,I2,I3):

1 - Event ID

2 - Number of Analysis records in .SPC file. (See Item #1)

3 - Delta Gain, dB (Only for gain not accounted for in analyzer
calibration. Note that a positive gain value will be
[subtracted]{.underline} from SPL values during processing .)

4 - Calibration analysis setting, dB (Analyzer indication for
calibration signal.)

5 - Post-detection level, dB SPL (If a single value is applicable to all
third-octave bands. Otherwise, use the FLOOR file format, defined in
Item #3.)

6 - \# of first Analysis record (Usually "1",) in .SPC file. (See Item
#1.)

7 - \# of last Analysis record in .SPC file. (See Item #1.)

> **"TIMEDAT":**

**Event Records:**

[Each line]{.underline} - FORTRAN format
(A4,16X,2I2,F5.2,1X,F8.2,1X,F7.4):

1 - Event ID

2 - Start Time, HOUR

3 - Start Time, MINUTE

4 - Start Time, SECOND

5 - Start Time, SECONDS (elapsed since midnight)

6 - Dummy value - not used - set to ".0000".

**3. Third-Octave Correction Data**

> A single format is used for all frequency-dependent correction
> data.This format is identical to the last four lines of the Analysis
> record format specified for the raw, third-octave spectral
> time-history file (Item #1), above.

[First line]{.underline} - FORTRAN format (11(1X,F6.2)):

1-11 - Dummy values - not used - set to "0.00".

[Second line]{.underline} - (Same FORTRAN format as previous line):

1-4 - Dummy values - not used - set to "0.00".

5-11 - Third-octave SPLs for ANSI bands 17-23

[Third line]{.underline} - (Same FORTRAN format as previous line):

1-11 - Third-octave SPLs for ANSI bands 24-34

[Fourth line]{.underline} - (Same FORTRAN format as previous line):

1-6 - Third-octave SPLs for ANSI bands 35-40

7-11 - Dummy values - not used - set to "0.00".

> A separate file for each type of correction, organized by microphone
> system, and also, if necessary, by individual aircraft flyby "event",
> must be provided. In addition, combined system correction and
> microphone correction files should be provided. Naming conventions are
> as follows:
>
> [Type of Correction:]{.underline} [Name:]{.underline}
>
> Recording system frequency response "**SYSTEM**"
>
> Analyzer frequency response "**ANALYZER**"
>
> Pink noise generator output calibration "**PINK**"
>
> Analyzer bandwidth error ("Integrated filter response") "**BWE**"
>
> Combined system corrections, including the above corrections
> "**COMP**"
>
> Microphone pressure-response "**MIC**"
>
> If a single incidence angle is used:
>
> Microphone free-field response (Including grid, if applicable)
> "**FF**"
>
> Windscreen insertion-loss "**WS**"
>
> Combined microphone and windscreen corrections "**MIKCOR**"
>
> Though not correction files, per se, the pre-detection and
> post-detection background noise spectra utilize the same format:
>
> Pre-Detection Background Noise "**AMBI**"
>
> Post-Detection Background Noise "**FLOOR**"
>
> When a correction data file is associated with a specific event, the
> files should be organized in subdirectories by event. Values in the
> files should indicate correction factors to be [added]{.underline} to
> aircraft event data SPLs, except for AMBI and FLOOR files, where
> values should indicate the actual SPLs. If gain or calibration
> corrections have been applied to the AMBI and FLOOR data, this should
> be indicated by adding the extension "**.ADJ**" to the filenames.

**4. Incidence-Dependent Third-Octave Correction Data**

> Correction data for microphone free-field response vs incidence angle,
> as well as windscreen insertion-loss vs incidence angle should be
> presented in the following format. If only a single value for
> incidence is used (Such as is common when microphones are oriented for
> primarily grazing incidence throughout the aircraft flyby, and when
> the change in the magnitude of the corrections due to varying
> incidence is small,) these corrections may be provided in the file
> format specified for Third-Octave Correction Data (Item #3), and
> included in the combined "**MIKCOR**" correction file as mentioned
> above. When Incidence-Dependent Third-Octave Correction Data files are
> used, however, separate files should be provided for microphone
> free-field response and windscreen insertion loss. A file of combined
> incidence-based corrections should also be provided. File-naming
> conventions: Combined incidence corrections - "**CORMIK**"; windscreen
> insertion-loss corrections - "**WS**"; microphone free-field
> corrections (Including grid) - "**FF**".
>
> (See next page.)

The file is comprised of several **Angular Correction** **records:**
Each contains the third-octave data corrections for a specific incidence
angle. Each record is comprised of three lines.

[First line]{.underline} - FORTRAN format (1X,F5.1)

Incidence angle, DEGREES (From normal axis of microphone. See Figure 2.)

[Second line]{.underline} - FORTRAN format (9(2X,F6.2))

1-9 - Third-octave corrections for specified angle for ANSI bands
#27-35, dB.

[Third line]{.underline} - FORTRAN format (8(2X,F6.2))

1-5 - Third-octave corrections for specified angle for ANSI bands
#36-40, dB.

6-8 - Dummy values - not used - set to ".00".

> Data must be provided to encompass all incidence angles calculated for
> each event. As in the other correction files, these values should be
> corrections to be [added]{.underline} to aircraft event SPLs.

**5. Raw Tracking Data Time-Histories**

> When implementing aircraft positional processes other than
> single-point systems (Item #6,) , a time-history of aircraft position
> vs. time should be provided in the following format. Note that XYZ
> co-ordinates should be referenced to the ground at the primary
> Centerline-Center microphone. If acoustical data for a single event
> are provided for multiple microphone sites, only a single Tracking
> Data Time-History file need be provided. By providing XYZ co-ordinates
> of each microphone relative to the primary Centerline-Center
> microphone separately, aircraft distances to each microphone can be
> properly calculated. Filenaming convention: **"SRxxxx"** (Where "xxxx"
> = Event ID.)

**Position records:**

Each line represents one time sample of tracking data. Note that sample
intervals need not be uniform, nor associated with specific acoustic
data record times. Validation software will interpolate between time
samples.

[Each line]{.underline} - FORTRAN format (3(E15.8,3X)E15.8):

1 - Time-of-day, SECONDS (elapsed since midnight)

2 - X (longitudinal) co-ordinate, FEET

3 - Y (lateral) co-ordinate, FEET (Note that sign should be assigned to
aircraft position as it is to microphone positions. I.e.: when the
aircraft Y co-ordinate is negative, it is on the same side of the
Centerline as a microphone with a negative Y co-ordinate.)

4 - Z (vertical) co-ordinate, FEET

> Note that tracking time-history data must encompass emission
> co-ordinates for 10dB-down points.

**6. Single-Point Tracking Data**

> When a single-point tracking process is implemented, the appropriate
> performance information should be provided in the following format.
> Multiple events at a single microphone may be combined in one file per
> subdirectory. Filenaming convention: "**NUXDAT**".

**Event records:**

Each contains data for a single event. 3 lines.

[First line]{.underline} - FORTRAN format (A4):

1 - Event ID

[Second line]{.underline} - FORTRAN format
(F9.3,2X,F5.2,2X,2(F7.2,2X),F5.2,2(1X,F6.2),2(2X,F5.2)):

1 - Time at overhead, SECONDS (elapsed since midnight)

2 - Microphone height, FEET. (Usually "4".)

3 - Altitude at overhead, FEET

4 - Reference altitude, FEET

5 - Dummy value - not used - set to "0.00".

6 - Groundspeed, KNOTS

7 - Reference groundspeed, KNOTS

8 - Climb / descent angle, DEGREES (Use negative value for descent.)

9 - Reference climb / descent angle, DEGREES

[Third line]{.underline} - FORTRAN format
(F8.4,1X,F7.4,1X,F6.2,3(1X,F8.2),4X,F5.2):

1 - Pitch, DEGREES (Total pitch, including climb / descent angle - set
to "0.0000" if emission angle calculation does not accomodate pitch.)

2 - Reference pitch, DEGREES (Total pitch, including climb / descent
angle - set to "0.0000" if emission angle calculation does not
accomodate pitch.)

3 - Horizontal cross-angle, DEGREES (See Fig. 1.)

4 - Microphone lateral distance Centerline, FEET

5 - Reference microphone lateral distance to Centerline, FEET

6 - Lateral distance, aircraft to microphone, at overhead, FEET

7 - Sign multiplier for lateral microphone distance to centerline (Use
"-1.00" for microphone location with negative lateral \[Y\] position,
"1.00" for mic location with positive lateral position.)

**7. Layered Meteorological Data**

> Weather information should be provided as temperature and humidity at
> the center points of 30 meter layers vs time of day. Filenaming
> convention: **"Mmmddyy".** ( Where "mm" = month, "dd' = day, and "yy"
> = year.)

**Four-line header:**

[First line]{.underline} - FORTRAN format (1X,I2)

1 - Number of time entries in file (Up to 5)

[Second line]{.underline} - FORTRAN format (I2,1X,I2,1X,I2)

1 - Measurement date, MONTH

2 - Measurement date, DAY

3 - Measurement date, YEAR

[Third line]{.underline} - FORTRAN format N\*(1X,F7.1) \[Where N =
number of time entries in file.\]

1 - Met Measurement time-of-day , SECONDS (elapsed since midnight)

[Fourth line]{.underline} - FORTRAN format N\*(3(1X,F5.2)) \[Where N =
number of time entries in file.\]

1 - Ten-meter temperature, DEGREES (Centigrade)

2 - Ten-meter relative humidity, PERCENT

3 - Ten-meter pressure, INCHES (Mercury)

**Layer records:**

[Each line]{.underline} - FORTRAN format N\*(2(1X,F5.2)) \[Where
N=number of time entries in file.\]

1 - Temperature at center of layer, DEGREES (Centigrade)

2 - Relative humidity at center of layer, PERCENT

**8. Single-point Meteorological Data**

> When weather data are only available from the Ten-meter station, or
> when averages of ten-meter and altitude values for temperature and
> humidity have been pre-determined, use the following format.
> Filenaming convention: **"Tmmddyy".** (Where "mm" = month, "dd" = day,
> and "yy" = year.)

**Time records:**

[Each line]{.underline} - FORTRAN format (2I2,1X,F5.2,1X,F4.1)

1 - Met measurement time, HOUR

2 - Met measurement time, MINUTE

3 - Temperature, DEGREES (Fahrenheit)

4 - Relative humidity, PERCENT

**9. Raw Meteorological Data**

> In addition to the layered or averaged weather data, unprocessed met
> data should also be provided. Use the following format. Filenaming
> convention: **"MXXDATmm.dd".** (Where "mm" = month, and "dd" = day.)
>
> The file is comprised of a sequence of measurements, by time. For each
> time entry, there is a header followed by a series of altitude
> measurements.

**Three-line header:**

[First line]{.underline} - FORTRAN format (I2,1X,I2,1X,I2)

1 - Measurement date, MONTH

2 - Measurement date, DAY

3 - Measurement date, YEAR

[Second line]{.underline} - FORTRAN format (I2,1X,I2)

1 - Met measurement time, HOUR

2 - Met measurement time, MINUTE

[Third line]{.underline} - FORTRAN format (1X,F5.2,2X,F6.2,3X,F6.3)

1 - Ten-meter temperature, DEGREES (Centigrade)

2 - Ten-meter relative humidity, PERCENT

3 - Ten-meter pressure, INCHES (Mercury)

**Altitude records:**

[Each line]{.underline} - FORTRAN format (I5,1X,F5.2,F6.2)

1 - Altitude, FEET

2 - Temperature, DEGREES(Centigrade)

3 - Relative humidity, PERCENT

**Final record in time entry:**

(Same format as Altitude records.)

a negative altitude value indicates the end of the current time-entry
data.

Attachments:

> Table 1 - Third Octave Bands of Interest C:\\CERT\\BANDS.DOC
>
> Figure 1 - Aircraft and Microphone Geometry C:\\CERT\\FIG1B.WPG
>
> Figure 2 - Microphone Incidence C:\\CERT\\INCID.DOC

C:\\CERT\\PFORMATS.DOC