Table: DEBRIEFED_HAUL
Entity (ENT) | Alaska Fisheries Science Center (AFSC)GUID: gov.noaa.nmfs.inport:10659 | Updated: August 9, 2022 | Published / External
-
View As
- Full List View
- Printable Form
- EXPORTS
- InPort XML
- View in Hierarchy
Summary
The debriefed haul table was created as a successor to the debriefed haul materialized view. The table is a bridge object between the Domestic data (pre 2008) and the ATL data (2008 onwards) As such, refinements to the structure and statistical reliability realized in the redevelopment of Norpac are lost. The use of this table is primarily for status of stocks authors who require a longitudinal view of observer data.
DescriptionThe debriefed haul table was created as a successor to the debriefed haul materialized view. The table is a bridge object between the Domestic data (pre 2008) and the ATL data (2008 onwards) As such, refinements to the structure and statistical reliability realized in the redevelopment of Norpac are lost. The use of this table is primarily for status of stocks authors who require a longitudinal view of observer data.
Entity Information
Entity Type
Data Table
Data Attribute / Type | Description |
---|---|
T_TABLE
VARCHAR2 |
Identifier of Source Table |
CRUISE
NUMBER |
Sequence generated by Norpac and supplied to the observer as an unique identifier for an observer cruise record. |
PERMIT
VARCHAR2 |
Unique Code identifying a Vessel or Processor - inherited from the NORPAC data set and created by the RAM division in Juneau. |
VESSEL
VARCHAR2 |
Alpha Numeric code from ATL_Lov_Vessel table, which identifies the vessel. |
HAUL_SEQ
NUMBER |
Sequence generated unique identifier for a haul record |
HAUL_JOIN
NUMBER |
This is a uniquie identifier of a haul record composed by concatenation of cruise, permit and haul_seq. For domestic table records this is a sequence generated unique identifier for a haul. |
TRIP_SEQ
NUMBER |
Sequence generated unique identifier for a trip as defined in ATL_fma_trip. |
TRIP_JOIN
NUMBER |
Surrogate FK to haul, It is a unique identifier of a trip record created by concatenating cruise, permit, and trip_seq (TO_NUMBER ( t.cruise||LPAD (t.permit, 6,'0')||LPAD (t.trip_seq, 9, '0')) AS trip_join) |
HAUL_DATE
DATE |
Date of haul retrieval. |
HAUL
NUMBER |
Number which is entered by the observer identifying a unique haul within a trip. |
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. |
GEAR_TYPE
NUMBER |
Numeric value from Norpac Domestic Gear or atl_lov_gear_type that combined with the Form defines the unique identifier for a gear record. |
PERFORMANCE
NUMBER |
Unique performance code for a gear type. see ATL_LOV_gear_perfomrance. |
VESSEL_TYPE
NUMBER |
Unique identifier of a vessel type, see ATL_LOV_vessel_type |
DEPLOYMENT_DATE
DATE |
Date and time of gear deployment |
DEPLOY_LATITUDE
NUMBER |
Gear deployment position. |
DEPLOY_LONGITUDE
NUMBER |
Gear deployment position |
DEPLOY_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. |
DEPLOY_LONGITUDE_SECONDS
NUMBER |
Gear deployment position. |
DEPLOY_LATITUDE_SECONDS
NUMBER |
Gear deployment position. |
DEPLOY_E_W
VARCHAR2 |
Gear deployment position. |
FISHING_DEPTH_FATHOMS
NUMBER |
Average fishing depth recorded by the observer from the vessel log. |
BOTTOM_DEPTH_FATHOMS
NUMBER |
Average bottom depth recorded by the observer from the vessel log. |
RETRIEVAL_DATE
DATE |
Date and time of gear retrieval. |
DURATION_IN_MIN
NUMBER |
Duration of a haul calculated in minutes. |
LOCATION
VARCHAR2 |
Identifies whether the information in a haul is based on retrieval or delivery (as in a mother ship). |
RETRV_LATITUDE
NUMBER |
Retrieval location. |
RETRV_LONGITUDE
NUMBER |
Retrieval location. |
RETRV_LONGITUDE_SECONDS
NUMBER |
Gear retrieval position. |
RETRV_LATITUDE_SECONDS
NUMBER |
Gear retrieval position. |
RETRV_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. |
RETRV_E_W
VARCHAR2 |
Retrieval location. |
GENERIC_AREA
NUMBER |
This attirbute is no longer collected, but is retained for the domestic data set. |
NMFS_AREA
NUMBER |
This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file. |
COBLZ_AREA
VARCHAR2 |
This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file. |
VESSEL_ESTIMATE
NUMBER |
Total catch weight in metric tons as recorded in the vessel log. |
OFFICIAL_TOTAL_CATCH
NUMBER |
Total catch weight as estimated by the observer in kgs and converted to MT for this presentation. |
OBSERVER_ESTIMATE
NUMBER |
Total catch weight as estimated by the observer in kgs and converted to MT for this presentation. |
OBSERVER_ESTIMATE_METHOD
VARCHAR2 |
Method used to determine the observer estimated catch. |
DENSITY
NUMBER |
Density used by the observer to determine the total catch weights. Recorded in kgs per m3. |
CATCHER_BOAT_ADFG
NUMBER |
If this haul was delivered to a mothership or catcher processor, this attibute records the adfg negistration number of that vessel. |
IFQ
VARCHAR2 |
Flag which identifies whether fishing is on an IFQ quota with the subsequent application of IFQ rules. |
CDQ_CODE
VARCHAR2 |
Unique AlphaNumeric code representing a CDQ or research group. |
SKATES_IN_SET
NUMBER |
Number of skates for longline fishing. |
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. |
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. |
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. |
RANDOM_SAMPLE_TABLE
VARCHAR2 |
Random Sample Reference Table code reference. |
RANDOM_BREAK_TABLE
VARCHAR2 |
Random Break Table identifier Currently limted to Y (es) or N(o). |
MM_PERCENT_MONITORED
NUMBER |
Percentage of time for this haul where marine mammal monitoring occured. For fixed gear deployments the valid values are anywhere in the range. For mobile gear deployments the values may be either 0 or 100. |
BIRD_DETERRENCE
VARCHAR2 |
Deterrence code from NORPAC bird or mammal deterance tables. |
BIRD_VERIFICATION
VARCHAR2 |
This attirbute is no longer collected, but is retained from the domestic data set. See the atl_bird _module deployed in 2010 for complete observer seabird data. |
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. |
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. |
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.'; |
YEAR
NUMBER |
Year is extracted from the haul rettrv_date_time field. |
LATDD_END
NUMBER |
Latitude decimal degrees is computed from the retrieval latitude. |
LONDD_END
NUMBER |
Longitude decimal degrees is computed from the retrieval longitude. |
LATDD_START
NUMBER |
Latitude decimal degrees is computed from the deployment latitude. |
LONDD_START
NUMBER |
Longitude decimal degrees is computed from the deployment longitude. |
SEABIRD_SAMPLE_TYPE
VARCHAR2 |
This attirbute is no longer collected, but is retained from the domestic data set. See the atl_bird _module deployed in 2010 for complete observer seabird data. |
ATLAS_VERSION
NUMBER |
If this haul data was transmitted from the field. This attribute records the version of the software used. |
OBSVR_EST_DISCARDS
NUMBER |
Observer estimate of total discards in kgs. |
Child Items
No Child Items for this record.
Contact Information
No contact information is available for this record.
Please contact the owner organization (AFSC) for inquiries on this record.
Extents
1986 - Present
Domestic Observer Data began to be collected in 1986 and is ongoing.
Item Identification
Title: | Table: DEBRIEFED_HAUL |
---|---|
Short Name: | DEBRIEFED_HAUL |
Status: | Completed |
Abstract: |
The debriefed haul table was created as a successor to the debriefed haul materialized view. The table is a bridge object between the Domestic data (pre 2008) and the ATL data (2008 onwards) As such, refinements to the structure and statistical reliability realized in the redevelopment of Norpac are lost. The use of this table is primarily for status of stocks authors who require a longitudinal view of observer data. |
Notes: |
Loaded by batch 2535, 11-09-2010 10:55 |
Physical Location
Organization: | Alaska Fisheries Science Center |
---|---|
City: | Seattle |
State/Province: | WA |
Country: | USA |
Entity Information
Entity Type: | Data Table |
---|---|
Active Version?: | Yes |
Schema Name: | OBSINT |
Description: |
The debriefed haul table was created as a successor to the debriefed haul materialized view. The table is a bridge object between the Domestic data (pre 2008) and the ATL data (2008 onwards) As such, refinements to the structure and statistical reliability realized in the redevelopment of Norpac are lost. The use of this table is primarily for status of stocks authors who require a longitudinal view of observer data. |
Data Attributes
Attribute Summary
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 an 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 | Alpha Numeric code from ATL_Lov_Vessel table, which identifies the vessel. | |
100
|
HAUL_SEQ | NUMBER | Sequence generated unique identifier for a haul record | |
100
|
HAUL_JOIN | NUMBER | This is a uniquie identifier of a haul record composed by concatenation of cruise, permit and haul_seq. For domestic table records this is a sequence generated unique identifier for a haul. | |
100
|
TRIP_SEQ | NUMBER | Sequence generated unique identifier for a trip as defined in ATL_fma_trip. | |
100
|
TRIP_JOIN | NUMBER | Surrogate FK to haul, It is a unique identifier of a trip record created by concatenating cruise, permit, and trip_seq (TO_NUMBER ( t.cruise||LPAD (t.permit, 6,'0')||LPAD (t.trip_seq, 9, '0')) AS trip_join) | |
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. | |
100
|
GEAR_TYPE | NUMBER | Numeric value from Norpac Domestic Gear or atl_lov_gear_type that combined with the Form defines the unique identifier for a gear record. | |
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
|
DEPLOY_LATITUDE | NUMBER | Gear deployment position. | |
100
|
DEPLOY_LONGITUDE | NUMBER | Gear deployment position | |
100
|
DEPLOY_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
|
DEPLOY_LONGITUDE_SECONDS | NUMBER | Gear deployment position. | |
100
|
DEPLOY_LATITUDE_SECONDS | NUMBER | Gear deployment position. | |
100
|
DEPLOY_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
|
DURATION_IN_MIN | NUMBER | Duration of a haul calculated in minutes. | |
100
|
LOCATION | VARCHAR2 | Identifies whether the information in a haul is based on retrieval or delivery (as in a mother ship). | |
100
|
RETRV_LATITUDE | NUMBER | Retrieval location. | |
100
|
RETRV_LONGITUDE | NUMBER | Retrieval location. | |
100
|
RETRV_LONGITUDE_SECONDS | NUMBER | Gear retrieval position. | |
100
|
RETRV_LATITUDE_SECONDS | NUMBER | Gear retrieval position. | |
100
|
RETRV_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
|
RETRV_E_W | VARCHAR2 | Retrieval location. | |
100
|
GENERIC_AREA | NUMBER | This attirbute is no longer collected, but is retained for the domestic data set. | |
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 estimated by the observer in kgs and converted to MT for this presentation. | |
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_ADFG | NUMBER | If this haul was delivered to a mothership or catcher processor, this attibute records the adfg negistration 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 for longline fishing. | |
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 occured. 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 | VARCHAR2 | Deterrence code from NORPAC bird or mammal deterance tables. | |
100
|
BIRD_VERIFICATION | VARCHAR2 | This attirbute is no longer collected, but is retained from the domestic data set. See the atl_bird _module deployed in 2010 for complete observer seabird data. | |
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
|
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
|
SEABIRD_SAMPLE_TYPE | VARCHAR2 | This attirbute is no longer collected, but is retained from the domestic data set. See the atl_bird _module deployed in 2010 for complete observer seabird data. | |
100
|
ATLAS_VERSION | NUMBER | If this haul data was transmitted from the field. This attribute records the version of the software used. | |
100
|
OBSVR_EST_DISCARDS | NUMBER | Observer estimate of total discards in kgs. |
Attribute Details
T_TABLE
Seq. Order: | 1 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 8 |
Required: | Yes |
Primary Key: | No |
Status: | Active |
Description: |
Identifier of Source Table |
General Data Type: | VARCHAR2 |
CRUISE
Seq. Order: | 2 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated by Norpac and supplied to the observer as an unique identifier for an observer cruise record. |
General Data Type: | NUMBER |
PERMIT
Seq. Order: | 3 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 6 |
Required: | No |
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: | VARCHAR2 |
VESSEL
Seq. Order: | 4 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 6 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Alpha Numeric code from ATL_Lov_Vessel table, which identifies the vessel. |
General Data Type: | VARCHAR2 |
HAUL_SEQ
Seq. Order: | 5 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated unique identifier for a haul record |
General Data Type: | NUMBER |
HAUL_JOIN
Seq. Order: | 6 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | Yes |
Primary Key: | Yes |
Precision: | 38 |
Status: | Active |
Description: |
This is a uniquie identifier of a haul record composed by concatenation of cruise, permit and haul_seq. For domestic table records this is a sequence generated unique identifier for a haul. |
General Data Type: | NUMBER |
TRIP_SEQ
Seq. Order: | 7 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Sequence generated unique identifier for a trip as defined in ATL_fma_trip. |
General Data Type: | NUMBER |
TRIP_JOIN
Seq. Order: | 8 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Surrogate FK to haul, It is a unique identifier of a trip record created by concatenating cruise, permit, and trip_seq (TO_NUMBER ( t.cruise||LPAD (t.permit, 6,'0')||LPAD (t.trip_seq, 9, '0')) AS trip_join) |
General Data Type: | NUMBER |
Foreign Key Relations: |
OBSINT.DEBRIEFED_TRIP |
HAUL_DATE
Seq. Order: | 9 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date of haul retrieval. |
General Data Type: | DATE |
HAUL
Seq. Order: | 10 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
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: | NUMBER |
HAUL_PURPOSE_CODE
Seq. Order: | 11 |
---|---|
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: | VARCHAR2 |
GEAR_TYPE
Seq. Order: | 12 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Numeric value from Norpac Domestic Gear or atl_lov_gear_type that combined with the Form defines the unique identifier for a gear record. |
General Data Type: | NUMBER |
PERFORMANCE
Seq. Order: | 13 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Unique performance code for a gear type. see ATL_LOV_gear_perfomrance. |
General Data Type: | NUMBER |
VESSEL_TYPE
Seq. Order: | 14 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Unique identifier of a vessel type, see ATL_LOV_vessel_type |
General Data Type: | NUMBER |
DEPLOYMENT_DATE
Seq. Order: | 15 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date and time of gear deployment |
General Data Type: | DATE |
DEPLOY_LATITUDE
Seq. Order: | 16 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Gear deployment position. |
General Data Type: | NUMBER |
DEPLOY_LONGITUDE
Seq. Order: | 17 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Gear deployment position |
General Data Type: | NUMBER |
DEPLOY_LONGITUDE_CONVERTED
Seq. Order: | 18 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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 |
DEPLOY_LONGITUDE_SECONDS
Seq. Order: | 19 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Gear deployment position. |
General Data Type: | NUMBER |
DEPLOY_LATITUDE_SECONDS
Seq. Order: | 20 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Gear deployment position. |
General Data Type: | NUMBER |
DEPLOY_E_W
Seq. Order: | 21 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Gear deployment position. |
General Data Type: | VARCHAR2 |
FISHING_DEPTH_FATHOMS
Seq. Order: | 22 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Average fishing depth recorded by the observer from the vessel log. |
General Data Type: | NUMBER |
BOTTOM_DEPTH_FATHOMS
Seq. Order: | 23 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Average bottom depth recorded by the observer from the vessel log. |
General Data Type: | NUMBER |
RETRIEVAL_DATE
Seq. Order: | 24 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Date and time of gear retrieval. |
General Data Type: | DATE |
DURATION_IN_MIN
Seq. Order: | 25 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Duration of a haul calculated in minutes. |
General Data Type: | NUMBER |
LOCATION
Seq. Order: | 26 |
---|---|
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: | VARCHAR2 |
RETRV_LATITUDE
Seq. Order: | 27 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Retrieval location. |
General Data Type: | NUMBER |
RETRV_LONGITUDE
Seq. Order: | 28 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Retrieval location. |
General Data Type: | NUMBER |
RETRV_LONGITUDE_SECONDS
Seq. Order: | 29 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Gear retrieval position. |
General Data Type: | NUMBER |
RETRV_LATITUDE_SECONDS
Seq. Order: | 30 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Gear retrieval position. |
General Data Type: | NUMBER |
RETRV_LONGITUDE_CONVERTED
Seq. Order: | 31 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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. |
General Data Type: | NUMBER |
RETRV_E_W
Seq. Order: | 32 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Retrieval location. |
General Data Type: | VARCHAR2 |
GENERIC_AREA
Seq. Order: | 33 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
This attirbute is no longer collected, but is retained for the domestic data set. |
General Data Type: | NUMBER |
NMFS_AREA
Seq. Order: | 34 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
This attribute is computed using the MDSYS.SDO_GEOMETRY package and an ESRI shape file. |
General Data Type: | NUMBER |
COBLZ_AREA
Seq. Order: | 35 |
---|---|
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: | VARCHAR2 |
VESSEL_ESTIMATE
Seq. Order: | 36 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 6 |
Scale: | 2 |
Status: | Active |
Description: |
Total catch weight in metric tons as recorded in the vessel log. |
General Data Type: | NUMBER |
OFFICIAL_TOTAL_CATCH
Seq. Order: | 37 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Total catch weight as estimated by the observer in kgs and converted to MT for this presentation. |
General Data Type: | NUMBER |
OBSERVER_ESTIMATE
Seq. Order: | 38 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Total catch weight as estimated by the observer in kgs and converted to MT for this presentation. |
General Data Type: | NUMBER |
OBSERVER_ESTIMATE_METHOD
Seq. Order: | 39 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Method used to determine the observer estimated catch. |
General Data Type: | VARCHAR2 |
DENSITY
Seq. Order: | 40 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Density used by the observer to determine the total catch weights. Recorded in kgs per m3. |
General Data Type: | NUMBER |
CATCHER_BOAT_ADFG
Seq. Order: | 41 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
If this haul was delivered to a mothership or catcher processor, this attibute records the adfg negistration number of that vessel. |
General Data Type: | NUMBER |
IFQ
Seq. Order: | 42 |
---|---|
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. |
General Data Type: | VARCHAR2 |
CDQ_CODE
Seq. Order: | 43 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Unique AlphaNumeric code representing a CDQ or research group. |
General Data Type: | VARCHAR2 |
SKATES_IN_SET
Seq. Order: | 44 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Number of skates for longline fishing. |
General Data Type: | NUMBER |
HOOKS_PER_SKATE
Seq. Order: | 45 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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. |
General Data Type: | NUMBER |
TOTAL_HOOKS_POTS
Seq. Order: | 46 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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. |
General Data Type: | NUMBER |
HAUL_SAMPLED_BY
Seq. Order: | 47 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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: | NUMBER |
RANDOM_SAMPLE_TABLE
Seq. Order: | 48 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Random Sample Reference Table code reference. |
General Data Type: | VARCHAR2 |
RANDOM_BREAK_TABLE
Seq. Order: | 49 |
---|---|
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: | VARCHAR2 |
MM_PERCENT_MONITORED
Seq. Order: | 50 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 3 |
Scale: | 0 |
Status: | Active |
Description: |
Percentage of time for this haul where marine mammal monitoring occured. 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: | NUMBER |
BIRD_DETERRENCE
Seq. Order: | 51 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Deterrence code from NORPAC bird or mammal deterance tables. |
General Data Type: | VARCHAR2 |
BIRD_VERIFICATION
Seq. Order: | 52 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This attirbute is no longer collected, but is retained from the domestic data set. See the atl_bird _module deployed in 2010 for complete observer seabird data. |
General Data Type: | VARCHAR2 |
PROCESSOR
Seq. Order: | 53 |
---|---|
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: | VARCHAR2 |
FISHING_START_DATE
Seq. Order: | 54 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
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 |
DATE_OF_ENTRY
Seq. Order: | 55 |
---|---|
Data Storage Type: | DATE |
Max Length: | 7 |
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
Seq. Order: | 56 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Year is extracted from the haul rettrv_date_time field. |
General Data Type: | NUMBER |
LATDD_END
Seq. Order: | 57 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Latitude decimal degrees is computed from the retrieval latitude. |
General Data Type: | NUMBER |
LONDD_END
Seq. Order: | 58 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Longitude decimal degrees is computed from the retrieval longitude. |
General Data Type: | NUMBER |
LATDD_START
Seq. Order: | 59 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Latitude decimal degrees is computed from the deployment latitude. |
General Data Type: | NUMBER |
LONDD_START
Seq. Order: | 60 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
Status: | Active |
Description: |
Longitude decimal degrees is computed from the deployment longitude. |
General Data Type: | NUMBER |
SEABIRD_SAMPLE_TYPE
Seq. Order: | 61 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
This attirbute is no longer collected, but is retained from the domestic data set. See the atl_bird _module deployed in 2010 for complete observer seabird data. |
General Data Type: | VARCHAR2 |
ATLAS_VERSION
Seq. Order: | 62 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 38 |
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 |
OBSVR_EST_DISCARDS
Seq. Order: | 63 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 10 |
Required: | No |
Primary Key: | No |
Precision: | 2 |
Status: | Active |
Description: |
Observer estimate of total discards in kgs. |
Extents
Extent Group 1
Extent Group 1 / Time Frame 1
Time Frame Type: | Continuing |
---|---|
Start: | 1986 |
Description: |
Domestic Observer Data began to be collected in 1986 and is ongoing. |
Catalog Details
Catalog Item ID: | 10659 |
---|---|
GUID: | gov.noaa.nmfs.inport:10659 |
Metadata Record Created By: | Doug Turnbull |
Metadata Record Created: | 2010-11-09 10:55+0000 |
Metadata Record Last Modified By: | SysAdmin InPortAdmin |
Metadata Record Last Modified: | 2022-08-09 17:11+0000 |
Metadata Record Published: | 2016-05-18 |
Owner Org: | AFSC |
Metadata Publication Status: | Published Externally |
Do Not Publish?: | N |
Metadata Last Review Date: | 2016-05-18 |
Metadata Review Frequency: | 1 Year |
Metadata Next Review Date: | 2017-05-18 |