5451 ALS_TEMP_LAND Entity Published / External 1916 Commercial Landings Data monthly summaries (Dealers) Data Set Completed Pre-validation Table to load Accumulative Landings Data Loaded by batch 1726, 10-16-2007 08:22 Theme landings Theme staging table Southeast Fisheries Science Center Miami FL USA Data Table Yes ALS Pre-validation Table to load Accumulative Landings Data 1 UNIXID VARCHAR2 8 No No Active Id of the person loading data VARCHAR2 2 RNUMBER NUMBER 22 No No 7 0 Active Which Record Number In the data file that is loaded. NUMBER 3 MONTHLAND VARCHAR2 2 No No Active Two character month that the data was landed. VARCHAR2 4 YEARLAND VARCHAR2 4 No No Active Four digit year that the fish was landed. VARCHAR2 5 ALSSTATE VARCHAR2 2 No No Active Two character NMFS State Code. VARCHAR2 6 ALSCTYIN VARCHAR2 3 No No Active Three character NMFS County Code. VARCHAR2 7 NMFSCOUNTY VARCHAR2 2 No No Active 2 chararacter NMFS County Code. VARCHAR2 8 DEALER VARCHAR2 9 No No Active The Dealer Code. VARCHAR2 9 NMFSGEAR VARCHAR2 3 No No Active NMFS Gear Code. VARCHAR2 10 NMFS_CODE VARCHAR2 4 No No Active NMFS Species Code. VARCHAR2 11 SHELLFIN VARCHAR2 1 No No Active Shellfin Code. VARCHAR2 12 POUNDS NUMBER 22 No No 9 0 Active Weight (pounds) of the fish landed . (WHole Weight, heads on for shrimp is the ALS standard.) NUMBER 13 VALUE NUMBER 22 No No 9 0 Active Value in dollars of the fish that was caught. NUMBER 14 SECTION VARCHAR2 1 No No Active Section Code. There is not always meaningful data in this field. VARCHAR2 15 PRICE NUMBER 22 No No 7 3 Active Average price per pound. The decimal point in this field is now real and is no longer implied. NUMBER 16 DISTANCE VARCHAR2 1 No No Active The Distance From Shore Code. VARCHAR2 17 STATECAUGHT VARCHAR2 2 No No Active 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. VARCHAR2 18 HOWFIGURED VARCHAR2 2 No No Active Indicates how the price was determined for historical Florida data. VARCHAR2 19 WHICHONE VARCHAR2 2 No No Active Gives the source of the data. VARCHAR2 20 TXSTATE VARCHAR2 2 No No Active TPWD (Texas) State Code. VARCHAR2 21 TXCOUNTY NUMBER 22 No No 3 0 Active TPWD (Texas) County Code. NUMBER 22 TXWATER VARCHAR2 3 No No Active TPWD (Texas) Water Body Code. VARCHAR2 23 TXBAY VARCHAR2 2 No No Active TPWD (Texas) Bay Code. VARCHAR2 24 TXSPECIES NUMBER 22 No No 5 0 Active TPWD (Texas) Species Code. NUMBER 25 LACOUNTY VARCHAR2 2 No No Active LDWF (Louisiana) county codes. VARCHAR2 26 LACONDITION VARCHAR2 1 No No Active Condition code for Louisiana data. VARCHAR2 27 FDEP_COAST VARCHAR2 1 No No Active FDEP Coast Code. (Florida Data) VARCHAR2 28 FDEPCTY VARCHAR2 2 No No Active The County Code on data that comes from FDEP. (Florida Data) VARCHAR2 29 FDEP_CODE VARCHAR2 3 No No Active FDEP Species Code. (Florida) VARCHAR2 30 FDEP_TRIPS NUMBER 22 No No 6 0 Active Number of trips made. It is entered on data that comes from FDEP. NUMBER 31 INSHORE VARCHAR2 1 No No Active Inshore code. VARCHAR2 32 BLANK_1 VARCHAR2 1 No No Active A filler field. VARCHAR2 33 BATCHNUM VARCHAR2 6 No No Active Batch Number for data that comes from Florida. VARCHAR2 34 BLANK_2 VARCHAR2 1 No No Active A filler field VARCHAR2 35 CONVERSION NUMBER 22 No No 9 5 Active For Records that come from Florida, this is the conversion factor used to convert the landing weight provided by Florida to Whole pounds. NUMBER 36 VAL_VAL NUMBER 22 No No 13 2 Active Summed ex-vessel value for trips with a reported price for a species. (FDEP Data) NUMBER 37 VAL_LBS NUMBER 22 No No 9 0 Active Summed pounds for which price was reported for a species. (FDEP Data) NUMBER 38 VAL_TRIPS NUMBER 22 No No 6 0 Active Number of trips which reported prices for a species. (FDEP Data) NUMBER 39 FL_COMMON VARCHAR2 45 No No Active Florida Common Name of the Species landed. It is used only for Florida data. VARCHAR2 40 SUBGROUP VARCHAR2 1 No No Active Subgroup. It is entered in the data that arrives from FDEP. VARCHAR2 41 FLEDIT VARCHAR2 1 No No Active Used for Florida data only. It may be "Y" for Editted data, or "N" for uneditted data. VARCHAR2 42 PRINTSEQ VARCHAR2 3 No No Active Print Sequence VARCHAR2 43 UNFACTORED_WEIGHT_FDEP NUMBER 22 No No 9 0 Active Unfactore Weight From Florida NUMBER 44 FDEP_CODE_TRIPTICKET VARCHAR2 3 No No Active FDEP Code On The Trup Ticket VARCHAR2 45 SOURCE_FILE VARCHAR2 50 No No Active Source File used to load data. VARCHAR2 46 WATERBODY VARCHAR2 4 No No Active Water Body Code. VARCHAR2 47 OLD_WATERBODY VARCHAR2 4 No No Active Water Body code that had been on record before water body change project VARCHAR2 48 REGION VARCHAR2 2 No No Active Region Code VARCHAR2 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. 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. NOAA/SEFSC Internal use only. Non-published Metadata access is restricted. Published Metadata is available to the public. Use only 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. gov.noaa.nmfs.inport:5451 Lee Weinberger 2007-10-16T08:22:52 Lee Weinberger 2024-06-14T14:05:19 2024-06-14 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