Search Help Show/Hide Menu
Summary
Item Identification
Keywords
Physical Location
Entity Info
Data Attributes
Support Roles
Extents
Access Info
Distribution Info
Issues
Related Items
Catalog Details

Summary

Abstract

The Cooperative Billfish Tagging Program (CBTP) at the National Oceanic and Atmospheric Administration (NOAA) Southwest Fisheries Science Center (SWFSC) collected tagging data (1963-2021) and angler survey responses (1969-2019) from thousands of volunteer anglers around the Pacific Ocean, with additional efforts from the Indian and Atlantic Oceans. The CBTP began in 1963 and has provided over 80,000 conventional mark-recapture tags and tagging supplies to billfish anglers fishing in the Pacific Ocean. Tag releases are recorded by anglers or captains on Tagging Report cards mailed to the NOAA Southwest Fisheries Science Center (SWFSC). More than 62,000 tags have been reported released on nine different billfish species in the Pacific Ocean, Atlantic Ocean, Indian Ocean, and other locales. Active tag distribution ended in March 2021, effectively ending the tagging program, but the SWFSC is still logging tag releases and recaptures for existing tags still in circulation. The data presented here represented all the information reported on the Tagging Report Cards received at the SWFSC as of February 2021.

Description

The SWFSC's constituent-based Billfish Tagging Program began in 1963 and has provided over 80,000 conventional spaghetti type tags and tagging supplies to billfish anglers fishing in the Pacific Ocean. Tag releases are recorded by anglers or captains on Tagging Report cards mailed in to the SWFSC and tags recovered on recaptured billfish are reported to the SWFSC via phone or email as indicated by the information printed on the body of the tag. Over 62,000 tags have been reported released on eight different billfish species in the Pacific Ocean, Atlantic Ocean, Indian Ocean, and other locales. Active tag distribution ended in March 2021, effectually ending the tagging program, but the SWFSC is still logging tag releases and recaptures for existing tags still in circulation.

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
tag_id
varchar(15)
The tag_id is an alphanumeric value (e.g. "A123456B") created by the concatenation of the alphanumeric tag identification printed on the body of the actual tag (e.g. "A123456") and the duplicate value (e.g. "B"). The tag identification is an uppercase letter followed by 6 numbers. In some instances the same tag number is reported as being deployed more than once, due to mistakes in tag acquisition and inventorying or if a fish is captured and re-released. To identify these instances, the first duplicate is designated as “B”, and the second as “C” (e.g. “A091324B” or “A091324C”). The order in which the tags are input into the database typically determines which are labeled as duplicates and thus which records terminate with "B" or "C". Tags with no duplicates do not terminate with "A".
dup
char(1)
In some instances the same tag_id is reported as deployed more than once, due to mistakes in tag acquisition and inventorying or if a fish is captured and re-released. To identify these instances, no duplicate is designated as “A”, the first duplicate is designated as “B”, and the second as “C” (e.g. “A091324B” or “A091324C”). The order in which the tags are input into the database typically determines which are labeled “A” versus “B”. Any "B" or "C" values are concatenated as terminal characters on the tag_id column.
research
varchar(1)
If the tag was released for or by a research institution. N= No, Y= Yes, Null = unanswered, but assumed N.
second_tag
varchar(15)
The tag identification for any second tag affixed to the billfish. This usually indicates research tags, but could include analog mark-recapture tags.
third_tag_pat
varchar(15)
The tag identification for a third tag or a Pop-off Archival Tag (PAT).
fourth_tag_spot
varchar(15)
The tag identification for a fourth tag or Smart Position and Temperature (SPOT) tag.
mm
tintyint
The month of tag release.
dd
tinyint
The day of tag release.
yyyy
smallint
The year of tag release.
location
varchar(50)
The general location of the tag release. Locations are colloquial and not geographically standardized (e.g. 10-minute fishing block, or degrees of latitude). Tag release location is either reported by the angler as a general location such as "Hawaii", or assigned during data entry based on provided coordinate data. However, records with coordinate data may not include "location" and records with "location" may not include coordinate data.
lat
decimal(9,6)
Signed decimal degree latitude of tag release, as calculated from provided lat_dg, lat_mn, and n_s.
lon
decimal(9,6)
Signed decimal degree longitude of tag release, as calculated from provided lon_dg, lon_mn, and e_w.
gear_cd
tinyint
Numeric code for fishing gear used to catch billfish.
gear_type
char(15)
Fishing gear type, corresponding to gear_cd, used to catch the billfish.
species_cd
tinyint
Numeric code for billfish species tagged.
species_common_name
varchar(50)
The common name of the billfish species tagged.
sex
char(1)
The sex of the tagged billfish.
length_1
smallint
Length measurement of fish at tag release. Length is estimated by anglers and not validated by NOAA at the time of release.
length_type
char(40)
Length measurement type. 0= no_value_reported, 11= cm_unknown, 12= cm_eye_to_tail_fork_billfish_only, 13= cm_bill_to_tail_fork_swordfish_only, 14= cm_cleithrum_to_tail_fork, 15= cm_lower_jaw_or_lip_to_tail_fork, 16= cm_snout_to_tail_tip_nonbillfish_only, 17= cm_snout_to_tail_fork_nonbillfish_only, 18= cm_tip_of_bill_to_tail_tip_billfish_only, 19= cm_dorsal_fin_to_dorsal_fin, 21= in_unknown, 22= in_eye_to_tail_fork_billfish_only, 23= in_bill_to_tail_fork_swordfish_only, 24= in_cleithrum_to_tail_fork, 25= in_lower_jaw_or_lip_to_tail_fork, 26= in_snout_to_tail_tip_nonbillfish_only, 27= in_snout_to_tail_fork_nonbillfish_only, 28= in_tip_of_bill_to_tail_tip_billfish_only, 29= in_dorsal_fin_to_dorsal_fin.
weight
smallint
Weight, in pounds, of billfish at tag release. Weight is estimated by anglers and not validated by NOAA at the time of release.
bait_cd
tinyint
Numeric code for fishing bait used to catch billfish. 0= unknown, 1= live_bait, 2= dead_bait, 3= unidentified_bait, 4= artificial_lure, 5= other, 6= fly.
bait_type
char(17)
Fishing bait used to catch billfish.
temp_f
tinyint
Water temperature, in degrees Fahrenheit, at billfish tagging.
fight
int
Fight time, in minutes, between hooking and landing billfish.
condition_cd
tinyint
Numeric code for billfish condition at release. 0= unknown, 1= excellent, 2= good, 3= fair, 4= poor, 5= injured, 6= dead.
condition
char(9)
Billfish condition at release based on angler's self-reported visual assessment.
hooks
char(1)
If any hooks are on the billfish at release.
comments
varchar(115)
Any comments related to tag release or data entry.
notes
varchar(115)
Any notes about data entry or corrections.

