Slide Menu
System Maintenance Notice, Sunday, January 23, 2022 @ 8am-2pm Eastern. The Operations Team will be performing system maintenance on all server environments. During this scheduled downtime, InPort will not be available.
View All
Search Help Show/Hide Menu

Item Identification

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

Pre-validation Table to load Accumulative Landings Data

Notes:

Loaded by batch 1726, 10-16-2007 08:22

Keywords

Theme Keywords

Thesaurus Keyword
UNCONTROLLED
None landings
None staging table

Physical Location

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

Entity Information

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

Pre-validation Table to load Accumulative Landings Data

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
UNIXID VARCHAR2 Id of the person loading data
100
RNUMBER NUMBER Which Record Number In the data file that is loaded.
100
MONTHLAND VARCHAR2 Two character month that the data was landed.
100
YEARLAND VARCHAR2 Four digit year that the fish was landed.
100
ALSSTATE VARCHAR2 Two character NMFS State Code.
100
ALSCTYIN VARCHAR2 Three character NMFS County Code.
100
NMFSCOUNTY VARCHAR2 2 chararacter NMFS County Code.
100
DEALER VARCHAR2 The Dealer Code.
100
NMFSGEAR VARCHAR2 NMFS Gear Code.
100
NMFS_CODE VARCHAR2 NMFS Species Code.
100
SHELLFIN VARCHAR2 Shellfin Code.
100
POUNDS NUMBER Weight (pounds) of the fish landed . (WHole Weight, heads on for shrimp is the ALS standard.)
100
VALUE NUMBER Value in dollars of the fish that was caught.
100
SECTION VARCHAR2 Section Code. There is not always meaningful data in this field.
100
PRICE NUMBER Average price per pound. The decimal point in this field is now real and is no longer implied.
100
DISTANCE VARCHAR2 The Distance From Shore Code.
100
STATECAUGHT VARCHAR2 State that that fish was landed. There is not always meaningful data in this field. When a value of "00" is in this field, it means nothing, not anything else.
100
HOWFIGURED VARCHAR2 Indicates how the price was determined for historical Florida data.
100
WHICHONE VARCHAR2 Gives the source of the data.
100
TXSTATE VARCHAR2 TPWD (Texas) State Code.
100
TXCOUNTY NUMBER TPWD (Texas) County Code.
100
TXWATER VARCHAR2 TPWD (Texas) Water Body Code.
100
TXBAY VARCHAR2 TPWD (Texas) Bay Code.
100
TXSPECIES NUMBER TPWD (Texas) Species Code.
100
LACOUNTY VARCHAR2 LDWF (Louisiana) county codes.
100
LACONDITION VARCHAR2 Condition code for Louisiana data.
100
FDEP_COAST VARCHAR2 FDEP Coast Code. (Florida Data)
100
FDEPCTY VARCHAR2 The County Code on data that comes from FDEP. (Florida Data)
100
FDEP_CODE VARCHAR2 FDEP Species Code. (Florida)
100
FDEP_TRIPS NUMBER Number of trips made. It is entered on data that comes from FDEP.
100
INSHORE VARCHAR2 Inshore code.
100
BLANK_1 VARCHAR2 A filler field.
100
BATCHNUM VARCHAR2 Batch Number for data that comes from Florida.
100
BLANK_2 VARCHAR2 A filler field
100
CONVERSION NUMBER For Records that come from Florida, this is the conversion factor used to convert the landing weight provided by Florida to Whole pounds.
100
VAL_VAL NUMBER Summed ex-vessel value for trips with a reported price for a species. (FDEP Data)
100
VAL_LBS NUMBER Summed pounds for which price was reported for a species. (FDEP Data)
100
VAL_TRIPS NUMBER Number of trips which reported prices for a species. (FDEP Data)
100
FL_COMMON VARCHAR2 Florida Common Name of the Species landed. It is used only for Florida data.
100
SUBGROUP VARCHAR2 Subgroup. It is entered in the data that arrives from FDEP.
100
FLEDIT VARCHAR2 Used for Florida data only. It may be "Y" for Editted data, or "N" for uneditted data.
100
PRINTSEQ VARCHAR2 Print Sequence
100
UNFACTORED_WEIGHT_FDEP NUMBER Unfactore Weight From Florida
100
FDEP_CODE_TRIPTICKET VARCHAR2 FDEP Code On The Trup Ticket
100
SOURCE_FILE VARCHAR2 Source File used to load data.
100
WATERBODY VARCHAR2 Water Body Code.
100
OLD_WATERBODY VARCHAR2 Water Body code that had been on record before water body change project
100
REGION VARCHAR2 Region Code

Attribute Details

UNIXID

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

Id of the person loading data

General Data Type: VARCHAR2

RNUMBER

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

Which Record Number In the data file that is loaded.

General Data Type: NUMBER

MONTHLAND

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

Two character month that the data was landed.

General Data Type: VARCHAR2

YEARLAND

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

Four digit year that the fish was landed.

General Data Type: VARCHAR2

ALSSTATE

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

Two character NMFS State Code.

General Data Type: VARCHAR2

ALSCTYIN

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

Three character NMFS County Code.

General Data Type: VARCHAR2

NMFSCOUNTY

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

2 chararacter NMFS County Code.

General Data Type: VARCHAR2

