Slide Menu
InPort and its associated services will be under maintenance and unavailable for the deployment of InPort Release 5.2.3. Downtime Schedule Tuesday, November 29, 2022 12:00pm - 1:30pm Eastern / 10:00am - 11:30pm Pacific / 7:00am - 8:30pm Hawaii Impacted Areas - InPort Website: https://www.fisheries.noaa.gov/inport - InPort WAF: https://www.fisheries.noaa.gov/inportserve/waf What's...
View All
Search Help Show/Hide Menu

Item Identification

Title: Table: TALS_GCANV6071
Short Name: TALS_GCANV6071
Status: Completed
Abstract:

This table contains historical annual landings data from 1962 through 1971. Please remember that this data are also available in fsrayg.gencan_r45@shark (on the SHARK on the DC machine.)

Notes:

Loaded by batch 1723, 10-16-2007 04:06.

Supplemental Information:

These landings are reported on forms which contain pre-printed species. Generally the species listed on the form reflect the species of interest of the State Agency as well as NMFS and they vary from state to state. Space is generally provided for 'write-in' species; however, it is probable that bias exists favoring the entry of the pre-printed species.

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None annual data
None landings

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 1962-1971

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None alabama
None florida
None georgia
None louisiana
None mississippi
None north carolina
None south carolins
None texas

Stratum Keywords

Thesaurus Keyword
UNCONTROLLED
None county
None gear
None species
None state
None waterbody

Physical Location

Organization: Southeast Fisheries Science Center
City: Miami
State/Province: FL
Country: USA
Location Description:

75 Virginia Beach Drive

Miami, FL 33149

Entity Information

Entity Type: Data Table
Active Version?: Yes
Schema Name: ALS
Description:

This table contains historical annual landings data from 1962 through 1971. Please remember that this data are also available in fsrayg.gencan_r45@shark (on the SHARK on the DC machine.)

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
MONTHLAND VARCHAR2 In this table there are no monthly data. The code '13' is used to indicate annual landings.
100
YEARLAND VARCHAR2 The Year Landed.
100
ALSSTATE VARCHAR2 The NMFS State Code of where the fish was landed. Florida has coastal codes of '10' (Atlantic), '11' (Gulf), '12' (Interior).
100
ALSCTYIN VARCHAR2 The three character county code.
100
NMFSCOUNTY VARCHAR2 The two character NMFS County Code.
100
WATERBODY VARCHAR2 The Water Body Code. Has been updated from the old state-dependent system to the Gulf grid / South Atlantic shrimp system coding. Previous code contained in the old_waterbody column.
100
NMFSGEAR VARCHAR2 The NMFS Gear Code.
100
NMFS_CODE VARCHAR2 The NMFS Species Code.
100
POUNDS NUMBER The whole weight in pounds except for Florida which lists the landed weight in pounds. For non-shrimp species weights are rounded to nearest even hundreds of pounds.
100
VALUE NUMBER The Value (in Dollars)
100
XPRICE VARCHAR2 The ex-vessel price. This column has an implied decimal in the second position. The price 0100 should read 0.100.
100
COMMON VARCHAR2 The common name of the species landed. Names are not consistent within this column. It is recommended that the table be joined by NMFS_CODE to the SPECIES_CODE_NMFS table for consistent reporting by name.
100
DISTANCE VARCHAR2 The Distance From Shore Code. Distance codes of '0' are supposed to represent inshore waters; however, it appears from examination of the catch that code of '0' was used as a place-holder in many instances.
100
STATECAUGHT VARCHAR2 This column is not to be used.
100
HOWFIGURED VARCHAR2 A code to indicate how the price was figured for Florida data. This column is null in this table.
100
WHICHONE VARCHAR2 Gives the source of the data. Codes are alpha-state initials except for 'GS' which stands for 'Gulf Shrimp' and indicates records originating from the Gulf Shrimp Survey data set.
100
REGION VARCHAR2 The Region Code. Indicates general region of landing. '4' is for Southern US Atlantic Waters (NC - Florida East Coast). '5' is for Gulf of Mexico.
100
OLD_WATERBODY VARCHAR2 Waterbody Code that originally was on the record prior to the comprehensive water code update. See ALS_WATERBODY_OLD_NEW_XREF for details.
100
UNFACTORED_WEIGHT_FDEP NUMBER Unfactored Weight From FLorida. This column had been added for compatibility purposes with other Landings Tables, but is not used in this table.
100
PRICE NUMBER This column is null.
100
CONVERSION NUMBER Conversion Factor Between Unfactored Weight From Florida and NMFS Species Weight. Provided for compatbility purposes with other tables. This column is not used for this application

Attribute Details

MONTHLAND

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

