DOI: 10.5281/zenodo.8004108
title: AeroSonicDB (YPAD-0523): Labelled audio dataset for acoustic detection and classification of aircraft

description: <strong>AeroSonicDB (YPAD-0523): Labelled audio dataset for acoustic detection and classification of aircraft</strong><br> Version 0.3 (June 2023) <strong>Publication</strong><br> If using this data in an academic work, please reference the DOI and version. <strong>Description</strong><br> AeroSonicDB (YPAD-0523) is a specialised dataset of ADS-B labelled audio clips for research in the fields of aircraft noise attribution and machine listening, particularly acoustic detection and classification of low-flying aircraft. Audio files in this dataset were recorded at locations in close proximity to a flight path approaching or departing Adelaide International Airport’s (ICAO code: YPAD) primary runway, 05/23. Recordings are initially labelled from radio (ADS-B) messages received from the aircraft overhead. Each recording is then human verified, and trimmed to the best (subjective) 20 seconds of audio in which the target aircraft is audible. A total of 1,890 audio clips are balanced across two top-level classes, “Aircraft” (3.57 hours: 642 20-second recordings) and “Silence” (3.37 hours: 1,248 5 and 10-second recordings). The aircraft class is then further broken-down into four unbalanced subclasses which broadly describe an aircrafts structure and propulsion mechanism. A variety of additional "airframe" features are provided to give researchers finer control of the dataset, and the opportunity to develop ontologies specific to their own use case. For convenience, the dataset has been split into training (6.28 hours) and testing (0.66 hours) subsets, with the training set further split into 10 folds for cross-validation. Care has been taken to ensure the class distribution for each subset and fold does not significantly deviate from the overall distribution. Researchers may find applications for this dataset in a number of fields; particularly aircraft noise isolation and monitoring in an urban environment, development of passive acoustic systems to assist radar technology, and understanding the sources of aircraft noise to help manufacturers design less-noisy aircraft. <strong>Audio data</strong><br> ADS-B (Automatic Dependent Surveillance–Broadcast) messages transmitted directly from aircraft are used to automatically capture and label audio recordings. A 60-second recording is triggered when an aircraft transmits a message indicating it is within a specified distance of the recording device. The file is labelled with a unique ICAO identifier code for the aircraft, as well as its last recorded altitude, date and time. The recording is then human verified and trimmed to 20 seconds - with the aircraft audible for the duration of the clip. A balanced collection of urban background noise without aircraft (silence) is included with the dataset as a means of distinguishing location specific environmental noises from aircraft noises. 10-second background noise, or “silence” recordings are triggered only when there are no aircraft broadcasting that they are within a specified distance of the recording device. These "silence" recordings are also human verified to ensure no aircraft noise is present. The dataset contains 1,180 10-second clips, and 68 5-second clips of silence/ambient background noise. <strong>Location information</strong><br> Recordings have been collected from three (3) locations. GPS coordinates for each location are provided in the "locations.json" file. In order to protect privacy, coordinates have been provided for a road or public space nearby the recording device instead of its exact location. <em>Location: 0</em><br> Situated in a suburban environment approximately 15.5km north-east of the start/end of the runway. For Adelaide, typical south-westerly winds bring most arriving aircraft past this location on approach. Winds from the north or east will cause aircraft to take-off to the north-east, however not all departing aircraft will maintain a course to trigger a recording at this location. The "trigger distance" for this location is set for 3km to ensure small/slower aircraft and large/faster aircraft are captured within a sixty-second recording. "Silence" or ambient background noises at this location include; cars, motorbikes, light-trucks, garbage trucks, power-tools, lawn mowers, construction sounds, sirens, people talking, dogs barking and a wide range of Australian native birds (New Holland Honeyeaters, Wattlebirds, Australian Magpies, Australian Ravens, Spotted Doves, Rainbow Lorikeets and others). <em>Location: 1</em><br> Situated approximately 500m south-east of the south-eastern end of the runway, this location is nearby recreational areas (golf course, skate park and parklands) with a busy road/highway inbetween the location and runway. This location features heavy winds and road traffic, as well as people talking, walking and riding, and also birds such as the Australian Magpie and Noisy Miner. The trigger distance for this location is set to 1km. Due to their low altitude aircraft are louder, but audible for a shorter time compared to "Location 0". <em>Location: 2</em><br> As an alternative to "Location 1", this location is situated approximately 950m south-east of the end of the runway. This location has a wastewater facility to the north, a residential area to the south and a popular beach to the west. This location offers greater wind protection and further distance from airport and highway noises. Ambient background sounds feature close proximity cars and motorbikes, cyclists, people walking, nail guns and other construction sounds, as well as the local birds mentioned above. <br> <strong>Aircraft metadata</strong><br> Supplementary "airframe" metadata for all aircraft has been gathered to help broaden the research possibilities from this dataset. Airframe information was collected and cross-checked from a number of open-source databases. The author has no reason to beleive any significant errors exist in the "aircraft_meta" files, however future versions of this dataset plan to obtain aircraft information directly from ICAO (International Civil Aviation Organization) to ensure a single, verifiable source of information. <strong>Class/subclass ontology (minutes of recordings)</strong> 0. no aircraft (202)<br> 0: no aircraft (202) 1. aircraft (214)<br> 1: piston-propeller aeroplane (12)<br> 2: turbine-propeller aeroplane (37)<br> 3: turbine-fan aeroplane (163)<br> 4: rotorcraft (1.6)<br> <br> The subclasses are a combination of the "airframe" and "engtype" features. Piston and Turboshaft rotorcraft/helicopters have been combined into a single subclass due to the small number of samples.<br> <br> <strong>Data splits</strong><br> Audio recordings have been split into training (90.5%) and test (9.5%) sets. The training set has further been split into 10 folds, giving researchers a common split to perform 10-fold cross-validation - ensuring reproducibility and comparative results. Data leakage into the test set has been avoided by ensuring recordings are disjointed from the training set by time and location - meaning samples in the test set for a particular location were recorded after any samples included in the training set for that particular location. <br> <strong>Labelled data</strong><br> The entire dataset (training and test) is referenced and labelled in the "sample_meta.csv" file. Each row contains a reference to a unique recording and all the labels and features associated with that recording and aircraft. Alternatively, these labels can be derived directly from the filename of the sample (see below), plus a JSON file which accompanies each aircraft sample. The "aircraft_meta.csv" and "aircraft_meta.json" files can be used to reference aircraft specific features - such as; manufacturer, engine type, ICAO type designator etc. (see below for all 14 airframe features). <strong>File naming convention</strong><br> Audio samples are in <em>WAV </em>format, and metadata for aircraft recordings are stored in <em>JSON </em>files. Both files share the same name, only differing by their file extension. <strong>Basic Convention</strong> “Aircraft ID + Date + Time + Location ID + Microphone ID” “XXXXXX_YYYY-MM-DD_hh-mm-ss_X_X” <strong>Sample with aircraft</strong> {hex_id} _ {date} _ {time} _ {location_id} _ {microphone_id} . {file_ext} 7C7CD0_2023-05-09_12-42-55_2_1.wav<br> 7C7CD0_2023-05-09_12-42-55_2_1.json <strong>Sample without aircraft</strong> “Silence” files are denoted with six (6) leading zeros rather than an aircraft hex code. All relevant metadata for “silence” samples are contained in the audio filename, and again in the accompanying “sample_meta.csv” 000000 _ {date} _ {time} _ {location_id} _ {microphone_id} . {file_ext} 000000_2023-05-09_12-30-55_2_1.wav <strong>Columns/Labels </strong><br> (found in sample_meta.csv, aircraft_meta.csv/json and aircraft recording JSON files) <em><strong>train-test</strong></em>: Train-test split (<em>train</em>, <em>test</em>) <em><strong>fold</strong></em>: Digit from 0 to 9 splitting the training subset 10 ways (else <em>test</em>) <em><strong>filename</strong></em>: The filename of the audio recording <strong><em>date</em></strong>: Date of the recording <em><strong>time</strong></em>: Time of the recording <em><strong>duration</strong></em>: Length of the recording (in seconds) <em><strong>location_id</strong></em>: ID for the location of the recording <em><strong>microphone_id</strong></em>: ID of the microphone used <em><strong>hex_id</strong></em>: Unique ICAO 24-bit address for the aircraft recorded <em><strong>altitude</strong></em>: Approximate altitude of the aircraft (in feet) at the start of the recording <em><strong>class</strong></em>: Top-level label for the recording (eg. 0 = No aircraft, 1 = Aircraft audible) <em><strong>subclass</strong></em>: Subclass label for the recording (eg. 0 = No aircraft, 3 = Turbine-fan aeroplane) <em><strong>reg</strong></em>: Registration number of the aircraft <em><strong>airframe</strong></em>: Describes the mechanical structure of the aircraft (eg. Power Driven Aeroplane, Rotorcraft) <em><strong>engtype</strong></em>: Type of engine (eg. Piston, Turboprop, Turbofan, Turboshaft) <em><strong>engnum</strong></em>: Number of engines <em><strong>shortdesc</strong></em>: 3 character alpha-numeric code describing the airframe and engine configuration (eg. L1P, L4J, H2T) <em><strong>typedesig</strong></em>: ICAO type designator for make and model of aircraft (eg. PC12, C185, B738) <em><strong>manu</strong></em>: Aircraft manufaturer (eg. Boeing, Pilatus, Airbus) <em><strong>model</strong></em>: Aircraft model (eg. 737-800, A320-232, DHC-8-315) <em><strong>engmanu</strong></em>: Engine manufacturer (eg. Pratt & Whitney, CFM Interntional, Rolls Royce) <em><strong>engmodel</strong></em>: Engine model (eg. TRENT XWB, CFM56-7B24E, PT6E-67XP) <em><strong>engfamily</strong></em>: Family of the engine model (eg. TRENT, CFM56, PT6) <em><strong>fueltype</strong></em>: Fuel type used in the engine (eg. Gasoline, Kerosine) <em><strong>propmanu</strong></em>: Propeller manufacturer (eg. Hartzell Propellers, Hamilton Standard, "Aircraft Not Fitted With Propeller") <em><strong>propmodel</strong></em>: Propeller model (eg. HC-E5A-3A\/NC10245B, 14SF-15, "Not Applicable") <em><strong>mtow</strong></em>: Maximum take off weight (MTOW) in kilograms <br> <strong>Conditions of use</strong><br> Dataset created by Blake Downward. The AeroSonicDB (YPAD-0523) dataset is offered free of charge for non-commercial use under the Creative Commons Attribution-NonCommercial 4.0 International (CC BY-NC 4.0) license. [https://creativecommons.org/licenses/by-nc/4.0/](https://creativecommons.org/licenses/by-nc/4.0/) <br> <strong>Feedback</strong><br> Please send suggestions, feedback and comments to:<br> Blake Downward: aerosonicdb@gmail.com <strong>Change log</strong> 0.3: locations.json file added, README updated 0.2: location information added to README