DEALER

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

The Dealer Code.

General Data Type: VARCHAR2

NMFSGEAR

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

NMFS Gear Code.

General Data Type: VARCHAR2

NMFS_CODE

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

NMFS Species Code.

General Data Type: VARCHAR2

SHELLFIN

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

Shellfin Code.

General Data Type: VARCHAR2

POUNDS

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

Weight (pounds) of the fish landed . (WHole Weight, heads on for shrimp is the ALS standard.)

General Data Type: NUMBER

VALUE

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

Value in dollars of the fish that was caught.

General Data Type: NUMBER

SECTION

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

Section Code. There is not always meaningful data in this field.

General Data Type: VARCHAR2

PRICE

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

Average price per pound. The decimal point in this field is now real and is no longer implied.

General Data Type: NUMBER

DISTANCE

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

State that that fish was landed. There is not always meaningful data in this field. When a value of "00" is in this field, it means nothing, not anything else.

General Data Type: VARCHAR2

HOWFIGURED

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

Indicates how the price was determined for historical Florida data.

General Data Type: VARCHAR2

WHICHONE

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

Gives the source of the data.

General Data Type: VARCHAR2

TXSTATE

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

TPWD (Texas) State Code.

General Data Type: VARCHAR2

TXCOUNTY

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

TPWD (Texas) County Code.

General Data Type: NUMBER

TXWATER

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

TPWD (Texas) Water Body Code.

General Data Type: VARCHAR2

TXBAY

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

TPWD (Texas) Bay Code.

General Data Type: VARCHAR2

TXSPECIES

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

TPWD (Texas) Species Code.

General Data Type: NUMBER

LACOUNTY

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

LDWF (Louisiana) county codes.

General Data Type: VARCHAR2

LACONDITION

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

Condition code for Louisiana data.

General Data Type: VARCHAR2

FDEP_COAST

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

FDEP Coast Code. (Florida Data)

General Data Type: VARCHAR2

FDEPCTY

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

The County Code on data that comes from FDEP. (Florida Data)

General Data Type: VARCHAR2

FDEP_CODE

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

FDEP Species Code. (Florida)

General Data Type: VARCHAR2

FDEP_TRIPS

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

Number of trips made. It is entered on data that comes from FDEP.

General Data Type: NUMBER

INSHORE

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

Inshore code.

General Data Type: VARCHAR2

BLANK_1

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

A filler field.

General Data Type: VARCHAR2

BATCHNUM

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

Batch Number for data that comes from Florida.

General Data Type: VARCHAR2

BLANK_2

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

A filler field

General Data Type: VARCHAR2

CONVERSION

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

For Records that come from Florida, this is the conversion factor used to convert the landing weight provided by Florida to Whole pounds.

General Data Type: NUMBER

VAL_VAL

CC ID: 17330
Seq. Order: 36
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 13
Scale: 2
Status: Active
Description:

Summed ex-vessel value for trips with a reported price for a species. (FDEP Data)

General Data Type: NUMBER

VAL_LBS

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

Summed pounds for which price was reported for a species. (FDEP Data)

General Data Type: NUMBER

VAL_TRIPS

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

Number of trips which reported prices for a species. (FDEP Data)

General Data Type: NUMBER

FL_COMMON

CC ID: 17327
Seq. Order: 39
Data Storage Type: VARCHAR2
Max Length: 45
Required: No
Primary Key: No
Status: Active
Description:

Florida Common Name of the Species landed. It is used only for Florida data.

General Data Type: VARCHAR2

SUBGROUP

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

Subgroup. It is entered in the data that arrives from FDEP.

General Data Type: VARCHAR2

FLEDIT

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

Used for Florida data only. It may be "Y" for Editted data, or "N" for uneditted data.

General Data Type: VARCHAR2

PRINTSEQ

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

Print Sequence

General Data Type: VARCHAR2

UNFACTORED_WEIGHT_FDEP

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

Unfactore Weight From Florida

General Data Type: NUMBER

FDEP_CODE_TRIPTICKET

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

FDEP Code On The Trup Ticket

General Data Type: VARCHAR2

SOURCE_FILE

CC ID: 17321
Seq. Order: 45
Data Storage Type: VARCHAR2
Max Length: 50
Required: No
Primary Key: No
Status: Active
Description:

Source File used to load data.

General Data Type: VARCHAR2

WATERBODY

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

Water Body Code.

General Data Type: VARCHAR2

OLD_WATERBODY

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

Water Body code that had been on record before water body change project

General Data Type: VARCHAR2

REGION

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

Region Code

General Data Type: VARCHAR2

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:

NOAA/SEFSC Internal use only.

Metadata Access Constraints:

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

Metadata Use Constraints:

Use only Published Metadata.

Activity Log

Activity Log 1

CC ID: 25458
Activity Date/Time: 2008-01-17
Activity Type: Column Alteration
Responsible Party: Joshua Bennett
Description:

Changed width of DEALER column from 9 to 10. This was to accommodate new 10 digit codes from South Carolina. Changes were made to all ALS tables for uniformity.

Catalog Details

Catalog Item ID: 5451
GUID: gov.noaa.nmfs.inport:5451
Metadata Record Created By: Lee M Weinberger
Metadata Record Created: 2007-10-16 08:22+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