Skip to main content
U.S. flag

An official website of the United States government

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Secure .gov websites use HTTPS
A lock ( ) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Skip to content

Catch-In-Areas Main

Metadata Updated: May 24, 2025

The Catch-In-Areas database integrates catch data from the Catch Accounting System (which has the spatial resolution of a NMFS Reporting Area) into a database that resolves the GIS data into polygons of approximately 7.5 km. In unrestricted outside waters, sixty four grid IDs fit inside one state statistical area. A state statistical area is = degree in latitude and one degree in longitude block. The 7.5 km grid size was picked for two reasons 1) we were likely to pick up at least one 30 minute VMS ping for a vessel running at fishing speed; and 2) the size (.125 degree latitude) is perfectly divisible in geographic coordinates so they fit perfectly inside a state statistical area. The grid polygons are often further divided into smaller polygons by the boundary of state statistical areas, the boundary of state and federal waters, or by the boundary of Steller sea lion critical habitat (broken out at 3, 6, 10, and 20 nautical miles from each of the 154 Steller sea lion rookeries and haulouts). Where confidentiality and mapping is an issue, seven-kilometer polygon are pre-coded for grouping into (3x3) 23km polygons. Each grid-id can queried individually or by sets of pre-coded attributes, such as reporting area and distance from Steller sea lion sites.

Access & Use Information

License: No license information was provided. If this work was prepared by an officer or employee of the United States government as part of that person's official duties it is considered a U.S. Government Work.

Downloads & Resources

Dates

Metadata Date May 15, 2025
Metadata Created Date October 19, 2024
Metadata Updated Date May 24, 2025
Reference Date(s) September 2, 2015 (publication)
Frequency Of Update daily

Metadata Source

Harvested from NMFS AKRO

Additional Metadata

Resource Type Dataset
Metadata Date May 15, 2025
Metadata Created Date October 19, 2024
Metadata Updated Date May 24, 2025
Reference Date(s) September 2, 2015 (publication)
Responsible Party (Point of Contact, Custodian)
Contact Email
Guid gov.noaa.nmfs.inport:27363
Access Constraints Cite As: Alaska Regional Office, [Date of Access]: Catch-In-Areas Main [Data Date Range], https://www.fisheries.noaa.gov/inport/item/27363., Access Constraints: None, Use Constraints: None, Distribution Liability: Confidential Fisheries Data
Bbox East Long -129
Bbox North Lat 69
Bbox South Lat 47
Bbox West Long -180
Coupled Resource
Frequency Of Update daily
Harvest Object Id 2bf541ef-696c-44af-855b-b8ddb10b5b09
Harvest Source Id 4461dba7-fc74-401a-8a38-13caddf3aaa5
Harvest Source Title NMFS AKRO
Licence NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose.
Lineage Observed Fleet We begin by separating VMS records as observed catch or unobserved. A record is considered observed when the federal observer logs the deploy time and retrieve time of a haul. The VMS records are processed when the vessel-id and date-time are within the observed times. Unobserved Fleet A portion of the fishing fleet is unobserved because they are too small, are within a gray area of being a partially observed, or simply do not require a federal observer. Many of these vessels only report the state statistical area where they fished and time period (in days) when they were fishing. Almost all of these vessels are required to carry VMS though. Instead of attempting to build a line based on unobserved VMS data where data may be sparse and spread-out, we instead depend on the VMS-points intersected onto the grid-id feature class. After the lines are created, they are moved back to SQL Server and intersected onto the Grid Area GIS feature class. This spatial intersect operations splits each line into parts that are referenced by the grid IDs. The Catch-In-Area database attributes catch based on the effort a vessel spends fishing. In order to apply the effort, we divide the line length [by grid id] by the total line length. This gives us the proportion of the line falling into each grid id. In affect the Catch-In-Areas is an effort based product. Data is spatially intersected onto Grid and then joined to V_CAS_Primary_All using a precise matching algorithm. The final table includes data from five tables [V_CAS_TXN_PRIMARY_ALL] .V_ELPR_VWPR_PRODUCT .V_ELLR_SLOG_PRODUCT .V_OBS_HAUL .V_VMS_VESSEL_LOCATION .V_OBS_HAUL_SPECIES_ALL]
Metadata Language eng
Metadata Type geospatial
Old Spatial {"type": "Polygon", "coordinates": [[[-180.0, 47.0], [-129.0, 47.0], [-129.0, 69.0], [-180.0, 69.0], [-180.0, 47.0]]]}
Progress completed
Spatial Data Service Type
Spatial Reference System
Spatial Harvester True
Temporal Extent Begin 2003

Didn't find what you're looking for? Suggest a dataset here.