Distribution Information

  • ERDDAP is a data server that gives you a simple, consistent way to download subsets of scientific datasets in common file formats and make graphs and maps. This particular ERDDAP installation contains data related to Environmental Research Division projects and collaborations.

Child Items

No Child Items for this record.

Contact Information

Point of Contact
Nicole Nasby-Lucas
nicole.nasby-lucas@noaa.gov
858-334-2826

Metadata Contact
Nicole Nasby-Lucas
nicole.nasby-lucas@noaa.gov
858-334-2826

Extents

Geographic Area 1

East Boundary - North, Central, and South American Coastline

Time Frame 1
1963-01-01 - Present

Item Identification

Title: The Billfish Tagging Program--Tag Releases
Status: On Going
Creation Date: 2021
Abstract:

The Cooperative Billfish Tagging Program (CBTP) at the National Oceanic and Atmospheric Administration (NOAA) Southwest Fisheries Science Center (SWFSC) collected tagging data (1963-2021) and angler survey responses (1969-2019) from thousands of volunteer anglers around the Pacific Ocean, with additional efforts from the Indian and Atlantic Oceans. The CBTP began in 1963 and has provided over 80,000 conventional mark-recapture tags and tagging supplies to billfish anglers fishing in the Pacific Ocean. Tag releases are recorded by anglers or captains on Tagging Report cards mailed to the NOAA Southwest Fisheries Science Center (SWFSC). More than 62,000 tags have been reported released on nine different billfish species in the Pacific Ocean, Atlantic Ocean, Indian Ocean, and other locales. Active tag distribution ended in March 2021, effectively ending the tagging program, but the SWFSC is still logging tag releases and recaptures for existing tags still in circulation. The data presented here represented all the information reported on the Tagging Report Cards received at the SWFSC as of February 2021.

