Slide Menu
Search Help Show/Hide Menu

Item Identification

Title: CURRENT_HAUL
Short Name: CURRENT HAUL
Status: In Work
Abstract:

This table contains the transformed haul data for presentation to the AKRO catch accounting. The table is populated and maintained through a combination of NORPAC trigger code and OBSINT procedural code. The chain of events is as follows: INSERT, UPDATE - The ATL_HAUL_OBSINT_AIUDR_T adds haul primary key records to the temp_haul table. A periodic process calls the procedure execute_load_current_haul which controls the extraction and transformation of norpac.atl_haul records for insert or update into current haul. On Delete from ATL_HAUL the trigger performs a cross schema cascade delete to temp_haul and current haul.

Purpose:

Present haul data that have been loaded into production to fishery managers and vessel owners prior the the finalization of those data by debriefing

Keywords

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 2008 AND FORWARD

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None BS, AI, BSAI, GOA

Stratum Keywords

Thesaurus Keyword
UNCONTROLLED
None OBSERVER, CURRENT DATA, FISHERY STATISTICS

Physical Location

Organization: Fisheries Monitoring and Analysis
City: Seattle
State/Province: WA
Country: USA
Location Description:

Alaska Fisheries Science Center

Entity Information

Entity Type: Data Table
Active Version?: Yes
Alias: Haul
Schema Name: Obsint
Description:

