| Table name |
Definition |
| NORPAC.DOMESTIC_HAUL |
Information associated with unique fishing events of gear deployment and
retrieval. |
| Column name |
Type |
Definition |
| HAUL_JOIN |
number(9,0) |
An assigned, unique number (up to nine digits) that uniquely identifies each
haul/set associated with vessel data. NORPAC.DOMESTIC_HAUL.HAUL_JOIN links a single haul record to records in the domestic
tables for data on species composition, length, age, marine mammal, and viability interactions. |
| CRUISE |
number(8,0) |
A unique five-digit number assigned to the observer for the length of their
contract period. This number alone identifies and groups a set of observer information. |
| VESSEL |
varchar2(4) |
A unique four-digit, alpha-numeric code identifying each vessel that
contracts for observer coverage. All vessel codes begin with the alpha code A, followed by a three-digit
number, or for plants, the codes begin with the alpha code P, followed by a three-digit number. |
| HAUL_DATE |
date |
The date of gear retrieval in Alaska Local Time; for trawls, the date that the
retrieval of the net began, i.e., when the winding of the cables began, and the net left the fishing level.
Format is stored in the database as DD-MON-YY format (i.e., 15-MAR-96), and displayed as YYMMDD HH:MI:SS
(i.e., 960315 00:00:00). |
| HAUL |
number(4,0) |
A unique number which identifies a specific occurrence of net, pot, longline
or jig fishing effort. Additionally, a day in which a vessel was on grounds is occasionally recorded with a haul number
of 0 (zero) if no codend, longline set, pot group retrievals or jigging sessions were begun. |
| GEAR_TYPE |
number(2,0) |
A one- or two-digit numeric code that indicates the kind of fishing gear used by
the vessel, where: 1 = non-pelagic trawl, 2 = pelagic trawl, 3 = unknown or mixed trawl, 4 = pair trawl,
5 = shrimp trawl, 6 = pot or trap, 7 = jig, 8 = longline, 9 = gill net, and 10 = Scottish seine. |
| PERFORMANCE |
number(2,0) |
A one-digit numeric code that indicates how well the fishing device operated,
where: 1 = no problem, 2 = crab pot in haul, 3 = net hung up, 4 = ripped net, 5 =an unspecified problem,
6 = groundline cut or lost one of following: codend, entire net, longline, jig, or pot gear,
7 = sea lion predation, 8 = killer whale predation, 9 = shortwiring. |
| VESSEL_TYPE |
number(2,0) |
A one-digit numeric code that indicates whether the vessel processes fish or
delivers it to a processing plant where: 1 = a catcher processor vessel, 2 = a mothership or a ship
that receives unsorted codends from other vessels, 3 = a catcher only vessel that delivers unprocessed fish
to a shoreside or floating plant or vessel, 4 = a mothership that receives sorted codends, 5 = a vessel
that sells the majority of their catch over the side to other fishing vessels who will utilize the fish
for bait, 6 = vessels that discard all catch from a haul; would be used for codend dumping of an entire
haul (added January 2004). |
| LOCATION |
varchar2(1) |
A one-digit alpha code that indicates what type of fishing activity occurred
at the latitude and longitude recorded. R = the position of the vessel when the retrieval of the haul/set
began, D = the position of the vessel when a delivery was completed to a mothership, N = the
position of the vessel at noon (Alaska Local Time) on a day when no fishing took place and the vessel was
not in port, S = the position of the vessel when gear reached fishing depth and there was no other available
information about the haul/set. |
| LATITUDE |
number(5,0) |
A four-digit number recorded in degrees and minutes north. The geographical
position where the gear retrieval began, or, on days when no fishing occurred, the position of
the vessel at noon (Alaska Local Time), or, for a mothership receiving a delivery, the delivery location. |
| LONGITUDE |
number(5,0) |
A five-digit number recorded in degrees and minutes. The geographical position
where the gear retrieval began, or, on days when no fishing occurred, the position of the vessel
at noon (Alaska Local Time), or, for a mothership receiving a delivery, the delivery location. |
| GENERIC_AREA |
number(3,0) |
A three-digit number representing NORPAC database management subareas which, in
most cases, are similar to NPFMC management areas. This field was replaced by NMFS_AREA and was no longer stored after 2002. |
| DEPLOYMENT_DATE |
date |
The date and time of gear deployment in Alaska Local Time; for trawls, the time
that the net reached fishing depth. Format is stored in the database as DD-MON-YY format (i.e., 15-MAR-96),
and displayed as YYMMDD HH:MI:SS (i.e., 960315 00:00:00). |
| DEPLOYMENT_LATITUDE |
number(4,0) |
A four-digit number recorded in degrees and minutes north. The geographical
position where the gear deployment occurred. |
| DEPLOYMENT_LONGITUDE |
number(5,0) |
A five-digit number recorded in degrees and minutes. The geographical
position where the gear deployment occurred. |
| FISHING_DEPTH |
number(4,0) |
Not recorded for longliners or pot vessels, this is the average fishing depth at which fishing took place, in fathoms, prior to
2004. Starting in 2004, units can be in fathoms or meters, indicated by the field, FISHING_DEPTH_F_M. If a data
user would like to compare pre-2004 depth data to post-2003 depth data, they could use only the
fishing_depth_fathoms columns for post-2003 data to ensure that they are always looking at data in fathoms. |
| BOTTOM_DEPTH |
number(5,0) |
The average of the lowest points on the ocean floor where fishing took place.
This is the only depth recorded for longline or pot vessels. Unit of measure was fathoms prior to 2004. Starting in 2004, units can be in fathoms or meters, indicated by the
field, BOTTOM_DEPTH_F_M. If a data user would like to compare pre-2004 depth data to post-2003
depth data, they could use only the bottom_depth_fathoms columns for post-2003 data to ensure that they
are always looking at data in fathoms. |
| VESSEL_ESTIMATE |
number(6,2) |
Beginning in 1995, the estimate of the catch entered by the officers of the
ship in the NMFS fishing log of the vessel, recorded to one-hundredth of a metric ton. |
| OFFICIAL_TOTAL_CATCH |
number(6,2) |
Total catch weight for the set or haul, including both retained and discarded
species, and recorded to the nearest one-hundredth of a metric ton. |
| OBSERVER_ESTIMATE |
number(6,2) |
Estimate of total catch for the set or haul made by the observer, recorded to
the nearest one-hundredth of a metric ton. |
| OBSERVER_ESTIMATE_METHOD |
varchar2(1) |
Beginning in 1995, a one-digit alpha code identifying whether the
volumetric estimate was performed using a bin volume (B) or a codend volume (C). |
| DENSITY |
number(3,2) |
Beginning in 1995, the density used in the calculation of the total catch
estimate by the observer, in metric tons per cubic meter, carried to two decimal places. |
| SKATES_IN_SET |
number(4,0) |
The number of skates in a set. |
| HOOKS_PER_SKATE |
number(4,0) |
The average number of hooks in a skate. |
| TOTAL_HOOKS_POTS |
number(6,0) |
For longliners, this is the total number of hooks in the set. For pot vessels,
this is the total number of pots in a set, i.e., the number of pots or group of pots in the set that were
retrieved. For jig boats, this is the number of jig machines being used. |
| HAUL_SAMPLED_BY |
number(5,0) |
A numeric code indicating which observer sampled a haul: 0 = not sampled,
9 = sampled by unknown. In addition, in years 2000 through 2003, primary and secondary observers
were differentiated: 1 = sampled by lone or lead observer, 2 = sampled by second observer. Beginning part way through 2003,
the sampling observer's cruise number was entered for each sampled haul. |
| RANDOM_SAMPLE_TABLE |
varchar2(1) |
A one-digit alpha code indicating if the haul was supposed to be sampled according
to the sampling table: n = off haul, y = on haul, x = table not used. |
| RANDOM_BREAK_TABLE |
varchar2(1) |
A one-digit alpha code indicating if the haul was supposed to be sampled according
to the break table: y = on break table, n = off break table or not using the table. |
| MM_PERCENT_MONITORED |
number(3,0) |
A three-digit numeric code identifying the percentage of the codend (trawlers
only), or of the set (longliners only), that was monitored for marine mammals, beginning in 1992. |
| MM_MONITORED_RANDOM |
varchar2(1) |
A one-digit alpha code, N = the haul was not randomly monitored for marine
mammals, Y = the haul was randomly monitored for marine mammals. |
| BIRD_DETERRENCE |
varchar2(2) |
An alpha-numeric code indicating the method of bird deterrence recorded by a longline vessel: 0 = no streamer; 1 = paired streamer line; 2 = single streamer line; 3 = lining tube and/or line
shooter; 4 = any combination of the above; 5 = buoy bag, bird bag, or other float device; 9 = no device used;
12 = bird streamer line; x = data not checked for 2003; n = observer did not check deterrence device.
|
| BIRD_VERIFICATION |
varchar2(1) |
A one-digit code indicating if the observer's observation concurred with the
vessel's recorded deterrence method in the vessel logbook: 1 = No, observer did not check the bird deterrence
gear during the set, 2 = Yes, the observer checked, and concurred with the vessel's logbook record, 3 = Yes,
the observer did check the deterrence gear, but the observer's observation did not concur with the
vessel's logbook record. |
| IFQ |
varchar2(1) |
A Y/N value indicating whether the haul or set was designated a halibut or
sablefish IFQ haul. |
| CDQ_CODE |
varchar2(3) |
Beginning in 1995, contains the letter 'C' and the last two digits of CDQ
number of the vessel, e.g., C51. |
| CATCHER_BOAT_ADFG |
number(6,0) |
If a vessel carrying an observer receives a delivery from another vessel,
this field contains the Alaska Department of Fish and Game (ADF&G) vessel code number of the delivering
vessel. |
| PERMIT |
number(5,0) |
Beginning in 1997, the last four digits of the Alaskan permit number of the
vessel. |
| PROCESSOR |
varchar2(6) |
Beginning in 1997, the processor code of the vessel. NORPAC.PROCESSOR provides the definitions. |
| FISHING_START_DATE |
date |
The date a catcher boat made the first tow of a trip. |
| DURATION |
number(5,0) |
For longline or pot vessels, the time interval from the time that the first part of
the line/pot-group was set until the time that the last of the line/pot-group was retrieved (also known as
soak time). For trawlers, duration is the length of time during which the net was at fishing level. Duration
is usually the difference between the DEPLOYMENT_DATE time and the RETRIEVAL_DATE time, but in some
cases, if the vessel lowered and raised the net several times during one haul, the duration can be less
than the difference. Recorded in minutes for all vessels. |
| YEAR |
number(4,0) |
A four-digit number identifying the year in which the gear retrieval of the haul
began or in which the noon position occurred. |
| DATE_OF_ENTRY |
date |
Date that data entered the database system. |
| ADFG_AREA |
number(6,0) |
Collected prior to 1995, a six-digit ADFG statistical area for the recorded
position. |
| SPEED |
number(3,1) |
Average towing speed of the vessel during the tow, recorded to the tenth of a
knot. Recorded from the vessel logbook. |
| RETAINED_CATCH |
number(6,2) |
Collected prior to 1994, the amount of catch (in metric tons), that was retained
by the vessel, recorded to the nearest one-hundredth of a metric ton. Retained means the weight of catch, in
round weight equivalents, that was not discarded by the vessel. |
| RETRIEVAL_DATE |
date |
The date and time of gear retrieval in Alaska Local Time; for trawls, the time
that the retrieval of the net began, i.e., when the winding of the cables began, and the net left the fishing
level. Format is stored in the database as DD-MON-YY format (i.e., 15-MAR-96), and displayed as
YYMMDD HH:MI:SS (i.e., 960315 00:00:00). |
| SHAPE |
sdo_geometry |
Geographical Information System (GIS) format for storing the location
information of the gear retrieval location. The nontopological geometry and attribute
information for the location of the haul/set is stored as a shape comprising a set of vector coordinates.
This file format is used in ArcView software. |
| NMFS_AREA |
number(3,0) |
A three-digit number representing statistical and reporting areas used by
National Marine Fisheries Service. |
| LATDD_START |
number(7,5) |
The decimal equivalent of 'deployment_latitude', the geographical location of
the gear deployment described above. |
| LATDD_END |
number(7,5) |
The decimal equivalent of 'latitude', the geographical location of the gear
retrieval described above. |
| LONDD_START |
number(8,5) |
The decimal equivalent of 'deployment_longitude', the geographical location of
the gear deployment described above. |
| LONDD_END |
number(8,5) |
The decimal equivalent of 'longitude', the geographical location of the gear
retrieval described above. |
| COBLZ_AREA |
varchar2(1) |
A yes/no field (Y = yes, N = no) indicating whether or not the gear retrieval
location was within the Bering Sea and Aleutian Islands region's Chionoecetes opilio Crab Bycatch Limitation
Zone (COBLZ). The COBLZ is an area defined as that portion of the Bering Sea Subarea north of 56N30'
N. lat. that is west of a line connecting the following coordinates in the order listed: 56N 30' N. lat.
165N 00' W. long. 58N 00' N. lat. 165N 00' W. long. 59N 30' N. lat. 170N 00' W. long. and north along
170N 00' W. long. to its intersection with the U.S.-Russia Boundary. |
| CREATE_DATE |
date |
Date record was inputted into database. |
| CREATED_BY |
varchar2(30) |
Person who loaded data into database. |
| LAST_UPDATE_DATE |
date |
Date data record was last altered. First entered in December 2003. |
| LAST_UPDATED_BY |
varchar2(30) |
Person who last altered data record. First entered in December 2003. |
| ATLAS_VERSION |
number(4,0) |
Version number of the 'at-sea' software used for data input and transmission.
First entered in 2004. |
| SEABIRD_SAMPLE_TYPE |
varchar2(1) |
A one-digit alpha code reflecting the sample size used to look for seabirds in
a trawl haul: W: Whole haul sampled for seabirds. P: Partial haul sampled for seabirds. B: Basket sampled
for seabirds. This column is blank for unsampled hauls. |
| E_W |
varchar2(1) |
A one-alpha digit code reflecting the raw data longitude of the gear retrieval
location, whether east ('E') or west ('W') of 180 degrees longitude. |
| DEPLOYMENT_E_W |
varchar2(1) |
A one-digit alpha code reflecting the raw data longitude of the gear deployment
location, whether east ('E') or west ('W') of 180 degrees longitude. |
| FISHING_DEPTH_F_M |
varchar2(1) |
A one-digit alpha code reflecting the units of fishing depth; 'F' for fathoms,
'M' for meters. |
| LONGITUDE_CONVERTED |
number(5,0) |
A five-digit number recorded in degrees and minutes. For a longitude east (E) of the 0 degree longitude, the longitude is subtracted
from 359 degrees 60 minutes. Value is always positive. For example, if the longitude is 174 degrees,
46 minutes E, then the longitude_converted = (359 degrees, 60 minutes) - (174 degrees, 46 minutes)
= 185 degrees, 14 minutes. |
| DEPLOYMENT_LONGITUDE_CONVERTED |
number(5,0) |
A five-digit number recorded in degrees and minutes. For a deployment_longitude east (E) of the 0 degree longitude, the longitude is
subtracted from 359 degrees 60 minutes. Value is always positive. For example, if the deployment_longitude
is 174 degrees, 46 minutes E, then the longitude_converted = (359 degrees, 60 minutes) - (174 degrees,
46 minutes) = 185 degrees, 14 minutes. |
| FISHING_DEPTH_FATHOMS |
number(4,0) |
Not recorded for longliners or pot vessels. It should be noted that if the observer recorded the fishing_depth in meters,
the fishing_depth was converted to fathoms by the database and stored in this column. Therefore, if a data
user would like to compare pre-2004 depth data (which is only in fathoms) to post-2003 depth data (which is
in fathoms or meters), they could use only the fishing_depth_fathoms column for post-2003 data to ensure
that they are always looking at data in fathoms. |
| BOTTOM_DEPTH_FATHOMS |
number(5,0) |
BOTTOM_DEPTH and BOTTOM_DEPTH_FATHOMS are the only depths recorded for longliners and pot vessels. It should be noted that if the observer recorded the bottom_depth in meters, the bottom_depth was converted to fathoms by the database and stored in the BOTTOM_DEPTH_FATHOMS column. Therefore, if a data user would like to compare pre-2004 depth data (which is only in fathoms) to post-2003 depth data (which is in fathoms or meters), they could use only the bottom_depth_fathoms column for post-2003 data to ensure that they are always looking at data in fathoms. |
| SEQUENCE_NUMBER |
number(6,0) |
A generated field for internal use only. |
|