Purpose:

The tagging program promotes ethical angling of billfish. In addition, release and recovery information are used to examine movement patterns and distribution for billfishes (mainly swordfish, and blue, black and striped marlin).

Notes:

Active tag distribution ended in March 2021, effectually ending the Billfish Tagging Program, but the SWFSC is still logging tag releases and recaptures for existing tags still in circulation. The data presented here represent all Tagging Report Cards received at the SWFSC as of February 2021.

For privacy of Personally Identifiable Information (PII), this public dataset does not contain angler or captain names, addresses, emails, phone numbers, boat names, or club names as provided to the SWFSC on the tagging report cards. Instead, individual anglers are identified as anonymous numbers to retain the count of distinct participants while not revealing PII. For more information on the CBTP's privacy policy, please refer to NOAA's IT Policy and Oversight.

Supplemental Information:

For detailed information about the operations, methods, and database organization of the SWFSC Cooperative Billfish Tagging Program, please refer to:

Heberer, L.N., Wraith, J., Kohin, S., Gu, Y., Nasby-Lucas, N.D., and Dewar, H. 2021. The NOAA Southwest Fisheries Science Center Cooperative Billfish Tagging Program Operations and Database. NOAA Tech. Memo. NMFS-SWFSC-640 at at https://repository.library.noaa.gov/view/noaa/28449.

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None billfish
None black marlin
None blue marlin
None commercial fisheries
None recreational fisheries
None sailfish
None shortbill spearfish
None striped marlin
None swordfish
None tagging

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 1963-2021

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None Pacific Ocean

Instrument Keywords

Thesaurus Keyword
UNCONTROLLED
None conventional mark-recapture

Physical Location

Organization: Southwest Fisheries Science Center
City: La Jolla
State/Province: CA
Country: USA

Entity Information

Entity Type: Data Table
Active Version?: Yes
Description:

