Search Help Show/Hide Menu
Summary
Item Identification
Data Attributes
Catalog Details

Summary

Entity Information

Data Attribute / Type Description
TRIP_ID
VARCHAR2(8 BYTE)
Trip identification number. Format is JAYYXX; so a ‘JA’ is followed by the last two digits of the trip year and then a sequential trip number, which starts at 01 for each year. So ‘JA7802’ is the second trip observed in 1978. It should be noted that this ID number appears to have been generated well after data collection; it does not appear on data sheets.
HAUL_GEAR
VARCHAR2(5 BYTE)
This 4 or 5 digit number represents the NMFS gear code for pelagic longline (675), prefixed by the haul number. So 12675 is the twelfth haul of this trip.
INCIDENTAL_TAKE
VARCHAR2(1 BYTE)
This variable indicates if a turtle, marine mammal, or sea bird was caught during this haul (value=1) or there was no catch of these species (Value=0).
BOUYS
VARCHAR2(4 BYTE)
Number of buoys used in the set. This variable tracks to the variable “NO. OF FLTS” on the paper data forms.
HOOKS
VARCHAR2(5 BYTE)
Number of hooks used in the set. This variable tracks to the variable “NO. OF HOOKS” on the paper data forms.
BEGIN_SET_DATE
VARCHAR2(8 BYTE)
Begin Set Date. The format is not quite straightforward. The last 4 digits are always the year, the two places preceding the year are the day of the month, although for single digit days there are no leading zeros, only a blank space. The one or two digits beginning the numeric string are the month, but this time with no space taking the place of a zero for single digit months; the single digit just starts the string. So for example October first 1979 is represented in the format 10 11979 and July 21st 1980 is represented as 7211980.
BEGIN_HAUL_DATE
VARCHAR2(8 BYTE)
Begin Haul date. The format is not quite straightforward. The last 4 digits are always the year, the two places preceding the year are the day of the month, although for single digit days there are no leading zeros, only a blank space. The one or two digits beginning the numeric string are the month, but this time with no space taking the place of a zero for single digit months; the single digit just starts the string. So for example October first 1979 is represented in the format 10 11979 and July 21st 1980 is represented as 7211980.
BS_HOUR
VARCHAR2(2 BYTE)
Hour, in 24 hour format, of the beginning of the set.
ES_HOUR
VARCHAR2(2 BYTE)
Hour, in 24 hour format, of the end of the set.
BH_HOUR
VARCHAR2(2 BYTE)
Hour, in 24 hour format, of the beginning of the haul.
EH_HOUR
VARCHAR2(2 BYTE)
Hour, in 24 hour format, of the end of the haul.
BS_LAT
VARCHAR2(4 BYTE)
Latitude at the beginning of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
BS_LON
VARCHAR2(4 BYTE)
Longitude at the beginning of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
ES_LAT
VARCHAR2(4 BYTE)
Latitude at the end of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
ES_LON
VARCHAR2(4 BYTE)
Longitude at the end of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
BH_LAT
VARCHAR2(4 BYTE)
Latitude at the beginning of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
BH_LON
VARCHAR2(4 BYTE)
Longitude at the beginning of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
EH_LAT
VARCHAR2(4 BYTE)
Latitude at the end of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
EH_LON
VARCHAR2(4 BYTE)
Longitude at the end of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
BS_TEMP
VARCHAR2(4 BYTE)
Surface water temperature in degrees F at the beginning of the set
ES_TEMP
VARCHAR2(4 BYTE)
Surface water temperature in degrees F at the end of the set
BH_TEMP
VARCHAR2(4 BYTE)
Surface water temperature in degrees F at the beginning of the haul
EH_TEMP
VARCHAR2(4 BYTE)
Surface water temperature in degrees F at the end of the haul

Child Items

No Child Items for this record.

Contact Information

No contact information is available for this record.

Please contact the owner organization (SEFSC) for inquiries on this record.

Item Identification

