Table: ALS_LANDINGS7278
Entity (ENT) | Southeast Fisheries Science Center (SEFSC)GUID: gov.noaa.nmfs.inport:5443 | Updated: August 9, 2022 | Published / External
Item Identification
Title: | Table: ALS_LANDINGS7278 |
---|---|
Short Name: | ALS_LANDINGS7278 |
Status: | Completed |
Abstract: |
This table originally contained the historical data that was in the file (MI00DLDG)DATA/LANDINGS7278 on the A7. It contains a mix of monthly and annual data for the gulf states. This oracle table was created during a conversion from the A7 flat files to Oracle tables in 1995 Overtime certain data was moved from this table to ALS_LANDINGS |
Notes: |
Loaded by batch 1724, 10-16-2007 04:33 |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | gulf states |
None | landings |
Spatial Keywords
Thesaurus | Keyword |
---|---|
UNCONTROLLED | |
None | alabama |
None | florida |
None | louisiana |
None | mississippi |
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 the historical data that was in the file (MI00DLDG)DATA/LANDINGS7278 on the A7. It contains a mix of monthly an annual data for the gulf states. |
Data Attributes
Attribute Summary
Name | Type | Description | ||
---|---|---|---|---|
100
|
MONTHLAND | VARCHAR2 | Month Landed. | |
100
|
YEARLAND | VARCHAR2 | 4 character Year Landed | |
100
|
ALSSTATE | VARCHAR2 | The state code. | |
100
|
ALSCTYIN | VARCHAR2 | The 3 character county code. | |
100
|
NMFSCOUNTY | VARCHAR2 | Two digit county code. (NMFS) | |
100
|
DEALER | VARCHAR2 | Dealer Code. | |
100
|
WATERBODY | VARCHAR2 | Water Body Code. | |
100
|
NMFSGEAR | VARCHAR2 | Gear Code. (NMFS) | |
100
|
NMFS_CODE | VARCHAR2 | Species Code. | |
100
|
SHELLFIN | VARCHAR2 | Shellfish or Finfish Code. | |
100
|
POUNDS | NUMBER | Weight. | |
100
|
VALUE | NUMBER | Value. | |
100
|
SECTION | VARCHAR2 | Section Code. | |
100
|
PRICE | NUMBER | Price payed. (Decimal point is actual) | |
100
|
DISTANCE | VARCHAR2 | Distance From Shore Code. | |
100
|
STATECAUGHT | VARCHAR2 | State Caught. | |
100
|
HOWFIGURED | VARCHAR2 | How the price was determined. | |
100
|
WHICHONE | VARCHAR2 | A code corresponding to 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 County Code. (Louisiana) | |
100
|
LACONDITION | VARCHAR2 | LDWF Condition Code. (Louisiana) | |
100
|
FDEP_COAST | VARCHAR2 | The FDEP (Florida) Coast Code. | |
100
|
FDEPCTY | VARCHAR2 | FDEP (Florida) County Code. | |
100
|
FDEP_CODE | VARCHAR2 | The FDEP (Florida) Species Code. | |
100
|
FDEP_TRIPS | NUMBER | Number of Trips for FDEP (Florida) data. | |
100
|
INSHORE | VARCHAR2 | In shore code. | |
100
|
BLANK_1 | VARCHAR2 | Blank field. | |
100
|
BATCHNUM | VARCHAR2 | Batch Number for FDEP (Florida) Data | |
100
|
BLANK_2 | VARCHAR2 | Blank field. | |
100
|
CONVERSION | NUMBER | Conversion factor. | |
100
|
VAL_VAL | NUMBER | Summed ex-vessel value for trips with a reported prices for a species. For FDEP (Florida) data. | |
100
|
VAL_LBS | NUMBER | Summed pounds for which price was reported for a species. For FDEP (Florida) data. | |
100
|
VAL_TRIPS | NUMBER | Number of trips which reported prices for a species. For FDEP (Florida) data. | |
100
|
FL_COMMON | VARCHAR2 | Common name for data that arrice from FDEP (Florida) | |
100
|
SUBGROUP | VARCHAR2 | Subgroup for FDEP (Florida) data, | |
100
|
FLEDIT | VARCHAR2 | Whether Florida Data is Editted or Uneditted. | |
100
|
RNUMBER | NUMBER | Record Number. | |
100
|
OLD_WATERBODY | VARCHAR2 | Waterbody Code That originally was on the record | |
100
|
REGION | VARCHAR2 | Region Code. Not used For this table | |
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. |
Attribute Details
MONTHLAND
Seq. Order: | 1 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Month Landed. |
General Data Type: | VARCHAR2 |
YEARLAND
Seq. Order: | 2 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
4 character Year Landed |
General Data Type: | VARCHAR2 |
ALSSTATE
Seq. Order: | 3 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The state code. |
General Data Type: | VARCHAR2 |
ALSCTYIN
Seq. Order: | 4 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The 3 character county code. |
General Data Type: | VARCHAR2 |
NMFSCOUNTY
Seq. Order: | 5 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Two digit county code. (NMFS) |
General Data Type: | VARCHAR2 |
DEALER
Seq. Order: | 6 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 9 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Dealer Code. |
General Data Type: | VARCHAR2 |
WATERBODY
Seq. Order: | 7 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Water Body Code. |
General Data Type: | VARCHAR2 |
NMFSGEAR
Seq. Order: | 8 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Gear Code. (NMFS) |
General Data Type: | VARCHAR2 |
NMFS_CODE
Seq. Order: | 9 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Species Code. |
General Data Type: | VARCHAR2 |
SHELLFIN
Seq. Order: | 10 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Shellfish or Finfish Code. |
General Data Type: | VARCHAR2 |
POUNDS
Seq. Order: | 11 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Weight. |
General Data Type: | NUMBER |
VALUE
Seq. Order: | 12 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 9 |
Scale: | 0 |
Status: | Active |
Description: |
Value. |
General Data Type: | NUMBER |
SECTION
Seq. Order: | 13 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Section Code. |
General Data Type: | VARCHAR2 |
PRICE
Seq. Order: | 14 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 7 |
Scale: | 3 |
Status: | Active |
Description: |
Price payed. (Decimal point is actual) |
General Data Type: | NUMBER |
DISTANCE
Seq. Order: | 15 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Distance From Shore Code. |
General Data Type: | VARCHAR2 |
STATECAUGHT
Seq. Order: | 16 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
State Caught. |
General Data Type: | VARCHAR2 |
HOWFIGURED
Seq. Order: | 17 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
How the price was determined. |
General Data Type: | VARCHAR2 |
WHICHONE
Seq. Order: | 18 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
A code corresponding to the source of the data. |
General Data Type: | VARCHAR2 |
TXSTATE
Seq. Order: | 19 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
TPWD (Texas) State Code. |
General Data Type: | VARCHAR2 |
TXCOUNTY
Seq. Order: | 20 |
---|---|
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
Seq. Order: | 21 |
---|---|
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
Seq. Order: | 22 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
TPWD (Texas) Bay Code. |
General Data Type: | VARCHAR2 |
TXSPECIES
Seq. Order: | 23 |
---|---|
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
Seq. Order: | 24 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
LDWF County Code. (Louisiana) |
General Data Type: | VARCHAR2 |
LACONDITION
Seq. Order: | 25 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
LDWF Condition Code. (Louisiana) |
General Data Type: | VARCHAR2 |
FDEP_COAST
Seq. Order: | 26 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The FDEP (Florida) Coast Code. |
General Data Type: | VARCHAR2 |
FDEPCTY
Seq. Order: | 27 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
FDEP (Florida) County Code. |
General Data Type: | VARCHAR2 |
FDEP_CODE
Seq. Order: | 28 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 3 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
The FDEP (Florida) Species Code. |
General Data Type: | VARCHAR2 |
FDEP_TRIPS
Seq. Order: | 29 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 6 |
Scale: | 0 |
Status: | Active |
Description: |
Number of Trips for FDEP (Florida) data. |
General Data Type: | NUMBER |
INSHORE
Seq. Order: | 30 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
In shore code. |
General Data Type: | VARCHAR2 |
BLANK_1
Seq. Order: | 31 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Blank field. |
General Data Type: | VARCHAR2 |
BATCHNUM
Seq. Order: | 32 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Batch Number for FDEP (Florida) Data |
General Data Type: | VARCHAR2 |
BLANK_2
Seq. Order: | 33 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Blank field. |
General Data Type: | VARCHAR2 |
CONVERSION
Seq. Order: | 34 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 8 |
Scale: | 5 |
Status: | Active |
Description: |
Conversion factor. |
General Data Type: | NUMBER |
VAL_VAL
Seq. Order: | 35 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 12 |
Scale: | 0 |
Status: | Active |
Description: |
Summed ex-vessel value for trips with a reported prices for a species. For FDEP (Florida) data. |
General Data Type: | NUMBER |
VAL_LBS
Seq. Order: | 36 |
---|---|
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. For FDEP (Florida) data. |
General Data Type: | NUMBER |
VAL_TRIPS
Seq. Order: | 37 |
---|---|
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. For FDEP (Florida) data. |
General Data Type: | NUMBER |
FL_COMMON
Seq. Order: | 38 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 45 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Common name for data that arrice from FDEP (Florida) |
General Data Type: | VARCHAR2 |
SUBGROUP
Seq. Order: | 39 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Subgroup for FDEP (Florida) data, |
General Data Type: | VARCHAR2 |
FLEDIT
Seq. Order: | 40 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 1 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Whether Florida Data is Editted or Uneditted. |
General Data Type: | VARCHAR2 |
RNUMBER
Seq. Order: | 41 |
---|---|
Data Storage Type: | NUMBER |
Max Length: | 22 |
Required: | No |
Primary Key: | No |
Precision: | 7 |
Scale: | 0 |
Status: | Active |
Description: |
Record Number. |
General Data Type: | NUMBER |
OLD_WATERBODY
Seq. Order: | 42 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 4 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Waterbody Code That originally was on the record |
General Data Type: | VARCHAR2 |
REGION
Seq. Order: | 43 |
---|---|
Data Storage Type: | VARCHAR2 |
Max Length: | 2 |
Required: | No |
Primary Key: | No |
Status: | Active |
Description: |
Region Code. Not used For this table |
General Data Type: | VARCHAR2 |
UNFACTORED_WEIGHT_FDEP
Seq. Order: | 44 |
---|---|
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 |
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: |
Password restricted. 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 use Published Metadata. |
Activity Log
Activity Log 1
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. |
Issues
Issue 1
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: | 5443 |
---|---|
GUID: | gov.noaa.nmfs.inport:5443 |
Metadata Record Created By: | Lee M Weinberger |
Metadata Record Created: | 2007-10-16 04:33+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 |