The SWFSC's constituent-based Billfish Tagging Program began in 1963 and has provided over 80,000 conventional spaghetti type tags and tagging supplies to billfish anglers fishing in the Pacific Ocean. Tag releases are recorded by anglers or captains on Tagging Report cards mailed in to the SWFSC and tags recovered on recaptured billfish are reported to the SWFSC via phone or email as indicated by the information printed on the body of the tag. Over 62,000 tags have been reported released on eight different billfish species in the Pacific Ocean, Atlantic Ocean, Indian Ocean, and other locales. Active tag distribution ended in March 2021, effectually ending the tagging program, but the SWFSC is still logging tag releases and recaptures for existing tags still in circulation.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
Primary Key tag_id varchar(15) The tag_id is an alphanumeric value (e.g. "A123456B") created by the concatenation of the alphanumeric tag identification printed on the body of the actual tag (e.g. "A123456") and the duplicate value (e.g. "B"). The tag identification is an uppercase letter followed by 6 numbers. In some instances the same tag number is reported as being deployed more than once, due to mistakes in tag acquisition and inventorying or if a fish is captured and re-released. To identify these instances, the first duplicate is designated as “B”, and the second as “C” (e.g. “A091324B” or “A091324C”). The order in which the tags are input into the database typically determines which are labeled as duplicates and thus which records terminate with "B" or "C". Tags with no duplicates do not terminate with "A".
100
Primary Key dup char(1) In some instances the same tag_id is reported as deployed more than once, due to mistakes in tag acquisition and inventorying or if a fish is captured and re-released. To identify these instances, no duplicate is designated as “A”, the first duplicate is designated as “B”, and the second as “C” (e.g. “A091324B” or “A091324C”). The order in which the tags are input into the database typically determines which are labeled “A” versus “B”. Any "B" or "C" values are concatenated as terminal characters on the tag_id column.
100
research varchar(1) If the tag was released for or by a research institution. N= No, Y= Yes, Null = unanswered, but assumed N.
100
second_tag varchar(15) The tag identification for any second tag affixed to the billfish. This usually indicates research tags, but could include analog mark-recapture tags.
100
third_tag_pat varchar(15) The tag identification for a third tag or a Pop-off Archival Tag (PAT).
100
fourth_tag_spot varchar(15) The tag identification for a fourth tag or Smart Position and Temperature (SPOT) tag.
100
mm tintyint The month of tag release.
100
dd tinyint The day of tag release.
100
yyyy smallint The year of tag release.
100
location varchar(50) The general location of the tag release. Locations are colloquial and not geographically standardized (e.g. 10-minute fishing block, or degrees of latitude). Tag release location is either reported by the angler as a general location such as "Hawaii", or assigned during data entry based on provided coordinate data. However, records with coordinate data may not include "location" and records with "location" may not include coordinate data.
100
lat decimal(9,6) Signed decimal degree latitude of tag release, as calculated from provided lat_dg, lat_mn, and n_s.
100
lon decimal(9,6) Signed decimal degree longitude of tag release, as calculated from provided lon_dg, lon_mn, and e_w.
100
gear_cd tinyint Numeric code for fishing gear used to catch billfish.
100
gear_type char(15) Fishing gear type, corresponding to gear_cd, used to catch the billfish.
100
species_cd tinyint Numeric code for billfish species tagged.
100
species_common_name varchar(50) The common name of the billfish species tagged.
100
sex char(1) The sex of the tagged billfish.
100
length_1 smallint Length measurement of fish at tag release. Length is estimated by anglers and not validated by NOAA at the time of release.
100
length_type char(40) Length measurement type. 0= no_value_reported, 11= cm_unknown, 12= cm_eye_to_tail_fork_billfish_only, 13= cm_bill_to_tail_fork_swordfish_only, 14= cm_cleithrum_to_tail_fork, 15= cm_lower_jaw_or_lip_to_tail_fork, 16= cm_snout_to_tail_tip_nonbillfish_only, 17= cm_snout_to_tail_fork_nonbillfish_only, 18= cm_tip_of_bill_to_tail_tip_billfish_only, 19= cm_dorsal_fin_to_dorsal_fin, 21= in_unknown, 22= in_eye_to_tail_fork_billfish_only, 23= in_bill_to_tail_fork_swordfish_only, 24= in_cleithrum_to_tail_fork, 25= in_lower_jaw_or_lip_to_tail_fork, 26= in_snout_to_tail_tip_nonbillfish_only, 27= in_snout_to_tail_fork_nonbillfish_only, 28= in_tip_of_bill_to_tail_tip_billfish_only, 29= in_dorsal_fin_to_dorsal_fin.
100
weight smallint Weight, in pounds, of billfish at tag release. Weight is estimated by anglers and not validated by NOAA at the time of release.
100
bait_cd tinyint Numeric code for fishing bait used to catch billfish. 0= unknown, 1= live_bait, 2= dead_bait, 3= unidentified_bait, 4= artificial_lure, 5= other, 6= fly.
100
bait_type char(17) Fishing bait used to catch billfish.
100
temp_f tinyint Water temperature, in degrees Fahrenheit, at billfish tagging.
100
fight int Fight time, in minutes, between hooking and landing billfish.
100
condition_cd tinyint Numeric code for billfish condition at release. 0= unknown, 1= excellent, 2= good, 3= fair, 4= poor, 5= injured, 6= dead.
100
condition char(9) Billfish condition at release based on angler's self-reported visual assessment.
100
hooks char(1) If any hooks are on the billfish at release.
100
comments varchar(115) Any comments related to tag release or data entry.
100
notes varchar(115) Any notes about data entry or corrections.

Attribute Details

tag_id

CC ID: 1088594
Seq. Order: 1
Data Storage Type: varchar(15)
Required: Yes
Primary Key: Yes
Status: Active
Description:

