doi:10.1038/s41598-017-17553-1: Radar tracks, raw data

206 x text files (comma separated values)

These files contain
the raw output data from the harmonic radar for bee flights that underpin the publication:

Woodgate JL, Makinson
JC, Lim KS, Reynolds AM, Chittka L. Continuous Radar Tracking Illustrates the
Development of Multi-destination Routes of Bumblebees. Scientific reports. 2017
Dec 11;7(1):17323. doi:10.1038/s41598-017-17553-1

These files are the
output from the radar. For most uses, the processed data from these files
(provided in the linked OSF archive, section ‘Coordinate data from each track’) will be preferable
since they have been converted from radar-centric to geocentric coordinates so
can be compared to one another and aligned with features in the real world.

Each file contains
tracking data from one flight by one bee. Most files contain an entire flight
but in some cases a single flight has been broken up into several sections,
denoted ‘a’, ‘b’, etc. Flights were defined as the movements undertaken by a
bee between leaving the nest and subsequently returning again. The radar
revolves once every 3s and records a positional fix if a signal from a
transponder is detected during each rotation.

Filenames are of the
form ‘YYMMDD_BID_BoutXX’, where

YYMMDD: date on which
track was recorded.

BID: a unique
identifier for each individual bee (will be the same for every datapoint within
a file). The bees were renamed for clarity in the publication according to the
following scheme:

Name in data files

Name in manuscript

B56

Bee 1

B61

Bee 2

B74

Bee 3

Y01

Bee 4

O72

Bee 5

G20

Bee 6

BoutXX: number
identifying how many flights each bee had made (A single bout encompasses all
the activity made between the bee leaving the nest and returning again.

Each file is a text
file with a 3-line header identifying the radar software, the date on which the
tracks were extracted, and variable names for the subsequent rows. The rest of
the file consists of comma delimited columns with a single row for each
positional fix recorded. The variables are:

Date: date on which
recording was made.

Time: timestamp for
each positional fix.

Range: distance in m
of bee from radar.

Azimuth: angle of bee
from axis of radar (NB, the radar records bees’ position in polar coordinates
relative to the radar’s own position. The radar is mobile and cannot be
guaranteed to be in the same position on different days. To convert the track
data to geocentric coordinates we record the position of several fixed
landmarks at the beginning of each day’s tracking and use these to triangulate
the position of the radar.)

Elev_angle: data
recorded by the radar on its own state. Never used in any analysis for this
paper but included for completeness.

Elevation: data
recorded by the radar on its own state. Never used in any analysis for this
paper but included for completeness.

V1: data recorded by
the radar on its own state. Never used in any analysis for this paper but
included for completeness.

V2: data recorded by
the radar on its own state. Never used in any analysis for this paper but
included for completeness.

本数据集包含206个文本文件（逗号分隔值格式）。这些文件记录了蜂群飞行过程中谐波雷达的原始输出数据，为以下发表的论文提供了基础：Woodgate JL, Makinson JC, Lim KS, Reynolds AM, Chittka L. 持续雷达追踪揭示大黄蜂多目的地航线的形成。科学报告，2017年12月11日；7(1):17323. doi:10.1038/s41598-017-17553-1。这些文件为雷达输出数据，在多数应用场景中，建议使用链接OSF存档中提供的经过处理的坐标数据（位于‘每个航迹的坐标数据’部分），因为这些数据已经从以雷达为中心的坐标系转换为以地球为中心的坐标系，因此可以相互比较并与现实世界中的特征对齐。每个文件包含一只蜜蜂一次飞行的跟踪数据。大多数文件包含整个飞行过程，但在某些情况下，单个飞行过程被分割成几个部分，标记为‘a’、‘b’等。飞行过程定义为蜜蜂从巢穴出发并返回巢穴所进行的移动。雷达每3秒旋转一次，并在每次旋转期间检测到应答器信号时记录位置修正。文件名格式为‘YYMMDD_BID_BoutXX’，其中

YYMMDD：记录轨迹的日期。

BID：每个蜜蜂个体的唯一标识符（在文件内的每个数据点中将保持一致）。根据以下方案，蜜蜂在出版物中被重新命名以增强可读性：

数据文件中的名称

稿件中的名称

B56

蜜蜂 1

B61

蜜蜂 2

B74

蜜蜂 3

Y01

蜜蜂 4

O72

蜜蜂 5

G20

蜜蜂 6

BoutXX：标识每只蜜蜂所进行飞行次数的数字（一个回合涵盖蜜蜂从巢穴出发并返回巢穴期间的所有活动）。

每个文件是一个文本文件，包含3行标题，分别标识雷达软件、提取轨迹的日期以及后续行中的变量名称。文件的其他部分由逗号分隔的列组成，每行记录一个位置修正。变量包括：

日期：记录的日期。

时间：每个位置修正的时间戳。

距离：蜜蜂与雷达之间的距离（米）。

方位角：蜜蜂与雷达轴线之间的角度（注意，雷达以极坐标形式记录相对于自身位置的蜜蜂位置。雷达是移动的，不能保证在不同日期处于相同位置。为了将轨迹数据转换为以地球为中心的坐标系，我们在每天跟踪开始时记录几个固定地标的方位，并使用这些地标进行三角测量以确定雷达的位置。）

仰角：雷达记录的自身状态数据。本论文的分析中未使用此数据，但为完整性起见包括在内。

高度：雷达记录的自身状态数据。本论文的分析中未使用此数据，但为完整性起见包括在内。

V1：雷达记录的自身状态数据。本论文的分析中未使用此数据，但为完整性起见包括在内。

V2：雷达记录的自身状态数据。本论文的分析中未使用此数据，但为完整性起见包括在内。