This table contains the transformed haul data for presentation to the AKRO catch accounting. The table is populated and maintained through a combination of NORPAC trigger code and OBSINT procedural code. The chain of events is as follows: INSERT, UPDATE - The ATL_HAUL_OBSINT_AIUDR_T adds haul primary key records to the temp_haul table. A periodic process calls the procedure execute_load_current_haul which controls the extraction and transformation of norpac.atl_haul records for insert or update into current haul. On Delete from ATL_HAUL the trigger perfoms a cross schema cascade delete to temp_haul and current haul.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
T_TABLE VARCHAR2 Identifier of Source Table
100
Cruise NUMBER Sequence generated by Norpac and supplied to the observer as an unique identifier for a processing plant observer cruise record
100
Permit VARCHAR2 Unique Code identifying a vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau
100
VESSEL VARCHAR2 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.
100
HAUL_SEQ Number Sequence generated unique identifier for a haul record
100
TRIP_SEQ Number Sequence generated unique identifier for a trip as defined in ATL_fma_trip.
100
HAUL_DATE DATE Date of haul retrieval.
100
HAUL Number Number which is entered by the observer identifying a unique haul within a trip.
100
HAUL_PURPOSE_CODE VARCHAR2 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.
67
GEAR_TYPE Number
100
PERFORMANCE NUMBER Unique performance code for a gear type. see ATL_LOV_gear_perfomrance.
100
VESSEL_TYPE Number Unique identifier of a vessel type, see ATL_LOV_vessel_type
100
DEPLOYMENT_DATE DATE Date and time of gear deployment
100
DEPLOYMENT_LATITUDE Number Gear deployment position. In Degrees and Minutes
100
DEPLOYMENT_LONGITUDE_CONVERTED Number 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.
100
DEPLOYMENT_E_W VARCHAR2 Gear deployment position.
100
FISHING_DEPTH_FATHOMS Number Average fishing depth recorded by the observer from the vessel log.
100
BOTTOM_DEPTH_FATHOMS Number Average bottom depth recorded by the observer from the vessel log.
100
RETRIEVAL_DATE DATE Date and time of gear retrieval.
100
LOCATION VARCHAR2 Identifies whether the information in a haul is based on retrieval or delivery (as in a mother ship).
100
LATITUDE Number Retrieval location in Degrees and Minutes
100
LONGITUDE Number Retrieval location. In Degrees and Minutes
100
LONGITUDE_CONVERTED Number 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.
100
E_W VARCHAR2 Retrieval location.
100
NMFS_AREA Number This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file.
100
COBLZ_AREA VARCHAR2 This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file.
100
VESSEL_ESTIMATE Number Total catch weight in metric tons as recorded in the vessel log.
100
OFFICIAL_TOTAL_CATCH Number 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.
100
OBSERVER_ESTIMATE Number Total catch weight as estimated by the observer in kgs and converted to MT for this presentation.
100
OBSERVER_ESTIMATE_METHOD VARCHAR2 Method used to determine the observer estimated catch.
100
DENSITY Number Density used by the observer to determine the total catch weights. Recorded in kgs per m3.
100
CATCHER_BOAT_ADFGv Number If this haul was delivered to a mothership or catcher processor, this attibute records the ADFG registration number of that vessel.
100
IFQ VARCHAR2 Flag which identifies whether fishing is on an IFQ quota with the subsequent application of IFQ rules.
100
CDQ_CODE VARCHAR2 Unique AlphaNumeric code representing a CDQ or research group.
100
SKATES_IN_SET Number Number of skates deployed for longline fishing operations
100
HOOKS_PER_SKATE NUMBER 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.
100
TOTAL_HOOKS_POTS NUMBER 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.
100
HAUL_SAMPLED_BY NUMBER 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.
100
RANDOM_SAMPLE_TABLE VARCHAR2 Random Sample Reference Table code reference.
100
RANDOM_BREAK_TABLE VARCHAR2 Random Break Table identifier Currently limted to Y (es) or N(o).
100
MM_PERCENT_MONITORED NUMBER 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.
100
BIRD_DETERRENCE V Deterrence code from NORPAC bird or mammal deterance tables.
100
PROCESSOR VARCHAR2 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.
100
FISHING_START_DATE DATE 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.
100
HAUL_JOIN NUMBER Surrogate FK to atl_haul. Composed of concatenation of cruise, permit and haul_seq.
100
DATE_OF_ENTRY DATE 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.';
100
YEAR NUMBER Year is extracted from the haul rettrv_date_time field.
100
LATDD_END NUMBER Latitude decimal degrees is computed from the retrieval latitude.
100
LONDD_END NUMBER Longitude decimal degrees is computed from the retrieval longitude.
100
LATDD_START NUMBER Latitude decimal degrees is computed from the deployment latitude.
100
LONDD_START NUMBER Longitude decimal degrees is computed from the deployment longitude.
100
RETRV_LONGITUDE_SECONDS N Gear retrieval position.
100
RETRV_LATITUDE_SECONDS NUMBER Gear retrieval position.
100
DEPLOY_LATITUDE_SECONDS NUMBER Gear retrieval position.
100
ATLAS_VERSION NUMBER If this haul data was transmitted from the field. This attribute records the version of the software used.
100
DEPLOYMENT_LONGITUDE NUMBER Location of start of haul
100
HAUL_HASH VARCHAR2 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.
100
SPECIES_HASH VARCHAR2 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.
100
SALMON_HASH VARCHAR2 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.
100
FLOW_SCALE_WEIGHT N Actual weight from the flow scale reading for a haul.
100
PRESORT_SAMPLE_HASH Varchar2 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.
100
LANDING_REPORT_ID_HASH VARCHAR2 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.

Attribute Details

T_TABLE

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

Identifier of Source Table

Cruise

CC ID: 235659
Seq. Order: 5
Data Storage Type: NUMBER
Max Length: 8
Required: Yes
Primary Key: No
Precision: 8
Scale: 0
Status: Active
Description:

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

General Data Type: Integer

Permit

CC ID: 235660
Seq. Order: 10
Data Storage Type: VARCHAR2
Max Length: 6
Required: Yes
Primary Key: No
Status: Active
Description:

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

General Data Type: Character
Case Restriction: Upper

VESSEL

CC ID: 235662
Seq. Order: 15
Data Storage Type: VARCHAR2
Max Length: 6
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Character
Case Restriction: Upper

HAUL_SEQ

CC ID: 235664
Seq. Order: 20
Data Storage Type: Number
Max Length: 8
Required: No
Primary Key: No
Precision: 8
Scale: 0
Status: Active
Description:

Sequence generated unique identifier for a haul record

General Data Type: Integer

TRIP_SEQ

