5443
Table: ALS_LANDINGS7278
ALS_LANDINGS7278
Entity
Published / External
2201
Southeast Region 1972-1976 general canvass statistics
Data Set
Completed
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
Loaded by batch 1724, 10-16-2007 04:33
Theme
gulf states
Theme
landings
Spatial
alabama
Spatial
florida
Spatial
louisiana
Spatial
mississippi
Southeast Fisheries Science Center
Miami
FL
USA
75 Virginia Beach Drive
Miami, FL 33149
Data Table
Yes
ALS
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.
1
MONTHLAND
VARCHAR2
2
No
No
Active
Month Landed.
VARCHAR2
2
YEARLAND
VARCHAR2
4
No
No
Active
4 character Year Landed
VARCHAR2
3
ALSSTATE
VARCHAR2
2
No
No
Active
The state code.
VARCHAR2
4
ALSCTYIN
VARCHAR2
3
No
No
Active
The 3 character county code.
VARCHAR2
5
NMFSCOUNTY
VARCHAR2
2
No
No
Active
Two digit county code. (NMFS)
VARCHAR2
6
DEALER
VARCHAR2
9
No
No
Active
Dealer Code.
VARCHAR2
7
WATERBODY
VARCHAR2
4
No
No
Active
Water Body Code.
VARCHAR2
8
NMFSGEAR
VARCHAR2
3
No
No
Active
Gear Code. (NMFS)
VARCHAR2
9
NMFS_CODE
VARCHAR2
4
No
No
Active
Species Code.
VARCHAR2
10
SHELLFIN
VARCHAR2
1
No
No
Active
Shellfish or Finfish Code.
VARCHAR2
11
POUNDS
NUMBER
22
No
No
9
0
Active
Weight.
NUMBER
12
VALUE
NUMBER
22
No
No
9
0
Active
Value.
NUMBER
13
SECTION
VARCHAR2
1
No
No
Active
Section Code.
VARCHAR2
14
PRICE
NUMBER
22
No
No
7
3
Active
Price payed. (Decimal point is actual)
NUMBER
15
DISTANCE
VARCHAR2
1
No
No
Active
Distance From Shore Code.
VARCHAR2
16
STATECAUGHT
VARCHAR2
2
No
No
Active
State Caught.
VARCHAR2
17
HOWFIGURED
VARCHAR2
2
No
No
Active
How the price was determined.
VARCHAR2
18
WHICHONE
VARCHAR2
2
No
No
Active
A code corresponding to the source of the data.
VARCHAR2
19
TXSTATE
VARCHAR2
2
No
No
Active
TPWD (Texas) State Code.
VARCHAR2
20
TXCOUNTY
NUMBER
22
No
No
3
0
Active
TPWD (Texas) County Code.
NUMBER
21
TXWATER
VARCHAR2
3
No
No
Active
TPWD (Texas) Water Body Code.
VARCHAR2
22
TXBAY
VARCHAR2
2
No
No
Active
TPWD (Texas) Bay Code.
VARCHAR2
23
TXSPECIES
NUMBER
22
No
No
5
0
Active
TPWD (Texas) Species Code.
NUMBER
24
LACOUNTY
VARCHAR2
2
No
No
Active
LDWF County Code. (Louisiana)
VARCHAR2
25
LACONDITION
VARCHAR2
1
No
No
Active
LDWF Condition Code. (Louisiana)
VARCHAR2
26
FDEP_COAST
VARCHAR2
1
No
No
Active
The FDEP (Florida) Coast Code.
VARCHAR2
27
FDEPCTY
VARCHAR2
2
No
No
Active
FDEP (Florida) County Code.
VARCHAR2
28
FDEP_CODE
VARCHAR2
3
No
No
Active
The FDEP (Florida) Species Code.
VARCHAR2
29
FDEP_TRIPS
NUMBER
22
No
No
6
0
Active
Number of Trips for FDEP (Florida) data.
NUMBER
30
INSHORE
VARCHAR2
1
No
No
Active
In shore code.
VARCHAR2
31
BLANK_1
VARCHAR2
1
No
No
Active
Blank field.
VARCHAR2
32
BATCHNUM
VARCHAR2
4
No
No
Active
Batch Number for FDEP (Florida) Data
VARCHAR2
33
BLANK_2
VARCHAR2
1
No
No
Active
Blank field.
VARCHAR2
34
CONVERSION
NUMBER
22
No
No
8
5
Active
Conversion factor.
NUMBER
35
VAL_VAL
NUMBER
22
No
No
12
0
Active
Summed ex-vessel value for trips with a reported prices for a species. For FDEP (Florida) data.
NUMBER
36
VAL_LBS
NUMBER
22
No
No
9
0
Active
Summed pounds for which price was reported for a species. For FDEP (Florida) data.
NUMBER
37
VAL_TRIPS
NUMBER
22
No
No
6
0
Active
Number of trips which reported prices for a species. For FDEP (Florida) data.
NUMBER
38
FL_COMMON
VARCHAR2
45
No
No
Active
Common name for data that arrice from FDEP (Florida)
VARCHAR2
39
SUBGROUP
VARCHAR2
1
No
No
Active
Subgroup for FDEP (Florida) data,
VARCHAR2
40
FLEDIT
VARCHAR2
1
No
No
Active
Whether Florida Data is Editted or Uneditted.
VARCHAR2
41
RNUMBER
NUMBER
22
No
No
7
0
Active
Record Number.
NUMBER
42
OLD_WATERBODY
VARCHAR2
4
No
No
Active
Waterbody Code That originally was on the record
VARCHAR2
43
REGION
VARCHAR2
2
No
No
Active
Region Code. Not used For this table
VARCHAR2
44
UNFACTORED_WEIGHT_FDEP
NUMBER
22
No
No
9
0
Active
Unfactored Weight From FLorida. This column had been added for compatibility purposes with other Landings Tables, but is not used in this table.
NUMBER
Confidential
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
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.
See NOAA Administrative Order 216-100
NOAA ADMINISTRATIVE ORDER SERIES
Date of Issuance: July 26, 1994
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.
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.
Confidential data are not to be released in any publication, report, oral presentation, or other means to the public.
Non-published Metadata access is restricted. Published Metadata is available to the public.
Only use Published Metadata.
2008-01-17
Column Alteration
Bennett, Joshua
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.
2011-06-10
Joshua E. Bennett
Shrimp gear is NULL in table for Gulf of Mexico region. Neither is it present in source table GSS.GSS_GULF_SHRIMP_56_83.
gov.noaa.nmfs.inport:5443
Lee Weinberger
2007-10-16T04:33:48
SysAdmin InPortAdmin
2022-08-09T17:10:59
2021-05-06
Southeast Fisheries Science Center
SEFSC
75 Virginia Beach Drive
Miami
FL
33149
USA
(305)361-5761
www.sefsc.noaa.gov
8:00 a.m. - 4:30 p.m. EST
1001
Public
No
2021-05-06
1 Year
2022-05-06