Search Help Show/Hide Menu
Metadata Rubric
100%
6 / 6
View Report
SEFSC Metadata Library > Fisheries Statistics Division > FISHERIES MONITORING > Commercial Catch and Effort > Commercial Landings Project > Commercial Fisheries Landings for U.S. Caribbea... > Puerto Rico Commercial Landings Statistics 1983... >

Table: ALS_LANDINGS_PUERTO_RICO

Entity (ENT)  |  Southeast Fisheries Science Center (SEFSC)
GUID: gov.noaa.nmfs.inport:5444  |  Updated: August 9, 2022  |  Published / External 
Summary
Item Identification
Keywords
Entity Info
Data Attributes
Access Info
Activity Log
Issues
Catalog Details

Summary

Abstract

Master Table For Landings From Puerto Rico. Though this table does have some effort data in it as well. Price data are also available in this table.

Description

Master Table For Landings From Puerto Rico. Though this table does have some effort data in it as well

Entity Information

Entity Type
Data Table

Data Attribute / Type Description
MONTH_LANDED
VARCHAR2 		Two Character Month Landed
YEAR_LANDED
VARCHAR2 		4 character Year Landed
STATE_LANDED
VARCHAR2 		State Code Landed. This is always loaded with the NMFS State Code For Puerto Rico ('55').
FISHING_CENTER
VARCHAR2 		Fishing Center Code. Generally, these are ordered by the geography of Puerto Rico from North > East > South > West around the island.
DEALER
VARCHAR2 		Dealer Code. Added For compatibility with other ALS Tables. This is column is always filled with all 9s as the Dealer is unknown.
WATER_BODY
VARCHAR2 		Water Body Code. This table only shows the water_body as '1866' for Puerto Rico waters. More detail can be found in the table jbennett.als_landings_puerto_rico_ed in the 'area fished' columns.
GEAR
VARCHAR2 		NMFS Gear Code (If One exists. It is generated between a cross table Of Erdman Gear Codes to NMFS Gear Code)
SPECIES
VARCHAR2 		NMFS Species Code (If One exists. It is generated between a cross table Of Erdman Species Codes to NMFS Species Codes)
SHELL_OR_FINFISH
VARCHAR2 		Finfish or shell fish code.
POUNDS
NUMBER 		Pounds Caught. (Whole weight). These are the pounds reported by the fishers. Adjustment (Correction) factors are supplied annually by Puerto Rico to account for those licensed Permit holders who did not report. These adjusted pounds are reported in the als_landings_puerto_rico_ed.
VALUE
NUMBER 		Value in dollars. This is the value of the reported landings (without adjusting for non-compliance.
SECTION
VARCHAR2 		Section Code, Added for compatibility with ALS.ALS_LANDINGS
PRICE
NUMBER 		Price payed for fish. (In dollars). These prices are collected from the fishers on the logbook reporting forms.
DISTANCE
VARCHAR2 		Distance From Shore Code. Added for compatibility with ALS.ALS_LANDINGS.
STATE_CAUGHT
VARCHAR2 		State Caught. Added For compatibility WIth ALS.ALS_LANDINGS
LANDING_DATE
DATE 		Actual Date animal was landed.
PR_ID_CODE
VARCHAR2 		Identification Code assigned to Fisher by Puerto Rico DNER. Sometimes the code is manufactured by the port agent and does not reflect the actual permit number. This is usually for permit holders who have recently been added to the licensing but for whom the agent did not yet have a code. The data manager has resolved these where possible.
PR_GEAR
VARCHAR2 		Erdman Gear Code. Erdman was the last name of the marine biologist responsible for cataloging the various species in the PR area. This particular list has been limited in scope. In 2012 the CCL gear list became available with more detail.
NUMBER_OF_TRIPS
NUMBER 		Number Of Trips. Prior to 2012, the forms could be used to report multiple trips, although fishers generally reported single trips. After 2012 only single trips could be reported.
PR_SPECIES
VARCHAR2 		Erdman Species Code
GEAR_QTY
NUMBER 		Number or size Of Gear. The combined field descriptors (quantity and size) has led to some confusion within this column (number of nets vs mesh size for instance).
GEAR_HOURS
NUMBER 		Soak Time for gear in hours. Traps are considered to have a soak time of 168 hours for a week of soaking without being hauled. This is not the same as the time the vessel is on the fishing grounds.
DAY_LANDED
VARCHAR2 		Day landed. Derived from landing date
USERID
VARCHAR2 		Oracle Id Of The Person Loading The Data
SOURCE_FILE
VARCHAR2 		Source File used to load data.
MINIMUM_DEPTH
NUMBER 		Minimum Depth Fished during the trip. This is intended to be recorded in fathoms (6 feet = 1 fathom).
MAXIMUM_DEPTH
NUMBER 		Maximum Depth Fished during the trip (recorded in fathoms).
TRIP_TICKET_NUMBER
VARCHAR2 		Trip Ticket Number. This number is assigned by Puerto Rico Fisheries Statistics group upon receiving the submitted forms on a form to form basis.

Child Items

No Child Items for this record.

Contact Information

No contact information is available for this record.

Please contact the owner organization (SEFSC) for inquiries on this record.

Item Identification

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

Master Table For Landings From Puerto Rico. Though this table does have some effort data in it as well. Price data are also available in this table.

Notes:

Loaded by batch 1725, 10-16-2007 05:43
Supplemental Information:

These are the original data sent by PR DNER. Another table: ALS.ALS_LANDINGS_PUERTO_RICO_ED, contains proposed edits to the data made at SEFSC.

Keywords

Spatial Keywords

Thesaurus Keyword
UNCONTROLLED
None puerto rico

Stratum Keywords

Thesaurus Keyword
UNCONTROLLED
None dealer
None fishing center
None landings
None month
None species
None year

Entity Information

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

Master Table For Landings From Puerto Rico. Though this table does have some effort data in it as well

Data Attributes

Attribute Summary

Rubric Score Primary Key? Name Type Description
100
 MONTH_LANDED VARCHAR2 Two Character Month Landed
100
 YEAR_LANDED VARCHAR2 4 character Year Landed
100
 STATE_LANDED VARCHAR2 State Code Landed. This is always loaded with the NMFS State Code For Puerto Rico ('55').
100
 FISHING_CENTER VARCHAR2 Fishing Center Code. Generally, these are ordered by the geography of Puerto Rico from North > East > South > West around the island.
100
 DEALER VARCHAR2 Dealer Code. Added For compatibility with other ALS Tables. This is column is always filled with all 9s as the Dealer is unknown.
100
 WATER_BODY VARCHAR2 Water Body Code. This table only shows the water_body as '1866' for Puerto Rico waters. More detail can be found in the table jbennett.als_landings_puerto_rico_ed in the 'area fished' columns.
100
 GEAR VARCHAR2 NMFS Gear Code (If One exists. It is generated between a cross table Of Erdman Gear Codes to NMFS Gear Code)
100
 SPECIES VARCHAR2 NMFS Species Code (If One exists. It is generated between a cross table Of Erdman Species Codes to NMFS Species Codes)
100
 SHELL_OR_FINFISH VARCHAR2 Finfish or shell fish code.
100
 POUNDS NUMBER Pounds Caught. (Whole weight). These are the pounds reported by the fishers. Adjustment (Correction) factors are supplied annually by Puerto Rico to account for those licensed Permit holders who did not report. These adjusted pounds are reported in the als_landings_puerto_rico_ed.
100
 VALUE NUMBER Value in dollars. This is the value of the reported landings (without adjusting for non-compliance.
100
 SECTION VARCHAR2 Section Code, Added for compatibility with ALS.ALS_LANDINGS
100
 PRICE NUMBER Price payed for fish. (In dollars). These prices are collected from the fishers on the logbook reporting forms.
100
 DISTANCE VARCHAR2 Distance From Shore Code. Added for compatibility with ALS.ALS_LANDINGS.
100
 STATE_CAUGHT VARCHAR2 State Caught. Added For compatibility WIth ALS.ALS_LANDINGS
100
 LANDING_DATE DATE Actual Date animal was landed.
100
 PR_ID_CODE VARCHAR2 Identification Code assigned to Fisher by Puerto Rico DNER. Sometimes the code is manufactured by the port agent and does not reflect the actual permit number. This is usually for permit holders who have recently been added to the licensing but for whom the agent did not yet have a code. The data manager has resolved these where possible.
100
 PR_GEAR VARCHAR2 Erdman Gear Code. Erdman was the last name of the marine biologist responsible for cataloging the various species in the PR area. This particular list has been limited in scope. In 2012 the CCL gear list became available with more detail.
100
 NUMBER_OF_TRIPS NUMBER Number Of Trips. Prior to 2012, the forms could be used to report multiple trips, although fishers generally reported single trips. After 2012 only single trips could be reported.
100
 PR_SPECIES VARCHAR2 Erdman Species Code
100
 GEAR_QTY NUMBER Number or size Of Gear. The combined field descriptors (quantity and size) has led to some confusion within this column (number of nets vs mesh size for instance).
100
 GEAR_HOURS NUMBER Soak Time for gear in hours. Traps are considered to have a soak time of 168 hours for a week of soaking without being hauled. This is not the same as the time the vessel is on the fishing grounds.
100
 DAY_LANDED VARCHAR2 Day landed. Derived from landing date
100
 USERID VARCHAR2 Oracle Id Of The Person Loading The Data
100
 SOURCE_FILE VARCHAR2 Source File used to load data.
100
 MINIMUM_DEPTH NUMBER Minimum Depth Fished during the trip. This is intended to be recorded in fathoms (6 feet = 1 fathom).
100
 MAXIMUM_DEPTH NUMBER Maximum Depth Fished during the trip (recorded in fathoms).
100
 TRIP_TICKET_NUMBER VARCHAR2 Trip Ticket Number. This number is assigned by Puerto Rico Fisheries Statistics group upon receiving the submitted forms on a form to form basis.

Attribute Details

MONTH_LANDED

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

Two Character Month Landed
General Data Type: VARCHAR2

YEAR_LANDED

CC ID: 17189
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

STATE_LANDED

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

State Code Landed. This is always loaded with the NMFS State Code For Puerto Rico ('55').
General Data Type: VARCHAR2

FISHING_CENTER

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

Fishing Center Code. Generally, these are ordered by the geography of Puerto Rico from North > East > South > West around the island.
General Data Type: VARCHAR2

DEALER

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

Dealer Code. Added For compatibility with other ALS Tables. This is column is always filled with all 9s as the Dealer is unknown.
General Data Type: VARCHAR2

WATER_BODY

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

Water Body Code. This table only shows the water_body as '1866' for Puerto Rico waters. More detail can be found in the table jbennett.als_landings_puerto_rico_ed in the 'area fished' columns.
General Data Type: VARCHAR2

GEAR

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

NMFS Gear Code (If One exists. It is generated between a cross table Of Erdman Gear Codes to NMFS Gear Code)
General Data Type: VARCHAR2

SPECIES

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

NMFS Species Code (If One exists. It is generated between a cross table Of Erdman Species Codes to NMFS Species Codes)
General Data Type: VARCHAR2

SHELL_OR_FINFISH

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

Finfish or shell fish code.
General Data Type: VARCHAR2

POUNDS

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

Pounds Caught. (Whole weight). These are the pounds reported by the fishers. Adjustment (Correction) factors are supplied annually by Puerto Rico to account for those licensed Permit holders who did not report. These adjusted pounds are reported in the als_landings_puerto_rico_ed.
General Data Type: NUMBER

VALUE

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

Value in dollars. This is the value of the reported landings (without adjusting for non-compliance.
General Data Type: NUMBER

SECTION

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

Section Code, Added for compatibility with ALS.ALS_LANDINGS
General Data Type: VARCHAR2

PRICE

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

Price payed for fish. (In dollars). These prices are collected from the fishers on the logbook reporting forms.
General Data Type: NUMBER

DISTANCE

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

Distance From Shore Code. Added for compatibility with ALS.ALS_LANDINGS.
General Data Type: VARCHAR2

STATE_CAUGHT

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

State Caught. Added For compatibility WIth ALS.ALS_LANDINGS
General Data Type: VARCHAR2

LANDING_DATE

CC ID: 17175
Seq. Order: 16
Data Storage Type: DATE
Max Length: 7
Required: No
Primary Key: No
Status: Active
Description:

Actual Date animal was landed.
General Data Type: DATE

PR_ID_CODE

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

Identification Code assigned to Fisher by Puerto Rico DNER. Sometimes the code is manufactured by the port agent and does not reflect the actual permit number. This is usually for permit holders who have recently been added to the licensing but for whom the agent did not yet have a code. The data manager has resolved these where possible.
General Data Type: VARCHAR2

PR_GEAR

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

Erdman Gear Code. Erdman was the last name of the marine biologist responsible for cataloging the various species in the PR area. This particular list has been limited in scope. In 2012 the CCL gear list became available with more detail.
General Data Type: VARCHAR2

NUMBER_OF_TRIPS

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

Number Of Trips. Prior to 2012, the forms could be used to report multiple trips, although fishers generally reported single trips. After 2012 only single trips could be reported.
General Data Type: NUMBER

PR_SPECIES

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

Erdman Species Code
General Data Type: VARCHAR2

GEAR_QTY

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

Number or size Of Gear. The combined field descriptors (quantity and size) has led to some confusion within this column (number of nets vs mesh size for instance).

General Data Type: NUMBER

GEAR_HOURS

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

Soak Time for gear in hours. Traps are considered to have a soak time of 168 hours for a week of soaking without being hauled. This is not the same as the time the vessel is on the fishing grounds.
General Data Type: NUMBER

DAY_LANDED

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

Day landed. Derived from landing date
General Data Type: VARCHAR2

USERID

CC ID: 17195
Seq. Order: 24
Data Storage Type: VARCHAR2
Max Length: 30
Required: No
Primary Key: No
Status: Active
Description:

Oracle Id Of The Person Loading The Data
General Data Type: VARCHAR2

SOURCE_FILE

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

Source File used to load data.
General Data Type: VARCHAR2

MINIMUM_DEPTH

CC ID: 17193
Seq. Order: 26
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Minimum Depth Fished during the trip. This is intended to be recorded in fathoms (6 feet = 1 fathom).
General Data Type: NUMBER

MAXIMUM_DEPTH

CC ID: 17192
Seq. Order: 27
Data Storage Type: NUMBER
Max Length: 22
Required: No
Primary Key: No
Precision: 4
Scale: 0
Status: Active
Description:

Maximum Depth Fished during the trip (recorded in fathoms).
General Data Type: NUMBER

TRIP_TICKET_NUMBER

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

Trip Ticket Number. This number is assigned by Puerto Rico Fisheries Statistics group upon receiving the submitted forms on a form to form basis.
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:

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:

Use Published Metadata only.

Activity Log

Activity Log 1

CC ID: 103762
Activity Date/Time: 2013-03-13
Activity Type: UPDATE
Responsible Party: Joshua Bennett
Description:

An update was done to the PR_ID_CODE for 1,081 records from 2008-2011 to correct improper permit ids in table. Edits were made by comparing ids to permit lists obtained from Puerto Rico and by observing sequence of trip_ticket_numbers to determine if a number had been mis-entered. Update file was PR_ID_FIX_06mar13.xlsx.

Activity Log 2

CC ID: 154457
Activity Date/Time: 2013-06-06
Activity Type: UPDATE
Responsible Party: Joshua Bennett
Description:

An update was made to the DISTANCE column. All 'Y' (greater than 10 NM) were set to DISTANCE code 'C'. All 'N' (10 NM or less) records were set to code 'B'. 2009 distance codes were updated as they were not previously loaded. An update was also done to year 2012 from the CCL data of code '7' (9 miles to 200 miles) where the info existed in CCL. This needs to be a part of the load process from now on.

Activity Log 3

CC ID: 355830
Activity Date/Time: 2016-11-03
Activity Type: Column Reformat
Responsible Party: Joshua Bennett
Description:

Reformatted Pounds column to accept decimals from Caribbean Commercial Logbook extracts. Previous imports had been rounding numbers leading to slight discrepancies. Data now exact match.

Issues

Issue 1

CC ID: 154458
Issue Date: 2013-06-06
Issue:

Distance from shore data not supplied for 2010 and 2011. Distance data currently not present prior to 2003.

Issue 2

CC ID: 355829
Issue Date: 2016-11-03
Author: Bennett, Joshua
Issue:

Pounds column in ALS.ALS_LANDINGS_PUERTO_RICO previously formatted as NUMBER (9,0) was rounding decimals. Did not match exactly with CCL extract data. Column reformatted to NUMBER (9,3). (landings for trips do not approach 5 digits). Problem fixed.

Catalog Details

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