13 Detections Table Field Definitions
Filename: detections.csv
Below are the field definitions for the Detections table, which is a primary table.
| Field | Definition | Required | Default | Data Type | Reference Table | Constraint |
| deployment_organization_code | Code of the organization that the deployment belongs to.
Examples: “NEFSC”, “WHOI” |
Always | Code | Organizations (see Excel) | ||
| deployment_code | Unique code for the deployment that the analysis belongs to.
Examples: “WHOI_GOM_202310_WE03”, “WHOI_MA-RI_202210_WE16”, “NEFSC_MA-RI_202110_NS01”, “NEFSC_MA-RI_202202_COX02” |
Always | Code | Deployments | ||
| analysis_organization_code | Code of the organization that conducted and owns the analysis.
Examples: “NEFSC”, “WHOI” |
Always | Code | Organizations (see Excel) | ||
| analysis_code | Code of the analysis that the detection belongs to.
Examples: “RIWH_ANALYSIS”, “BEAKED_ANALYSIS” |
Always | Code | Analyses | ||
| detection_start_datetime | Start date and time for the time period for the detection event or time bin depending on analysis granularity
Example: “2025-03-26T15:34:27-0500” |
Always | Timestamp | |||
| detection_end_datetime | End date and time for the time period for the detection event or time bin depending on analysis granularity. If detection is for a single point in time, the start and end datetimes can be the same.
Examples: “2025-03-26T15:34:27-0500”, “2025-03-26T15:34:30-0500” |
Always | Timestamp | |||
| detection_effort_secs | The amount of time (in seconds) the effort occurred in. This would translate to encounter or event duration for encounter/event level data. If the entire period was analyzed, enter total duration between the detection start and end datetimes.
Example: If the first 5 minutes of every hourly analysis bin was analyzed, this number would be “300”. If the full hour of every hourly analysis bin was analyzed, this number would be “3600”. |
Always | Float | |||
| detection_sound_source_code | The species or detected sound the detection period relates to
Examples: “HUWH”, “STDO”, “RV-L”, “RAIN” |
Always | Code | Sound Sources (see Excel) | ||
| detection_call_type_code | The call/click type used for presence determination for the detection period
Examples: “RIWH_UPCALL”, “HUWH_SONG”, “OD_WHIS_HF” |
Always | Code | Call Types (see Excel) | ||
| detection_behavior_code | Behavior associated with detected event
Examples: “CONTACT”, “FORAGING”, “MOM_CALF”, “MATING” |
Code | Behaviors (see Excel) | |||
| detection_demographic_code | The demographic determined of the sound source for the detection period
Examples: “ADULT_FEMALE_OR_JUV”, “MID-SIZED_INDIVIDUAL”, “MIXED_GROUP” |
Code | Demographics (see Excel) | |||
| detection_n_validated | Number of actual detections that have been validated to be correct in the detection time period
Examples: “3”, “258” |
Integer | ||||
| detection_n_total | Total number of detections for the sound source within the detection time period (can include true and false detections)
Examples: “15”, “179” |
Integer | ||||
| detection_result_code | Detection result indicating if the species was detected or not
Examples: “DETECTED”, “POSSIBLY_DETECTED”, “NOT_DETECTED” |
Always | Code | Detection Result Types (see Excel) | ||
| detection_event_type | Type of detection event (if available)
Example: PAMGuard’s eventType field |
Text | ||||
| detection_event_id | ID of the detection event (if available)
Example: PAMGuard’s event ID |
Text | ||||
| detection_latitude | Latitude of the platform location at time of detection (or start of encounter) in decimal degrees (DD.DDDD), only applicable to mobile platforms (e.g., gliders, buoys)
Example: “41.141289” |
Float | ||||
| detection_longitude | Longitude of the platform location at time of detection (or start of encounter) in decimal degrees (DD.DDDD), only applicable to mobile platforms (e.g., gliders, buoys). Negative for locations west of the central meridian.
Example: “-71.102908” |
Float | ||||
| detection_received_level_db | Received level of the detection in dB. For single call detections, a singular value should be placed here. For encounters or time binned data, an average or median received level should be placed here. Further details such as the exact unit (e.g. dB RMS, or dB pp), and whether a median or average received level was used should be placed in the analysis_json or analysis_comments fields of the parent analysis. For encounters/time binned data, each signal’s received level can be placed in the detection_json field.
Example: “15” |
Float | ||||
| detection_quality_code | Quality type of the detection if it was validated or not. This field may be left blank if the analysis_quality_code is “UNKNOWN” for the parent analysis, otherwise it is recommended to fill it out.
Examples: “INVALID”, “UNVERIFIED”, “VALID”, “PARTIALLY_VALID” |
Code | Detection Quality Types (see Excel) | |||
| detection_n_animals | Estimated number of animals thought to be in the detection
Example: “25” |
Integer | ||||
| detection_n_animals_min | Minimum number of animals thought to be in the detection
Example: “1” |
Integer | ||||
| detection_n_animals_max | Maximum number of animals thought to be in the detection
Example: “3” |
Integer | ||||
| detection_json | Additional structured data about the detection | JSON | ||||
| detection_comments | Comments about the detection | Text | ||||
| localization_method_code | Method used to localize the position of the animal(s)
Examples: “3D_SIMPLEX”, “DMON_REAL-TIME”, “SHIP-POSITION” |
Required if submitting localization data | Code | Localization Methods (see Excel) | ||
| localization_latitude | Estimated localized latitude of the animal in decimal degrees (DD.DDDDDD)
Example: “41.141289” |
Float | ||||
| localization_latitude_min | Minimum localized latitude accounting for localization uncertainty in decimal degrees (DD.DDDDDD)
Example: “40.724307” |
Float | ||||
| localization_latitude_max | Maximum localized latitude accounting for localization uncertainty in decimal degrees (DD.DDDDDD)
Example: “41.141289” |
Float | ||||
| localization_longitude | Estimates localized longitude of the animal in decimal degrees (DD.DDDDDD), negative for locations west of the central meridian
Example: “-71.102908” |
Float | ||||
| localization_longitude_min | Minimum localized longitude accounting for localization uncertainty in decimal degrees (DD.DDDDDD), negative for locations west of the central meridian
Example: “-70.016567” |
Float | ||||
| localization_longitude_max | Maximum localized longitude accounting for localization uncertainty in decimal degrees (DD.DDDDDD), negative for locations west of the central meridian
Example: “-71.102908” |
Float | ||||
| localization_distance_m | Estimated range of detection (in meters) from the recording platform
Examples: “3”, “60.5” |
Float | ||||
| localization_distance_m_min | Minimum range of detection (in meters) from the recording platform
Example: “0” |
Float | ||||
| localization_distance_m_max | Maximum range of detection (in meters) from the recording platform
Example: “8047” |
Float | ||||
| localization_bearing | For beamforming, the estimated bearing angle of the localization cone (0-360 degrees). Specify if bearing is measured relative to true north, magnetic north, or device orientation, and compass rose convention (clockwise, counter-clockwise) in analysis_json or analysis_comments.
Examples: “170”, “170.5” |
Float | ||||
| localization_bearing_min | For beamforming, the start bearing angle of the localization cone (0-360 degrees)
Examples: “167”, “167.5” |
Float | ||||
| localization_bearing_max | For beamforming, the end bearing angle of the localization cone (0-360 degrees)
Example: “175”, “175.34” |
Float | ||||
| localization_depth_method_code | Method used to estimate depth of the animal(s)
Examples: “3D_TDOA”, “MANUAL_DRTD”, “WHALEDO” |
Code | Localization Depth Methods (see Excel) | |||
| localization_depth_n_signals | Number of signals used to derive the depth
Examples: “7”, “218” |
Integer | ||||
| localization_depth_m | Estimated depth of animal (in meters)
Examples: “5”, “28.6” |
Float | ||||
| localization_depth_m_min | Minimum depth of animal (in meters)
Example: “1.5” |
Float | ||||
| localization_depth_m_max | Maximum depth of animal (in meters)
Example: “893” |
Float | ||||
| localization_json | Additional structured data about localization in JSON format | JSON | ||||
| localization_comments | Comments about the localization | Text |