Title: Variables in table JLL_EFFORT
Short Name: Effort variables
Status: Completed

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
TRIP_ID VARCHAR2(8 BYTE) Trip identification number. Format is JAYYXX; so a ‘JA’ is followed by the last two digits of the trip year and then a sequential trip number, which starts at 01 for each year. So ‘JA7802’ is the second trip observed in 1978. It should be noted that this ID number appears to have been generated well after data collection; it does not appear on data sheets.
100
HAUL_GEAR VARCHAR2(5 BYTE) This 4 or 5 digit number represents the NMFS gear code for pelagic longline (675), prefixed by the haul number. So 12675 is the twelfth haul of this trip.
100
INCIDENTAL_TAKE VARCHAR2(1 BYTE) This variable indicates if a turtle, marine mammal, or sea bird was caught during this haul (value=1) or there was no catch of these species (Value=0).
100
BOUYS VARCHAR2(4 BYTE) Number of buoys used in the set. This variable tracks to the variable “NO. OF FLTS” on the paper data forms.
100
HOOKS VARCHAR2(5 BYTE) Number of hooks used in the set. This variable tracks to the variable “NO. OF HOOKS” on the paper data forms.
100
BEGIN_SET_DATE VARCHAR2(8 BYTE) Begin Set Date. The format is not quite straightforward. The last 4 digits are always the year, the two places preceding the year are the day of the month, although for single digit days there are no leading zeros, only a blank space. The one or two digits beginning the numeric string are the month, but this time with no space taking the place of a zero for single digit months; the single digit just starts the string. So for example October first 1979 is represented in the format 10 11979 and July 21st 1980 is represented as 7211980.
100
BEGIN_HAUL_DATE VARCHAR2(8 BYTE) Begin Haul date. The format is not quite straightforward. The last 4 digits are always the year, the two places preceding the year are the day of the month, although for single digit days there are no leading zeros, only a blank space. The one or two digits beginning the numeric string are the month, but this time with no space taking the place of a zero for single digit months; the single digit just starts the string. So for example October first 1979 is represented in the format 10 11979 and July 21st 1980 is represented as 7211980.
100
BS_HOUR VARCHAR2(2 BYTE) Hour, in 24 hour format, of the beginning of the set.
100
ES_HOUR VARCHAR2(2 BYTE) Hour, in 24 hour format, of the end of the set.
100
BH_HOUR VARCHAR2(2 BYTE) Hour, in 24 hour format, of the beginning of the haul.
100
EH_HOUR VARCHAR2(2 BYTE) Hour, in 24 hour format, of the end of the haul.
100
BS_LAT VARCHAR2(4 BYTE) Latitude at the beginning of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
BS_LON VARCHAR2(4 BYTE) Longitude at the beginning of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
ES_LAT VARCHAR2(4 BYTE) Latitude at the end of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
ES_LON VARCHAR2(4 BYTE) Longitude at the end of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
BH_LAT VARCHAR2(4 BYTE) Latitude at the beginning of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
BH_LON VARCHAR2(4 BYTE) Longitude at the beginning of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
EH_LAT VARCHAR2(4 BYTE) Latitude at the end of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
EH_LON VARCHAR2(4 BYTE) Longitude at the end of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.
100
BS_TEMP VARCHAR2(4 BYTE) Surface water temperature in degrees F at the beginning of the set
100
ES_TEMP VARCHAR2(4 BYTE) Surface water temperature in degrees F at the end of the set
100
BH_TEMP VARCHAR2(4 BYTE) Surface water temperature in degrees F at the beginning of the haul
100
EH_TEMP VARCHAR2(4 BYTE) Surface water temperature in degrees F at the end of the haul

Attribute Details

TRIP_ID

CC ID: 227092
Seq. Order: 1
Data Storage Type: VARCHAR2(8 BYTE)
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

Trip identification number. Format is JAYYXX; so a ‘JA’ is followed by the last two digits of the trip year and then a sequential trip number, which starts at 01 for each year. So ‘JA7802’ is the second trip observed in 1978. It should be noted that this ID number appears to have been generated well after data collection; it does not appear on data sheets.

HAUL_GEAR

CC ID: 227093
Seq. Order: 2
Data Storage Type: VARCHAR2(5 BYTE)
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

This 4 or 5 digit number represents the NMFS gear code for pelagic longline (675), prefixed by the haul number. So 12675 is the twelfth haul of this trip.

