Slide Menu
Search Help Show/Hide Menu

Item Identification

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

als.ALS_GENERAL_CANVASS holds the annual landings data data for Florida. This data is from 1976-1992.

Notes:

Loaded by batch 1686, 10-12-2007 09:48

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None annual data
None finfish
None landings

Temporal Keywords

Thesaurus Keyword
UNCONTROLLED
None 1976-1996

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None florida

Stratum Keywords

Thesaurus Keyword
UNCONTROLLED
None distance from shore
None gear
None species
None waterbody

Physical Location

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

75 Virginia Beach Drive

Miami, FL 33016

Entity Information

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

als.ALS_GENERAL_CANVASS holds the annual landings data data for Florida. This data is from 1976-1992.

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
MONTHLAND VARCHAR2 The month landed. In this table it is always 13 which indicates annual data.
100
YEARLAND VARCHAR2 The Year Landed.
100
ALSSTATE VARCHAR2 The NMFS state code.
100
ALSCTYIN VARCHAR2 The three digit county code. (0 + the two digit county code)
100
NMFSCOUNTY VARCHAR2 The NMFS County Code. (2 digits)
100
DEALER VARCHAR2 The Dealer Number.
100
WATERBODY VARCHAR2 The Waterbody Code.
100
NMFSGEAR VARCHAR2 The NMFS Gear Code.
100
NMFS_CODE VARCHAR2 The NMFS Species Code.
100
SHELLFIN VARCHAR2 The code that says whether the catch is a shellfish or a finfish.
100
POUNDS NUMBER The pounds caught.
100
VALUE NUMBER The Value in Dollars.
100
SECTION VARCHAR2 The Section Code.
100
PRICE NUMBER The Price.
100
DISTANCE VARCHAR2 The DIstance From Shore COde.
100
STATECAUGHT VARCHAR2 The State Caught.
100
HOWFIGURED VARCHAR2 How the price was figured.
100
OLD_WATERBODY VARCHAR2 OLD_WATERBODY Code. This has been included because there was a project to modify the ALS data that involved substantial changing of Waterbody Codes
100
REGION VARCHAR2 Region Code
100
UNFACTORED_WEIGHT_FDEP NUMBER Column Added For Compatability purposes for newer trip ticket data that comes from Florida.This column is not used in this table
100
CONVERSION NUMBER Column Added For Compatability purposes for newer trip ticket data that comes from Florida.This column is not used in this table

Attribute Details

MONTHLAND

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

The month landed. In this table it is always 13 which indicates annual data.

General Data Type: VARCHAR2

YEARLAND

CC ID: 16696
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: 16695
Seq. Order: 3
Data Storage Type: VARCHAR2
Max Length: 2
Required: No
Primary Key: No
Status: Active
Description:

The NMFS state code.

General Data Type: VARCHAR2

ALSCTYIN

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

The three digit county code. (0 + the two digit county code)

General Data Type: VARCHAR2

NMFSCOUNTY

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

The NMFS County Code. (2 digits)

General Data Type: VARCHAR2

DEALER

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

The Dealer Number.

General Data Type: VARCHAR2

WATERBODY

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

The Waterbody Code.

General Data Type: VARCHAR2

NMFSGEAR

CC ID: 16690
Seq. Order: 8
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: 16689
Seq. Order: 9
Data Storage Type: VARCHAR2
Max Length: 4
Required: No
Primary Key: No
Status: Active
Description:

The NMFS Species Code.

General Data Type: VARCHAR2

SHELLFIN

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

The code that says whether the catch is a shellfish or a finfish.

General Data Type: VARCHAR2

POUNDS

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

The pounds caught.

General Data Type: NUMBER

VALUE

CC ID: 16686
Seq. Order: 12
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

SECTION

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

The Section Code.

General Data Type: VARCHAR2

PRICE

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

The Price.

General Data Type: NUMBER

DISTANCE

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

The DIstance From Shore COde.

General Data Type: VARCHAR2

STATECAUGHT

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

The State Caught.

General Data Type: VARCHAR2

HOWFIGURED

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

How the price was figured.

General Data Type: VARCHAR2

OLD_WATERBODY

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

OLD_WATERBODY Code. This has been included because there was a project to modify the ALS data that involved substantial changing of Waterbody Codes

General Data Type: VARCHAR2

REGION

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

Region Code

General Data Type: VARCHAR2

UNFACTORED_WEIGHT_FDEP

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

Column Added For Compatability purposes for newer trip ticket data that comes from Florida.This column is not used in this table

General Data Type: NUMBER

CONVERSION

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

Column Added For Compatability purposes for newer trip ticket data that comes from Florida.This column is not used in this table

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.

Catalog Details

Catalog Item ID: 5388
GUID: gov.noaa.nmfs.inport:5388
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2007-10-12 09:48+0000
Metadata Record Last Modified By: Lee M Weinberger
Metadata Record Last Modified: 2021-05-06 22:24+0000
Metadata Record Published: 2021-05-06
Owner Org: SEFSC
Metadata Publication Status: Published Externally
Do Not Publish?: N
Metadata Next Review Date: 2022-05-07