In this table there are no monthly data. The code '13' is used to indicate annual landings.

General Data Type: VARCHAR2

YEARLAND

CC ID: 17129
Seq. Order: 2
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

The Year Landed.

General Data Type: VARCHAR2

ALSSTATE

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

The NMFS State Code of where the fish was landed. Florida has coastal codes of '10' (Atlantic), '11' (Gulf), '12' (Interior).

General Data Type: VARCHAR2

ALSCTYIN

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

The three character county code.

General Data Type: VARCHAR2

NMFSCOUNTY

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

The two character NMFS County Code.

General Data Type: VARCHAR2

WATERBODY

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

The Water Body Code. Has been updated from the old state-dependent system to the Gulf grid / South Atlantic shrimp system coding. Previous code contained in the old_waterbody column.

General Data Type: VARCHAR2

NMFSGEAR

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

The NMFS Gear Code.

General Data Type: VARCHAR2

NMFS_CODE

CC ID: 17123
Seq. Order: 8
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

The NMFS Species Code.

General Data Type: VARCHAR2

POUNDS

CC ID: 17122
Seq. Order: 9
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 9
Scale: 0
Status: Active
Description:

The whole weight in pounds except for Florida which lists the landed weight in pounds. For non-shrimp species weights are rounded to nearest even hundreds of pounds.

General Data Type: NUMBER

VALUE

CC ID: 17121
Seq. Order: 10
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 9
Scale: 0
Status: Active
Description:

The Value (in Dollars)

General Data Type: NUMBER

XPRICE

CC ID: 17120
Seq. Order: 11
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

The ex-vessel price. This column has an implied decimal in the second position. The price 0100 should read 0.100.

General Data Type: VARCHAR2

COMMON

CC ID: 17119
Seq. Order: 12
Data Storage Type: VARCHAR2
Max Length: 21
Required: No
Primary Key: No
Status: Active
Description:

The common name of the species landed. Names are not consistent within this column. It is recommended that the table be joined by NMFS_CODE to the SPECIES_CODE_NMFS table for consistent reporting by name.

General Data Type: VARCHAR2

DISTANCE

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

The Distance From Shore Code. Distance codes of '0' are supposed to represent inshore waters; however, it appears from examination of the catch that code of '0' was used as a place-holder in many instances.

General Data Type: VARCHAR2

STATECAUGHT

CC ID: 17117
Seq. Order: 14
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

This column is not to be used.

General Data Type: VARCHAR2

HOWFIGURED

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

A code to indicate how the price was figured for Florida data. This column is null in this table.

General Data Type: VARCHAR2

WHICHONE

CC ID: 17115
Seq. Order: 16
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

Gives the source of the data. Codes are alpha-state initials except for 'GS' which stands for 'Gulf Shrimp' and indicates records originating from the Gulf Shrimp Survey data set.

General Data Type: VARCHAR2

REGION

CC ID: 17114
Seq. Order: 17
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

The Region Code. Indicates general region of landing. '4' is for Southern US Atlantic Waters (NC - Florida East Coast). '5' is for Gulf of Mexico.

General Data Type: VARCHAR2

OLD_WATERBODY

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

Waterbody Code that originally was on the record prior to the comprehensive water code update. See ALS_WATERBODY_OLD_NEW_XREF for details.

General Data Type: VARCHAR2

UNFACTORED_WEIGHT_FDEP

CC ID: 17112
Seq. Order: 19
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 9
Scale: 0
Status: Active
Description:

Unfactored Weight From FLorida. This column had been added for compatibility purposes with other Landings Tables, but is not used in this table.

General Data Type: NUMBER

PRICE

CC ID: 17111
Seq. Order: 20
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 7
Scale: 3
Status: Active
Description:

This column is null.

General Data Type: NUMBER

CONVERSION

CC ID: 17110
Seq. Order: 21
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 9
Scale: 5
Status: Active
Description:

Conversion Factor Between Unfactored Weight From Florida and NMFS Species Weight. Provided for compatbility purposes with other tables. This column is not used for this application

General Data Type: NUMBER

Access Information

Security Class: Confidential
Security Classification System:

Password Restricted. Rule of 3: Data summaries must include at least 3 dealers to be considered non-confidential. See:

NOAA FORM 58-5 (1-84) TRANSMITTAL 127,

National Oceanic and Atmospheric Administration

NOAA Administrative Order 216-100

NOAA ADMINISTRATIVE ORDER SERIES

Date of Issuance: July 26, 1994

Security Handling Description:

Confidential data may only be released to entities having a signed non-disclosure agreement on file with the Director of the Information Resources Management Division (IRMD). Otherwise, confidentiality may be suppressed by the following methods used for aggregation of confidential data:

Data that are submitted as confidential can be released to the public under the following circumstances:

1. Combined or aggregated data. Confidential data can be released if the data are aggregated or summarized in a manner that prevents the identification of the person or organization that submitted the data. The "rule of three" and identification of majority allocations" are the primary data suppression methods.

2. Obscure (scramble) or remove the data identifier. For some types of data, confidential data Can be released as non-confidential if the identity of the person, vessel, company, etc. that submitted the data is not included or is scrambled as part of the data that are released.

3. Submitter. Confidential data collected under federal authority Can be released to the original entity (person, vessel, business, etc.) that sUbmitted the data.

4. Confidential data waived. The protection of confidential data can be waived by the person or business that submitted the data.

Data Access Policy:

See NOAA Administrative Order 216-100

NOAA ADMINISTRATIVE ORDER SERIES

Date of Issuance: July 26, 1994

Data Access Procedure:

These standards and procedures apply to all employees of the SEFSC that need access to confidential fisheries statistics. This includes full time or term employees, contractors, volunteers, and/or other employees associated with the SEFSC, but not directly employed by either organization. Any SEFSC employee that needs or desires access to confidential data must have read NOA 216-100 and submitted a signed nondisclosure statement to the Director, Information Resources Management Division (IRMD). The non-disclosure statement must be approved by the Director of IRMD and maintained on file by IRMD. It is the responsibility of the Director of IRMD to certifY upon request, that a person or organization that requests access to confidential data is authorized access to those data. All employees that have access to and/or use confidential data (federal and nonfederal) are responsible to protect those data from unauthorized access or release. Contractors or grantees that have an agreement with NMFS can be granted

access to confidential data as an authorized user (See NOA 216-100 1 Section 6.03e). It should be clearly understood that confidential data cannot be released simply by an individual signing a nondisclosure statement. There must be a clear and demonstrable need for the confidential data that are requested as part of a contract or grant. Confidential data can only be released for the specific contract or grant. Upon completion of the contract or grant, the recipient must either return the data or state that it has been destroyed. The contractor or grantee cannot use the data for any purpose other than the uses stated in the agreement. The Contracting Officers Technical Representative (COTR) or the Technical Monitor (TM) that has been assigned to the contract or grant, respectively, has the following? responsibilities:

1. The COTR/TM has the responsibility to determine whether the contractor/grantee is eligible to receive the confidential data that are requested in the agreement.

2. The COTR/TM has the responsibility to assure that all persons included in the agreement have read NOA 2l6-l00 and have signed a nondisclosure statement. A statement must be signed by each person that will have access to the confidential data under the agreement, i.e., a blanket statement cannot be used for the company or firm. The COTR/TM also has the responsibility to make sure that the Director, IRMD has signed and approved the nondisclosure statement and the statement is on file with IRMD.

3. The COTR/TM has the responsibility to assure that confidential data are not released in any publication, report, oral presentation, or other means to the public by the contractor or grantee.

Data Access Constraints:

To access confidential data a completed non-disclosure agreement must be on file with NOAA-SEFSC. Otherwise Data that are submitted as confidential can be released to the public under the following circumstances:

1. Combined or aggregated data. Confidential data can be released if the data are aggregated or summarized in a manner that prevents the identification of the person or organization that submitted the data. The "rule of three" and identification of majority allocations" are the primary data suppression methods.

2. Obscure (scramble) or remove the data identifier. For some types of data, confidential data Can be released as non-confidential if the identity of the person, vessel, company, etc. that submitted the data is not included or is scrambled as part of the data that are released.

3. Submitter. Confidential data collected under federal authority Can be released to the original entity (person, vessel, business, etc.) that sUbmitted the data.

4. Confidential data waived. The protection of confidential data can be waived by the person or business that submitted the data.

Data Use Constraints:

Confidential data are not to be released in any publication, report, oral presentation, or other means to the public.

Metadata Access Constraints:

Non-published Metadata access is restricted. Published Metadata is available to the public.

Metadata Use Constraints:

Only published metadata are to be used.

Issues

Issue 1

CC ID: 43580
Issue Date: 2011-06-10
Author: Joshua E. Bennett
Issue:

Shrimp gear is NULL in table for Gulf of Mexico region. Neither is it present in source table GSS.GSS_GULF_SHRIMP_56_83.

Catalog Details

Catalog Item ID: 5442
GUID: gov.noaa.nmfs.inport:5442
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2007-10-16 04:06+0000
Metadata Record Last Modified By: SysAdmin InPortAdmin
Metadata Record Last Modified: 2022-08-09 17:10+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Last Review Date: 2021-05-06
Metadata Review Frequency: 1 Year
Metadata Next Review Date: 2022-05-06