The tag_id is an alphanumeric value (e.g. "A123456B") created by the concatenation of the alphanumeric tag identification printed on the body of the actual tag (e.g. "A123456") and the duplicate value (e.g. "B").

The tag identification is an uppercase letter followed by 6 numbers. In some instances the same tag number is reported as being deployed more than once, due to mistakes in tag acquisition and inventorying or if a fish is captured and re-released. To identify these instances, the first duplicate is designated as “B”, and the second as “C” (e.g. “A091324B” or “A091324C”). The order in which the tags are input into the database typically determines which are labeled as duplicates and thus which records terminate with "B" or "C". Tags with no duplicates do not terminate with "A".

Display Example: A123456B
Format Mask: A999999A
Foreign Key Relations:

"tag_id" in "Billfish Tagging Program--Tag Recaptures" table

dup

CC ID: 1088595
Seq. Order: 2
Data Storage Type: char(1)
Max Length: 1
Required: Yes
Primary Key: Yes
Status: Active
Description:

In some instances the same tag_id is reported as deployed more than once, due to mistakes in tag acquisition and inventorying or if a fish is captured and re-released. To identify these instances, no duplicate is designated as “A”, the first duplicate is designated as “B”, and the second as “C” (e.g. “A091324B” or “A091324C”). The order in which the tags are input into the database typically determines which are labeled “A” versus “B”.

Any "B" or "C" values are concatenated as terminal characters on the tag_id column.

Case Restriction: Upper
Display Example: B
Allowed Values: A-C

research

CC ID: 1088596
Seq. Order: 3
Data Storage Type: varchar(1)
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

If the tag was released for or by a research institution. N= No, Y= Yes, Null = unanswered, but assumed N.

Case Restriction: Upper
Display Example: Y
Null Value Meaning:

Null values are assumed to indicate "No".

Allowed Values: Yes; No; Null
Default Value: Null

second_tag

CC ID: 1088597
Seq. Order: 4
Data Storage Type: varchar(15)
Required: No
Primary Key: No
Status: Active
Description:

The tag identification for any second tag affixed to the billfish. This usually indicates research tags, but could include analog mark-recapture tags.

Null Value Meaning:

No second tag was released.

third_tag_pat

CC ID: 1088598
Seq. Order: 5
Data Storage Type: varchar(15)
Required: No
Primary Key: No
Status: Active
Description:

The tag identification for a third tag or a Pop-off Archival Tag (PAT).

Display Example: 2P0551
Null Value Meaning:

No third tag or PAT tag was released.

fourth_tag_spot

CC ID: 1088599
Seq. Order: 6
Data Storage Type: varchar(15)
Required: No
Primary Key: No
Status: Active
Description:

The tag identification for a fourth tag or Smart Position and Temperature (SPOT) tag.

Null Value Meaning:

No fourth tag or SPOT tag was released.

mm

CC ID: 1088601
Seq. Order: 7
Data Storage Type: tintyint
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

The month of tag release.

General Data Type: integer
Format Mask: mm
Null Value Meaning:

No month reported.

Allowed Values: 01-12

dd

CC ID: 1088602
Seq. Order: 8
Data Storage Type: tinyint
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

The day of tag release.

General Data Type: integer
Display Example: 13
Format Mask: dd
Null Value Meaning:

No day reported.

yyyy

CC ID: 1088652
Seq. Order: 9
Data Storage Type: smallint
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

The year of tag release.

General Data Type: integer
Display Example: 2021
Format Mask: yyyy
Null Value: Blank
Null Value Meaning:

No year reported.

location

CC ID: 1088660
Seq. Order: 10
Data Storage Type: varchar(50)
Required: No
Primary Key: No
Status: Active
Description:

The general location of the tag release. Locations are colloquial and not geographically standardized (e.g. 10-minute fishing block, or degrees of latitude). Tag release location is either reported by the angler as a general location such as "Hawaii", or assigned during data entry based on provided coordinate data. However, records with coordinate data may not include "location" and records with "location" may not include coordinate data.

General Data Type: character
Display Example: Hawaii, USA
Null Value Meaning:

No location provided.

lat