CC ID: 235665
Seq. Order: 25
Data Storage Type: Number
Max Length: 8
Required: No
Primary Key: No
Precision: 8
Scale: 0
Status: Active
Description:

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

General Data Type: Integer

HAUL_DATE

CC ID: 235667
Seq. Order: 30
Data Storage Type: DATE
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

Date of haul retrieval.

General Data Type: Date

HAUL

CC ID: 235668
Seq. Order: 35
Data Storage Type: Number
Max Length: 6
Required: No
Primary Key: No
Precision: 6
Scale: 0
Status: Active
Description:

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

General Data Type: Integer

HAUL_PURPOSE_CODE

CC ID: 235669
Seq. Order: 40
Data Storage Type: VARCHAR2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Character

GEAR_TYPE

CC ID: 235670
Seq. Order: 45
Data Storage Type: Number
Max Length: 2
Min Length: 2
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
General Data Type: Integer

PERFORMANCE

CC ID: 235671
Seq. Order: 50
Data Storage Type: NUMBER
Max Length: 2
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
Description:

Unique performance code for a gear type. see ATL_LOV_gear_perfomrance.

General Data Type: Integer

VESSEL_TYPE

CC ID: 235672
Seq. Order: 55
Data Storage Type: Number
Max Length: 2
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
Description:

Unique identifier of a vessel type, see ATL_LOV_vessel_type

General Data Type: Integer

DEPLOYMENT_DATE

CC ID: 235673
Seq. Order: 60
Data Storage Type: DATE
Max Length: 12
Required: No
Primary Key: No
Status: Active
Description:

Date and time of gear deployment

General Data Type: Date

DEPLOYMENT_LATITUDE

CC ID: 235674
Seq. Order: 65
Data Storage Type: Number
Max Length: 4
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Gear deployment position. In Degrees and Minutes

General Data Type: Integer

DEPLOYMENT_LONGITUDE_CONVERTED

CC ID: 235675
Seq. Order: 70
Data Storage Type: Number
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Number

DEPLOYMENT_E_W

CC ID: 235676
Seq. Order: 75
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Gear deployment position.

General Data Type: Character
Case Restriction: Upper

FISHING_DEPTH_FATHOMS

CC ID: 235677
Seq. Order: 80
Data Storage Type: Number
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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

General Data Type: Integer

BOTTOM_DEPTH_FATHOMS

CC ID: 235678
Seq. Order: 85
Data Storage Type: Number
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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

RETRIEVAL_DATE

CC ID: 235679
Seq. Order: 90
Data Storage Type: DATE
Max Length: 12
Required: No
Primary Key: No
Status: Active
Description:

Date and time of gear retrieval.

LOCATION

CC ID: 235680
Seq. Order: 95
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

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

General Data Type: Character

LATITUDE

CC ID: 235681
Seq. Order: 100
Data Storage Type: Number
Max Length: 4
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Retrieval location in Degrees and Minutes

General Data Type: Integer

LONGITUDE

CC ID: 235682
Seq. Order: 105
Data Storage Type: Number
Max Length: 5
Required: No
Primary Key: No
Precision: 5
Scale: 0
Status: Active
Description:

Retrieval location. In Degrees and Minutes

General Data Type: Integer

LONGITUDE_CONVERTED

CC ID: 235683
Seq. Order: 110
Data Storage Type: Number
Max Length: 7
Required: No
Primary Key: No
Precision: 7
Scale: 0
Status: Active
Description:

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.

E_W

CC ID: 235684
Seq. Order: 115
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Retrieval location.

General Data Type: Character

NMFS_AREA

CC ID: 235685
Seq. Order: 120
Data Storage Type: Number
Max Length: 3
Required: No
Primary Key: No
Precision: 3
Scale: 0
Status: Active
Description:

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

General Data Type: Integer

COBLZ_AREA

CC ID: 235686
Seq. Order: 125
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

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

General Data Type: Character
Case Restriction: Upper
Allowed Values: Y, N, NULL

VESSEL_ESTIMATE

CC ID: 235687
Seq. Order: 130
Data Storage Type: Number
Max Length: 6
Required: No
Primary Key: No
Precision: 6
Scale: 2
Status: Active
Description:

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

