CURRENT_HAUL

Identifier of Source Table

Sequence generated by Norpac and supplied to the observer as an unique identifier for a processing plant observer cruise record

Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau

VessPlnt code from old NORPAC system plus new vessels recorded in ATL_LOV_Vessel. This code may ultimately be retired, but is essential to the transitional ETL from Atlas to Inseason and Domestic.

Sequence generated unique identifier for a haul record

Sequence generated unique identifier for a trip as defined in ATL_fma_trip.

Date of haul retrieval.

Number which is entered by the observer identifying a unique haul within a trip.

Haul data may be utilized for catch accounting, stock assessment, or for various special projects. This field is entered by the observer and not validated by ATLAS. Validation is performed when loaded into the production NORPAC data set.

Unique performance code for a gear type. see ATL_LOV_gear_perfomrance.

Unique identifier of a vessel type, see ATL_LOV_vessel_type

Date and time of gear deployment

Gear deployment position. In Degrees and Minutes

The conversion of longitude is required of values to the east of the 180th meridian. The configuration within Oracle Spatial uses a 360 degree globe - 179 E must therefore be submitted as 181. The calling program must, as in the conversion to decimal degrees submit latitude to the east of the 180th meridian as a negative number.

Gear deployment position.

Average fishing depth recorded by the observer from the vessel log.

Average bottom depth recorded by the observer from the vessel log.

Date and time of gear retrieval.

Identifies whether the information in a haul is based on retrieval or delivery (as in a mother ship).

Retrieval location in Degrees and Minutes

Retrieval location. In Degrees and Minutes

Retrieval location. The conversion of longitude is required of values to the east of the 180th meridian. The configuration within Oracle Spatial uses a 360 degree globe - 179 E must therefore be submitted as 181. The calling program must, as in the conversion to decimal degrees submit latitude to the east of the 180th meridian as a negative number.

Retrieval location.

This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file.

This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file.

Total catch weight in metric tons as recorded in the vessel log.

Total catch weight as computed from the sum of the extrapolate species composition records. For trawl fisheries in the GOA, prohibited species census data may be back apportioned to hauls which constitute an offload if one exists. OTC will then be computed as the sum of the extrapolated species plus the sum of the back apportioned species.

Total catch weight as estimated by the observer in kgs and converted to MT for this presentation.

Method used to determine the observer estimated catch.

Density used by the observer to determine the total catch weights. Recorded in kgs per m3.

If this haul was delivered to a mothership or catcher processor, this attibute records the ADFG registration number of that vessel.

Flag which identifies whether fishing is on an IFQ quota with the subsequent application of IFQ rules.

Unknown

Unique AlphaNumeric code representing a CDQ or research group.

Number of skates deployed for longline fishing operations

Number of hooks per skate for longline fishing usually calculated as the average number of hooks per segment from the atl_haul_hook_count table.

Total number of hooks deployed for this haul, usually calculated as the average number of hooks per segment from the atl_haul_hook_count table * the number of skates in set. Or in the case of a pot fishery the total number of pots deployed in a haul.

Identifies where a haul is sampled by an observer and in some cases by which observer. The observer of a haul is not necessarily the primary observer recorded for a cruise.

Random Sample Reference Table code reference.

Random Break Table identifier Currently limted to Y (es) or N(o).

Percentage of time for this haul where marine mammal monitoring occurred. For fixed gear deployments the valid values are anywhere in the range. For mobile gear deployments the values may be either 0 or 100.

Deterrence code from NORPAC bird or mammal deterance tables.

Processor is computed by atl_utilities, and returns the shore plant processor code for catcher vessels who have an offload, and the processor permit for catcher processors and motherships.

Fishing start date is defined as the first haul deployment of a trip. If the deployment date is null due to unverifiable observer data then the trip start date is used; if null the default is a mandatory value haul retrieval date.

Surrogate FK to atl_haul. Composed of concatenation of cruise, permit and haul_seq.

Date of entry is now (2010) recorded when a haul is loaded into the Norpac data set. In the case that that value is null then it is computed from the latest load date recorded in atl_record_status.';

Year is extracted from the haul rettrv_date_time field.

Latitude decimal degrees is computed from the retrieval latitude.

Longitude decimal degrees is computed from the retrieval longitude.

Latitude decimal degrees is computed from the deployment latitude.

Longitude decimal degrees is computed from the deployment longitude.

Gear retrieval position.

Gear retrieval position.

Gear retrieval position.

If this haul data was transmitted from the field. This attribute records the version of the software used.

Location of start of haul

The haul hash is utilized by AKRO to identify changes to a haul record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

The species hash is utilized by AKRO to identify changes to a species composition record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

The salmon hash is utilized by AKRO to identify changes to a salmon retention record. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

Actual weight from the flow scale reading for a haul.

The presort hash is utilized by AKRO to identify changes to presort records. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.

The landing report id hash is utilized by AKRO to identify changes to the list of eLanding report ids associated with a haul. The hash is created every time that a record is created or updated. Only critical data columns are referenced and change is denoted by a change in the hash value.