INCIDENTAL_TAKE

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

This variable indicates if a turtle, marine mammal, or sea bird was caught during this haul (value=1) or there was no catch of these species (Value=0).

BOUYS

CC ID: 227132
Seq. Order: 4
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Number of buoys used in the set. This variable tracks to the variable “NO. OF FLTS” on the paper data forms.

HOOKS

CC ID: 227133
Seq. Order: 5
Data Storage Type: VARCHAR2(5 BYTE)
Max Length: 5
Required: No
Primary Key: No
Status: Active
Description:

Number of hooks used in the set. This variable tracks to the variable “NO. OF HOOKS” on the paper data forms.

BEGIN_SET_DATE

CC ID: 227134
Seq. Order: 6
Data Storage Type: VARCHAR2(8 BYTE)
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

Begin Set Date. The format is not quite straightforward. The last 4 digits are always the year, the two places preceding the year are the day of the month, although for single digit days there are no leading zeros, only a blank space. The one or two digits beginning the numeric string are the month, but this time with no space taking the place of a zero for single digit months; the single digit just starts the string. So for example October first 1979 is represented in the format 10 11979 and July 21st 1980 is represented as 7211980.

BEGIN_HAUL_DATE

CC ID: 227135
Seq. Order: 7
Data Storage Type: VARCHAR2(8 BYTE)
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

Begin Haul date. The format is not quite straightforward. The last 4 digits are always the year, the two places preceding the year are the day of the month, although for single digit days there are no leading zeros, only a blank space. The one or two digits beginning the numeric string are the month, but this time with no space taking the place of a zero for single digit months; the single digit just starts the string. So for example October first 1979 is represented in the format 10 11979 and July 21st 1980 is represented as 7211980.

BS_HOUR

CC ID: 227136
Seq. Order: 8
Data Storage Type: VARCHAR2(2 BYTE)
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Hour, in 24 hour format, of the beginning of the set.

ES_HOUR

CC ID: 227137
Seq. Order: 9
Data Storage Type: VARCHAR2(2 BYTE)
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Hour, in 24 hour format, of the end of the set.

BH_HOUR

CC ID: 227138
Seq. Order: 10
Data Storage Type: VARCHAR2(2 BYTE)
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Hour, in 24 hour format, of the beginning of the haul.

EH_HOUR

CC ID: 227139
Seq. Order: 11
Data Storage Type: VARCHAR2(2 BYTE)
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Hour, in 24 hour format, of the end of the haul.

BS_LAT

CC ID: 227140
Seq. Order: 12
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Latitude at the beginning of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

BS_LON

CC ID: 227141
Seq. Order: 13
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Longitude at the beginning of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

ES_LAT

CC ID: 227142
Seq. Order: 14
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Latitude at the end of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

ES_LON

CC ID: 227143
Seq. Order: 15
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Longitude at the end of the set, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

BH_LAT

CC ID: 227144
Seq. Order: 16
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Latitude at the beginning of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

BH_LON

CC ID: 227145
Seq. Order: 17
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Longitude at the beginning of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

EH_LAT

CC ID: 227146
Seq. Order: 18
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Latitude at the end of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

EH_LON

CC ID: 227147
Seq. Order: 19
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Longitude at the end of the haul, in 4 digit format (first two are degrees, second two are whole minutes). A value of zero should be interpreted as a null.

BS_TEMP

CC ID: 227331
Seq. Order: 20
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Surface water temperature in degrees F at the beginning of the set

ES_TEMP

CC ID: 227332
Seq. Order: 21
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Surface water temperature in degrees F at the end of the set

BH_TEMP

CC ID: 227333
Seq. Order: 22
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Surface water temperature in degrees F at the beginning of the haul

EH_TEMP

CC ID: 227334
Seq. Order: 23
Data Storage Type: VARCHAR2(4 BYTE)
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

Surface water temperature in degrees F at the end of the haul

Catalog Details

Catalog Item ID: 27625
GUID: gov.noaa.nmfs.inport:27625
Metadata Record Created By: Larry Beerkircher
Metadata Record Created: 2015-09-30 12:50+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2021-05-06
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2022-05-06