CC ID: 1088670
Seq. Order: 11
Data Storage Type: decimal(9,6)
Required: No
Primary Key: No
Precision: 9
Scale: 6
Status: Active
Description:

Signed decimal degree latitude of tag release, as calculated from provided lat_dg, lat_mn, and n_s.

Null Value Meaning:

No value reported.

Allowed Values: -90 to 90

lon

CC ID: 1088675
Seq. Order: 12
Data Storage Type: decimal(9,6)
Required: No
Primary Key: No
Precision: 9
Scale: 6
Status: Active
Description:

Signed decimal degree longitude of tag release, as calculated from provided lon_dg, lon_mn, and e_w.

Null Value Meaning:

No values reported.

gear_cd

CC ID: 1088676
Seq. Order: 13
Data Storage Type: tinyint
Max Length: 2
Required: Yes
Primary Key: No
Status: Active
Description:

Numeric code for fishing gear used to catch billfish.

General Data Type: integer
Allowed Values: 1-11 1= baitboat; 2= purse_seine; 3= troll; 4= rod_reel; 5= harpoon; 6= longline; 7= handline; 8= gillnet; 9= unknown; 10= halibut_trawler; 11= free_tag

gear_type

CC ID: 1088677
Seq. Order: 14
Data Storage Type: char(15)
Required: Yes
Primary Key: No
Status: Active
Description:

Fishing gear type, corresponding to gear_cd, used to catch the billfish.

General Data Type: character
Case Restriction: Lower

species_cd

CC ID: 1088678
Seq. Order: 15
Data Storage Type: tinyint
Required: Yes
Primary Key: No
Status: Active
Description:

Numeric code for billfish species tagged.

General Data Type: integer
Allowed Values: 7-14; 65;77; 78 7= broadbill_swordfish; 8= sailfish; 9= striped_marlin; 10= black_marlin; 11= pacific_blue_marlin; 12= unidentified_marlin; 13= unidentified_billfish; 14= shortbill_spearfish; 65= white_marlin; 77= longbill_spearfish; 78= atlantic_blue_marlin

species_common_name

CC ID: 1088679
Seq. Order: 16
Data Storage Type: varchar(50)
Required: Yes
Primary Key: No
Status: Active
Description:

The common name of the billfish species tagged.

General Data Type: character
Allowed Values: 7= broadbill_swordfish; 8= sailfish; 9= striped_marlin; 10= black_marlin; 11= pacific_blue_marlin; 12= unidentified_marlin; 13= unidentified_billfish; 14= shortbill_spearfish; 65= white_marlin; 77= longbill_spearfish; 78= atlantic_blue_marlin

sex

CC ID: 1088680
Seq. Order: 17
Data Storage Type: char(1)
Max Length: 1
Required: Yes
Primary Key: No
Status: Active
Description:

The sex of the tagged billfish.

General Data Type: character
Case Restriction: Upper
Allowed Values: M= Male; F= Female; U= Unknown

length_1

CC ID: 1088681
Seq. Order: 18
Data Storage Type: smallint
Required: No
Primary Key: No
Status: Active
Description:

Length measurement of fish at tag release. Length is estimated by anglers and not validated by NOAA at the time of release.

General Data Type: integer
Null Value Meaning:

No value reported.

length_type

CC ID: 1088718
Seq. Order: 19
Data Storage Type: char(40)
Required: Yes
Primary Key: No
Status: Active
Description:

Length measurement type. 0= no_value_reported, 11= cm_unknown, 12= cm_eye_to_tail_fork_billfish_only, 13= cm_bill_to_tail_fork_swordfish_only, 14= cm_cleithrum_to_tail_fork, 15= cm_lower_jaw_or_lip_to_tail_fork, 16= cm_snout_to_tail_tip_nonbillfish_only, 17= cm_snout_to_tail_fork_nonbillfish_only, 18= cm_tip_of_bill_to_tail_tip_billfish_only, 19= cm_dorsal_fin_to_dorsal_fin, 21= in_unknown, 22= in_eye_to_tail_fork_billfish_only, 23= in_bill_to_tail_fork_swordfish_only, 24= in_cleithrum_to_tail_fork, 25= in_lower_jaw_or_lip_to_tail_fork, 26= in_snout_to_tail_tip_nonbillfish_only, 27= in_snout_to_tail_fork_nonbillfish_only, 28= in_tip_of_bill_to_tail_tip_billfish_only, 29= in_dorsal_fin_to_dorsal_fin.