OFFICIAL_TOTAL_CATCH

CC ID: 235688
Seq. Order: 135
Data Storage Type: Number
Max Length: 10
Required: No
Primary Key: No
Precision: 10
Scale: 2
Status: Active
Description:

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.

OBSERVER_ESTIMATE

CC ID: 235690
Seq. Order: 140
Data Storage Type: Number
Max Length: 10
Required: No
Primary Key: No
Precision: 10
Scale: 2
Status: Active
Description:

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

OBSERVER_ESTIMATE_METHOD

CC ID: 235694
Seq. Order: 145
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Method used to determine the observer estimated catch.

DENSITY

CC ID: 235695
Seq. Order: 150
Data Storage Type: Number
Max Length: 10
Required: No
Primary Key: No
Precision: 10
Scale: 2
Status: Active
Description:

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

CATCHER_BOAT_ADFGv

CC ID: 235697
Seq. Order: 155
Data Storage Type: Number
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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

IFQ

CC ID: 235699
Seq. Order: 160
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

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

Null Value: Y, N, NULL
Null Value Meaning:

Unknown

CDQ_CODE

CC ID: 235700
Seq. Order: 165
Data Storage Type: VARCHAR2
Max Length: 3
Required: No
Primary Key: No
Status: Active
Description:

Unique AlphaNumeric code representing a CDQ or research group.

SKATES_IN_SET

CC ID: 235959
Seq. Order: 170
Data Storage Type: Number
Max Length: 6
Required: No
Primary Key: No
Precision: 6
Scale: 2
Status: Active
Description:

Number of skates deployed for longline fishing operations

HOOKS_PER_SKATE

CC ID: 235961
Seq. Order: 175
Data Storage Type: NUMBER
Max Length: 6
Required: No
Primary Key: No
Precision: 6
Scale: 2
Status: Active
Description:

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_HOOKS_POTS

CC ID: 235962
Seq. Order: 180
Data Storage Type: NUMBER
Max Length: 6
Required: No
Primary Key: No
Precision: 6
Scale: 2
Status: Active
Description:

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.

HAUL_SAMPLED_BY

CC ID: 235970
Seq. Order: 185
Data Storage Type: NUMBER
Max Length: 8
Required: No
Primary Key: No
Precision: 8
Scale: 0
Status: Active
Description:

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.

General Data Type: INTEGER

RANDOM_SAMPLE_TABLE

CC ID: 235971
Seq. Order: 190
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

Random Sample Reference Table code reference.

RANDOM_BREAK_TABLE

CC ID: 235972
Seq. Order: 195
Data Storage Type: VARCHAR2
Max Length: 1
Required: No
Primary Key: No
Status: Active
Description:

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

General Data Type: Character
Case Restriction: Upper
Allowed Values: Y, N, NULL

MM_PERCENT_MONITORED

CC ID: 235975
Seq. Order: 200
Data Storage Type: NUMBER
Max Length: 3
Required: No
Primary Key: No
Precision: 3
Scale: 0
Status: Active
Description:

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.

General Data Type: INTEGER

BIRD_DETERRENCE

CC ID: 235976
Seq. Order: 205
Data Storage Type: V
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Deterrence code from NORPAC bird or mammal deterance tables.

PROCESSOR

CC ID: 235977
Seq. Order: 210
Data Storage Type: VARCHAR2
Max Length: 6
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Character

FISHING_START_DATE

CC ID: 235978
Seq. Order: 215
Data Storage Type: DATE
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Date

HAUL_JOIN

CC ID: 235979
Seq. Order: 220
Data Storage Type: NUMBER
Max Length: 26
Required: No
Primary Key: No
Precision: 26
Scale: 0
Status: Active
Description:

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

General Data Type: Integer

DATE_OF_ENTRY

CC ID: 235980
Seq. Order: 225
Data Storage Type: DATE
Max Length: 8
Required: No
Primary Key: No
Status: Active
Description:

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.';

General Data Type: Date

YEAR

