INM Radar File Conversion Utility

Description:

The INM Radar File Conversion Utility provides the ability to convert INM radar data into a format that the APECS Animator can animate properly. The source INM radar data can either be in an ASCII formatted file or in a set of INM created binary files.

Once converted, INM radar data can be displayed in the same manner as JSIMMOD and SIMMOD data.

The INM Radar File Conversion Utility in the Animator works in a manner very similar to INM 6.0 itself and is described by the following three categories:

1. Input Files
2. Track Data
3. Output Filename
4. Final Notes

Input Files

The snapshot below displays the Input File(s) tab of the INM Radar to APECS Radar Conversion Utility. Please note the two input file type options:

• ASCII Input File
• _FP and _TK Binary Input Files

ASCII Input File - When the ASCII Input File option is chosen the user should supply a filename which points to an ASCII comma-separated text file. The file should be formatted in the same manner as INM expects. The INM 6.0 documentation on this format is found in the INM User's Guide at page 3-18.

You supply the input text file. The text file can contain any kind of track data, but the intention is that you process raw ARTS radar track data, and write the track data to a specially formatted text file.

The format of the INM ASCII radar file is as follows:

Code, FltId, AcType, OpType, ApFrom, ApTo, RwyId
, Time,  X or Lat,  Y or Long,  Alt,  Spd
, Time,  X or Lat,  Y or Long,  Alt,  Spd
...etc...
Code, FltId, AcType, OpType, ApFrom, ApTo, RwyId
, Time,  X or Lat,  Y or Long,  Alt,  Spd
, Time,  X or Lat,  Y or Long,  Alt,  Spd
, Time,  X or Lat,  Y or Long,  Alt,  Spd
...etc...

where:

Code	Beacon or numeric code (0557) or 0000
FltId	Flight identifier (AAL1234)
Actype	FAA aircraft type id (B727)
OpType	Operation type: A = approach, D = depart, V = overflight, ? = unknown
ApFrom	From-airport (SFO) or ???
ApTo	To-airport (LAX) or ???
RwyId	Runway end (31L) or ???
Time	Time of radar return (decimal hours)
X or Lat	X value (nmi , km) or latitude (decimal deg)
Y or Long	Y value (nmi , km) or longitude (decimal deg)
Alt	Aircraft Altitude (ft, m)
Spd	Aircraft ground speed (kt, km/hr) or 0

Fields must be separated by commas. A comma must be in the first column of a track point line. Blank lines and comment lines can be anywhere. There can be any number of tracks and points per track.

A line starting with the number-sign character (#) is ignored. You can use this method to document your file or to comment-out data sections.

The following is an example radar track CSV text file in X,Y format.

#EXAMPLE RADAR FILE TEST50.CSV
0012, SDU105, BA31, A, ???, SFO, ???
, 9.28833, 11.15063, -5.67526, 3500, 187
, 9.28972, 10.99544, -5.53952, 3500, 186

0016, UAL1287, B737, A, ???, SFO, ???
, 9.18444, 2.22314, -1.16763, 700, 169
, 9.18972, 1.67270, -0.85274, 400, 156
, 9.19222, 1.37155, -0.75014, 300, 152
, 9.19361, 1.26781, -0.60724, 300, 152

_FP and _TK Binary Input Files - When the _FP and _TK Binary Input Files option is chosen the user should supply filenames corresponding to previously imported INM radar data. When radar data is imported into INM two files are created called _FP.bin and _TK.bin. These two files contain most (aircraft speed data is omitted) of the data found in the original ASCII CSV file from which they were imported.

The exact format of the _FP.bin and _TK.bin files is not relevant in this document, but a couple of checks you can perform to determine if your two files are probably valid are as follows:

• Divide the exact file size of the _FP.bin file by 40. The result should be an even number with no remainder. If there is no remainder, then your file is probably ok and the number of tracks in the file is equal to the result.
• Divide the exact file size of the _TK.bin file by 16. The result should be an even number with no remainder. If there is no remainder, then your file is probably ok and the number of tracks points in the file is equal to the result.

Track Data

The Track Data tab allows the user to modify the parameters to the INM Radar to APECS Radar Conversion Utility. The parameters are very similar to those found in INM.

Units used in input file:

• English - If your data is in nautical miles for distance and feet for altitude select this option.
• Metric - If your data is in kilometers for distance and meters for altitude select this option.

Track points are in:

• X, Y (nmi, km) - If your data is distance X east and distance Y north from a given latitude and longitude origin select this option. Type in the latitude/longitude of the origin in the fields provided. The radar track Y axis must be oriented on true north.
• Lat, Long (deg) - If your data is already in latitude/longitude format then select this option.

Important Note:

Testing has indicated that the _FP.bin and _TK.bin files are stored by INM 6.0 in English X, Y format. If you choose to convert these two files you should choose the appropriate options above and supply an appropriate origin latitude/longitude in the provided fields.

Output Filename

The Output Filename tab is where the name of the output file for the conversion process is specified.

Final Notes

After converting the INM radar data to the APECS INM radar format the data will not be automatically loaded. You must choose the Options - Preferences menu item to actually specify that the INM radar data should be displayed in the APECS Animator.

Once you have chosen the Options - Preferences menu item you should choose the INM option on the Data Source tab. Supply the filename in the text field provided. After supplying the correct filename press the Apply button to change the display of aircraft to the newly converted INM radar data.