General Data Type: integer
Allowed Values: 0= no_value_reported, 11= cm_unknown, 12= cm_eye_to_tail_fork_billfish_only, 13= cm_bill_to_tail_fork_swordfish_only, 14= cm_cleithrum_to_tail_fork, 15= cm_lower_jaw_or_lip_to_tail_fork, 16= cm_snout_to_tail_tip_nonbillfish_only, 17= cm_snout_to_tail_fork_nonbillfish_only, 18= cm_tip_of_bill_to_tail_tip_billfish_only, 19= cm_dorsal_fin_to_dorsal_fin, 21= in_unknown, 22= in_eye_to_tail_fork_billfish_only, 23= in_bill_to_tail_fork_swordfish_only, 24= in_cleithrum_to_tail_fork, 25= in_lower_jaw_or_lip_to_tail_fork, 26= in_snout_to_tail_tip_nonbillfish_only, 27= in_snout_to_tail_fork_nonbillfish_only, 28= in_tip_of_bill_to_tail_tip_billfish_only, 29= in_dorsal_fin_to_dorsal_fin.

weight

CC ID: 1088719
Seq. Order: 20
Data Storage Type: smallint
Required: No
Primary Key: No
Status: Active
Description:

Weight, in pounds, of billfish at tag release. Weight is estimated by anglers and not validated by NOAA at the time of release.

General Data Type: integer
Unit of Measure: pounds
Null Value Meaning:

No value reported.

bait_cd

CC ID: 1088720
Seq. Order: 21
Data Storage Type: tinyint
Required: Yes
Primary Key: No
Status: Active
Description:

Numeric code for fishing bait used to catch billfish. 0= unknown, 1= live_bait, 2= dead_bait, 3= unidentified_bait, 4= artificial_lure, 5= other, 6= fly.

Allowed Values: 0= unknown, 1= live_bait, 2= dead_bait, 3= unidentified_bait, 4= artificial_lure, 5= other, 6= fly.

bait_type

CC ID: 1088723
Seq. Order: 22
Data Storage Type: char(17)
Required: Yes
Primary Key: No
Status: Active
Description:

Fishing bait used to catch billfish.

Allowed Values: 0= unknown, 1= live_bait, 2= dead_bait, 3= unidentified_bait, 4= artificial_lure, 5= other, 6= fly.

temp_f

CC ID: 1088725
Seq. Order: 23
Data Storage Type: tinyint
Required: No
Primary Key: No
Status: Active
Description:

Water temperature, in degrees Fahrenheit, at billfish tagging.

General Data Type: integer
Unit of Measure: degrees Fahrenheit
Null Value Meaning:

No value reported.

Allowed Values: 40-100

fight

CC ID: 1088726
Seq. Order: 24
Data Storage Type: int
Required: No
Primary Key: No
Status: Active
Description:

Fight time, in minutes, between hooking and landing billfish.

Null Value Meaning:

No value reported.

condition_cd

CC ID: 1088727
Seq. Order: 25
Data Storage Type: tinyint
Required: Yes
Primary Key: No
Status: Active
Description:

Numeric code for billfish condition at release. 0= unknown, 1= excellent, 2= good, 3= fair, 4= poor, 5= injured, 6= dead.

General Data Type: integer
Allowed Values: 0= unknown, 1= excellent, 2= good, 3= fair, 4= poor, 5= injured, 6= dead.

condition

CC ID: 1088728
Seq. Order: 26
Data Storage Type: char(9)
Required: Yes
Primary Key: No
Status: Active
Description:

Billfish condition at release based on angler's self-reported visual assessment.

General Data Type: character
Allowed Values: 0= unknown, 1= excellent, 2= good, 3= fair, 4= poor, 5= injured, 6= dead.

hooks