CC ID: 235981
Seq. Order: 230
Data Storage Type: NUMBER
Max Length: 4
Min Length: 4
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Year is extracted from the haul rettrv_date_time field.

General Data Type: Integer

LATDD_END

CC ID: 235982
Seq. Order: 235
Data Storage Type: NUMBER
Max Length: 7
Required: No
Primary Key: No
Precision: 7
Scale: 5
Status: Active
Description:

Latitude decimal degrees is computed from the retrieval latitude.

General Data Type: Number

LONDD_END

CC ID: 235983
Seq. Order: 240
Data Storage Type: NUMBER
Max Length: 8
Required: No
Primary Key: No
Precision: 8
Scale: 5
Status: Active
Description:

Longitude decimal degrees is computed from the retrieval longitude.

General Data Type: Number

LATDD_START

CC ID: 235984
Seq. Order: 245
Data Storage Type: NUMBER
Max Length: 7
Required: No
Primary Key: No
Precision: 7
Scale: 5
Status: Active
Description:

Latitude decimal degrees is computed from the deployment latitude.

General Data Type: Number

LONDD_START

CC ID: 235985
Seq. Order: 250
Data Storage Type: NUMBER
Max Length: 8
Required: No
Primary Key: No
Precision: 8
Scale: 5
Status: Active
Description:

Longitude decimal degrees is computed from the deployment longitude.

RETRV_LONGITUDE_SECONDS

CC ID: 235986
Seq. Order: 255
Data Storage Type: N
Max Length: 2
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
Description:

Gear retrieval position.

General Data Type: Integer

RETRV_LATITUDE_SECONDS

CC ID: 235987
Seq. Order: 260
Data Storage Type: NUMBER
Max Length: 2
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
Description:

Gear retrieval position.

General Data Type: Integer

DEPLOY_LATITUDE_SECONDS

CC ID: 235988
Seq. Order: 265
Data Storage Type: NUMBER
Max Length: 2
Required: No
Primary Key: No
Precision: 2
Scale: 0
Status: Active
Description:

Gear retrieval position.

General Data Type: Integer

ATLAS_VERSION

CC ID: 235989
Seq. Order: 270
Data Storage Type: NUMBER
Max Length: 3
Required: No
Primary Key: No
Precision: 3
Scale: 2
Status: Active
Description:

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

General Data Type: Number

DEPLOYMENT_LONGITUDE

CC ID: 235990
Seq. Order: 275
Data Storage Type: NUMBER
Max Length: 23
Required: No
Primary Key: No
Status: Active
Description:

Location of start of haul

General Data Type: Number

HAUL_HASH

CC ID: 235991
Seq. Order: 280
Data Storage Type: VARCHAR2
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Character

SPECIES_HASH

CC ID: 235992
Seq. Order: 285
Data Storage Type: VARCHAR2
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Character

SALMON_HASH

CC ID: 235993
Seq. Order: 290
Data Storage Type: VARCHAR2
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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.

General Data Type: Character

FLOW_SCALE_WEIGHT

CC ID: 235994
Seq. Order: 295
Data Storage Type: N
Max Length: 10
Required: No
Primary Key: No
Precision: 10
Scale: 3
Status: Active
Description:

Actual weight from the flow scale reading for a haul.

General Data Type: Number

PRESORT_SAMPLE_HASH

CC ID: 345611
Seq. Order: 296
Data Storage Type: Varchar2
Max Length: 32
Required: No
Primary Key: No
Status: Active
Description:

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.

Case Restriction: Upper
Display Example: EE3CACFD295AAB8A5DD7D975B358F620
Null Value: null set

LANDING_REPORT_ID_HASH

CC ID: 782190
Data Storage Type: VARCHAR2
Required: No
Primary Key: No
Status: Active
Description:

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.

Catalog Details

Catalog Item ID: 28148
GUID: gov.noaa.nmfs.inport:28148
Metadata Record Created By: Julie A Blair
Metadata Record Created: 2015-10-23 17:39+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:11+0000
Metadata Record Published: 2016-08-23
Owner Org: AFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2016-08-23
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2017-08-23