Skip to content

Aircraft dropsondes in range

Jump to bottom
Ajda Savarin edited this page Sep 11, 2023 · 2 revisions 
./bash/download_process_aircraft_dropsonde_saildrone.sh

OR

python ../scripts/download_aircraft_recon_dropsonde_full.py
python ../scripts/download_latest_saildrone_data.py

python ../scripts/identify_dropsondes_in_range_of_saildrone.py

In order for things to run as expected, you will also need to set some switches in ./configs/config.yml

1. Saildrone data download defaults:

  • 1.1: download_saildrone_data: True
  • 1.2: download_saildrone_data_path: data/saildrone
  • 1.3: all_saildrones: 1031, 1036, 1040, 1041, 1042, 1045, 1057, 1064, 1065, 1068, 1069, 1083
  • 1.4: update_saildrones: 1031, 1036, 1040, 1041, 1042, 1045, 1057, 1064, 1065, 1068, 1069, 1083

This step will run whenever 1.1 is set to True, but not if it is set to False. It will download all the saildrones listed in 1.4 to the directory specified in 1.2. You should always have at least two saildrones listed in 1.4 - the process is very fast.

A note of caution -- the data is downloaded from the public NOAA PMEL ERDDAP, so it is updated only every 30 minutes or so, and it provides the data at the frequency it is displayed on the Saildrone Portal. If in real-time, the data contains gaps, those gaps will not be filled in with later downloads.

**2. Aircraft dropsondes in range defaults **:

  • 2.1: download_aicraft_recon_dropsonde_full: True
  • 2.2: identify_dropsondes_in_range_of_saildrone: True
  • 2.3: download_aircraft_recon_dropsonde_data_path: data/recon/dropsonde_full
  • 2.4: dropsonde_start_date: 2023-08-01 00:00:00
  • 2.5: dropsonde_end_date: 2023-09-01 23:59:59
  • 2.6: saildrone_for_dropsonde_comparison: 1031
  • 2.7: saildrone_time_tolerance_minutes: 30
  • 2.8: saildrone_distance_tolerance_km: 100

This step will run whenever 2.1 (download) and 2.2 (identify) are set to True, but not if set to False. It will download the full dropsonde data from aircraft recon missions - this is available a day or two after the flight, not in real-time, and store it in 2.3. It will download all the dropsondes in the time range between 2.4 and 2.5, and compare their locations to saildrone 2.6. The dropsonde needs to be within 2.8 km from the saildrone 2.6 within 2.7 minutes in order to count.

Example output:

  • .csv file with all dropsondes and min and max distances from a given saildrone here
  • .csv file with only the dropsondes within a given distance tolerance form a given saildrone here

Ajda Savarin

Clone this wiki locally