CC ID: 1088729
Seq. Order: 27
Data Storage Type: char(1)
Required: No
Primary Key: No
Status: Active
Description:

If any hooks are on the billfish at release.

Null Value Meaning:

No value reported, but assumed "No".

Allowed Values: U= Unknown; N= No, Y= Yes, or a numeric value.

comments

CC ID: 1088730
Seq. Order: 28
Data Storage Type: varchar(115)
Required: No
Primary Key: No
Status: Active
Description:

Any comments related to tag release or data entry.

notes

CC ID: 1088731
Seq. Order: 29
Data Storage Type: varchar(115)
Required: No
Primary Key: No
Status: Active
Description:

Any notes about data entry or corrections.

Support Roles

Data Steward

CC ID: 860625
Date Effective From: 2016-02-09
Date Effective To:
Contact (Person): Nasby-Lucas, Nicole
Address: 8901 La Jolla Shores Drive
La Jolla, CA 92037
US
Email Address: nicole.nasby-lucas@noaa.gov
Phone: 858-334-2826
Contact Instructions:

Please contact Nicole Nasby-Lucas (nicole.nasby-lucas@noaa.gov).

Distributor

CC ID: 860626
Date Effective From: 2016-02-09
Date Effective To:
Contact (Organization): Southwest Fisheries Science Center (SWFSC)
Address: 8901 La Jolla Shores Dr.
La Jolla, CA 92037
USA
Phone: (858)546-7000
URL: http://swfsc.noaa.gov/
Business Hours: 8:00-16:30

Metadata Contact

CC ID: 860627
Date Effective From: 2016-02-09
Date Effective To:
Contact (Person): Nasby-Lucas, Nicole
Address: 8901 La Jolla Shores Drive
La Jolla, CA 92037
US
Email Address: nicole.nasby-lucas@noaa.gov
Phone: 858-334-2826

Point of Contact

CC ID: 860628
Date Effective From: 2016-02-09
Date Effective To:
Contact (Person): Nasby-Lucas, Nicole
Address: 8901 La Jolla Shores Drive
La Jolla, CA 92037
US
Email Address: nicole.nasby-lucas@noaa.gov
Phone: 858-334-2826
Contact Instructions:

Please contact Nicole Nasby-Lucas (nicole.nasby-lucas@noaa.gov).

Extents

Extent Group 1

Extent Group 1 / Geographic Area 1

CC ID: 857808
Description

East Boundary - North, Central, and South American Coastline

Extent Group 1 / Time Frame 1

CC ID: 857807
Time Frame Type: Continuing
Start: 1963-01-01
Alternate End As Of Info: complete to 1 year prior

Access Information

Security Class: Unclassified

Distribution Information

Distribution 1

CC ID: 1088877
Start Date: 2021
End Date: Present
Download URL: https://oceanview.pfeg.noaa.gov/erddap/tabledap/FRD_Billfish_releases.html
Distributor: Southwest Fisheries Science Center (SWFSC) (2016-02-09 - Present)
File Name: Billfish Tagging Program,Tag Releases
Description:

ERDDAP is a data server that gives you a simple, consistent way to download subsets of scientific datasets in common file formats and make graphs and maps. This particular ERDDAP installation contains data related to Environmental Research Division projects and collaborations.

Issues

Issue 1

CC ID: 1087333
Issue:

Coordinate information may not be accurate for three reasons:

-Tag release location is estimated by anglers when GPS coordinate data is not available.

-Location information is communicated over phone and email, or handwritten by anglers on cards. Often, handwriting is difficult for data entry staff to discern.

- There may be human input error with location data due to the nature of manual population of the database.

Related Items

Item Type Relationship Type Title
Entity (ENT) Part of a Seamless Database The Billfish Tagging Program--Tag Recoveries

Tag releases and tag recaptures can be paired if "tagid" and "dup" are equal among the datasets.

Catalog Details

Catalog Item ID: 56757
GUID: gov.noaa.nmfs.inport:56757
Metadata Record Created By: Mihir Desai
Metadata Record Created: 2019-06-26 14:11+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2021-10-01
Owner Org: SWFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2021-10-01
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2022-10-01