gov.noaa.nmfs.inport:27363 eng UTF8 dataset Database Alaska Regional Office (907)586-7202 709 W. 9th St, P.O. Box 21668 Juneau AK 99802-1668 USA https://alaskafisheries.noaa.gov/ WWW:LINK-1.0-http--link Website Website for this organization information 8:00 am - 4:30 pm, Mon-Fri. resourceProvider Jahn, Abby 709 West 9th Street Juneau AK 99801 USA abby.jahn@noaa.gov email pointOfContact Gasper, Jason R jason.gasper@noaa.gov pointOfContact 2025-11-12T21:56:13 ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data ISO 19115-2:2009(E) Catch-In-Areas Main Catch-In-Areas 2015-09-02 publication NOAA/NMFS/EDM 27363 https://www.fisheries.noaa.gov/inport/item/27363 WWW:LINK-1.0-http--link Full Metadata Record View the complete metadata record on InPort for more information about this dataset. information documentDigital Steve Lewis 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. 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.8 km. The spatial resolution is added to Catch Accounting using a combination of Observer and VMS data, where for observed vessels observer data is joined with VMS data; for unobserved vessels, VMS data is used to find fishing locations based on time periods and reported state statistical areas. Steve Lewis, NOAA Fisheries, Alaska Region completed Jahn, Abby 709 West 9th Street Juneau AK 99801 USA abby.jahn@noaa.gov email pointOfContact Gasper, Jason R jason.gasper@noaa.gov pointOfContact Jahn, Abby 709 West 9th Street Juneau AK 99801 USA abby.jahn@noaa.gov email: abby.jahn@noaa.gov custodian Gasper, Jason R jason.gasper@noaa.gov custodian daily Alaska Fisheries CIA Catch-In-Areas GIS catch accounting catch data polygon spatial theme DOC/NOAA/NMFS/AKRO > Alaska Regional Office, National Marine Fisheries Service, NOAA, U.S. Department of Commerce dataCentre Global Change Master Directory (GCMD) Data Center Keywords 2017-04-24 publication 8.5 Earth Science Data and Information System, Earth Science Projects Division, Goddard Space Flight Center (GSFC), National Aeronautics and Space Administration (NASA) https://forum.earthdata.nasa.gov/app.php/tag/GCMD%2BKeywords GCMD Keyword Forum Page Global Change Master Directory (GCMD). 2025. GCMD Keywords, Version 22. Greenbelt, MD: Earth Science Data and Information System, Earth Science Projects Division, Goddard Space Flight Center (GSFC), National Aeronautics and Space Administration (NASA). URL (GCMD Keyword Forum Page): https://forum.earthdata.nasa.gov/app.php/tag/GCMD+Keywords information custodian AKRO Sustainable Fisheries (SF) Division Metadata Portfolio project InPort otherRestrictions Cite As: Alaska Regional Office, [Date of Access]: Catch-In-Areas Main [Data Date Range], https://www.fisheries.noaa.gov/inport/item/27363. 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. otherRestrictions Access Constraints: None otherRestrictions Use Constraints: None otherRestrictions Distribution Liability: Confidential Fisheries Data restricted Confidential NOAA Data Management Plan (DMP) NOAA/NMFS/EDM 27363 https://www.fisheries.noaa.gov/inportserve/waf/noaa/nmfs/akro/dmp/pdf/27363.pdf WWW:LINK-1.0-http--link NOAA Data Management Plan (DMP) NOAA Data Management Plan for this record on InPort. information crossReference eng; US elevation environment inlandWaters oceans Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.3.1.4959 -180 -129 47 69 Dataset | Currentness: none 2003 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. A series of Speed algorithms clean the data of Observer or VMS outlier records. Speed is computed after each cleaning subset using several algorithms, simplified below. When the speed is greater than 8.5knots, the VMS or Observer records are removed as long as there are greater than 2 records When there is more than one VMS transponder associated with an observed haul, we only keep the VMS transponder that is closest to the observed retrieve location. Most VMS data is removed from Hook-and-Line and Pot Observed records since the gear is dropped and retrieved while the vessels loiters or deploys other sets of gear. When only a single observed record is available by haul, we add .002 to the Latitude and Longitude of the observed retrieve location in order to have enough points to build a line. When a VMS or Observed point is greater than 120km from the observed deploy or retrieve point, the record is deleted. The observed-VMS lines are built in ArcMap, grouped by the Catch Accounting Reference Key and sorted by the date-time from the Observed and VMS records. These lines can be simple, straight or very complex that run back and forth several times between the relevant VMS and observer points. All segments of the lines are used in the proportional calculations that follow. 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. For catcher processors the catch is assigned by individual haul from the Catch Accounting System to each based on the length of the line. For catcher vessels, the catch is split by individual haul into grid-IDs but then aggregated to the catcher vessels reported trip. A related algorithm applies the catch of the Observed haul to the trip. This is due to Catch Accounting assigning catch by a catcher vessel's trip rather than by individual haul. 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. The criteria the Catch-In-Areas database uses to find a vessel that is fishing instead of cruising or being idle include 1) A vessel must be operating between .9 knots and 4.1 knots; 2) a vessel must not be in an area known not to be a fishing area, e.g., very near ports; 3) a vessel must be operating inside at least one of the state statistical areas reported on its fish ticket; and 4) the date-time of the VMS point must be within the date range on the fish ticket. We use the vessels reported latitude and longitude to determine vessel speed. This calculation is based off the standard formula: Radius_of_the_Earth*((2*ASIN(SQRT((SIN((RADIANS(LAT1)-RADIANS(LAT2))/2)2)+COS(RADIANS(LAT1))*COS(RADIANS(LAT2))*(SIN((RADIANS(LONG1)-RADIANS(LONG2))/2)2))))) Geoid 6371.1 A catch record in this process is weight ESRI REST Service Lewis, Steve 907-586-7858 907-586-7255 P.O. Box 21668 Juneau AK 99801 USA steve.lewis@noaa.gov email distributor 22.1 https://alaskafisheries.noaa.gov/maps/ WWW:LINK-1.0-http--link RES_Services_CIA Splash page to mapping applications download dataset Representativeness Catch-In-Areas database matching algorithms match 99.976% of the Catch Accounting to spatial data. Accuracy Data has embedded 'metadata' called the Match-Source column, that identifies each row in the database to a specific matching method. Checksum and Go-NoGo tables are created in order for analytical products to be built. Analytical Accuracy Data has embedded 'metadata' called the Match-Source column, that identifies each row in the database to a specific matching method. Checksum and Go-NoGo tables are created in order for analytical products to be built. Quantitation Limits Approximately 96% of the catch is matched directly and 4% of the catch is matched using very specific extrapolations. Bias VMS units depend on satellites and while the vessel's transponders should buffer the signal until it has captured a satellite, it does not always work that way. Therefore we only match only 96% of the catch. There other other issues with data including date mis-compares. Comparability VMS-Obs-UnObs database; another part of the Catch-In-Areas. Completeness Measure Tuning of database and adjusting for new types of data. Precision 7.8 kilometers. Analytical Precision 7.8 kilometers. Field Precision variable Sensitivity VMS Completeness Report See Checksums Conceptual Consistency See Checksums 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] otherRestrictions otherRestrictions Access Constraints: . | Use Constraints: .