afsc-gap-products / data-requests

An empty repo for tracking requests for GAP data

AFSC RACE Groundfish and Shellfish Assessment Program Data Request Tracking System

data-requests: This is a repository dedicated to use only for communication about data requests via GitHub issues.

The code in this repository is regularly being updated and improved. Please refer to releases for finalized products and project milestones.

This code is primarily maintained by:

The Groundfish Assessment Program ([email protected]; @afsc-gap-products)

Nancy Roberson (Nancy.Roberson AT noaa.gov; @NancyRoberson)

Alaska Fisheries Science Center (AFSC) National Oceanic and Atmospheric Administration (NOAA)
Resource Assessment and Conservation Engineering Division (RACE)
Groundfish Assessment Program (GAP)

7600 Sand Point Way N.E., bldg. 4
Seattle, WA 98115 USA

User Resources

• Data Access Documentation for All Production Data
• Fisheries One Stop Shop (FOSS)
• Groundfish Assessment Program Bottom Trawl Surveys
• AFSC’s Resource Assessment and Conservation Engineering Division
• Survey code books
• Publications and Data Reports
• Research Surveys conducted at AFSC

Making a request

If you are interested in a subset of the raw data, or a data product, first peruse our public data portal to see if the haul and catch data there are sufficient.

If that does not fulfill your needs, submit your request as an issue to this repository. Note that requests for querying historical raw data will be filled more quickly and with more regular periodicity than requests for derived data products that require new analysis (and depending on the time needed for this development, the latter may require discussions of the nature of the collaboration as noted in the section below "Credit for data and analysis").

If possible, include the following information:

1. Data product requested (stratum CPUE, etc.)
2. Species
3. Region (GOA, AI, Bering Sea)
4. Time frame
5. Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email addresses if requestor does not have a GitHub account)

To better understand what data are available and how to interpret the data you receive, please see the full documentation and metadata, and review our survey codebooks.

Fulfilling a request

If you are a GAP scientist providing data to a requester, when you are done,

1. Comment on the issue for that request with code or a link to the code you used to generate that data product. If it is something very standard like a CPUE table, there's no need to post the code, just note which script or static table you used.

2. Deposit the data in our Google Drive folder and prefix it with the issue number (e.g., 5_salmon_shark/). If you don't have access to this folder, contact Lewis, Duane, or Ned. Once the data request has been fulfilled, make a note on the issue and close it.

Credit for data and analysis

Adapted from Stan's note to the groundfish team:

The AFSC Groundfish Assessment Program (GAP) staff produces important data for research and management of fishery resources and, as a result of these vast collections, we are often the recipients of data requests. Some of these data requests are routine and minor and don't take much time or effort. Other data requests can be large, require custom processing, and can take a great deal of time, effort, and skill. In all instances when GAP-produced data is used, GAP and/or GAP employees should be acknowledged for the time and effort to produce the data.

These acknowledgments can take the form of a “thank you” note in informal documents or websites, to co-authorship or formal acknowledgments in scientific papers. In every instance, the Groundfish Assessment Program and the scientist(s) responding to the data request need to be recognized for their efforts. The form of acknowledgment should depend on the product GAP data was used for and on the GAP employee contribution (e.g. data only, data & data-products (graphs, tables, figures), data & interpretation or data and writing).

GAP employees are encouraged, when providing data products to others, to ask for appropriate acknowledgment at the time of acceptance of the data request. For example, you can include a note in the email stating: “I would appreciate acknowledgment of the hard work by the personnel of AFSC Groundfish Assessment Program needed to collect the data.”

The acknowledgment in the form of co-authorship requires a significant contribution to the paper. If you think coauthorship is appropriate to the request, make this request in your initial response to the data request. Support your request with information about your specific contribution. Stan cites Yale University's “Guidance on Authorship in Scholarly or Scientific Publications”:

Each author should have participated sufficiently in the work to take public responsibility for its content. All co-authors should have been directly involved in all three of the following:

1. Planning and contribution to some component (conception, design, conduct, analysis, or interpretation) of the work that led to the paper or interpreting at least a portion of the results;

2. Writing a draft of the article or revising it for intellectual content; and

3. Final approval of the version to be published. All authors should review and approve the manuscript before it is submitted for publication, at least as it pertains to their roles in the project.

In general, if a data request requires a GAP scientist to write code for an analysis to derive a product (e.g., life-staged biomass estimates or CPUE summarized for a specific region or time frame) then it is appropriate to request coauthorship, with the above qualifications in mind. Each co-author is responsible for considering his or her role in the project and whether that role merits attribution of authorship. Co-authors should review and approve the manuscript, at least as it pertains to their roles in the project.

Discuss data requests with your supervisor and/or Program Manager and reach a decision on the effort required to complete data requests. If you feel that it should earn you co-authorship, this should be negotiated with the data requester before you fulfill the data request and be part of your Performance Plan.

Access Constraints

User Constraints: Users must read and fully comprehend the metadata prior to use. Data should not be used beyond the limits of the source scale. Acknowledgment of AFSC Groundfish Assessment Program, as the source from which these data were obtained, in any publications and/or other representations of these data, is suggested.

General questions and more specific data requests can be sent to [email protected] or submitted as an issue on our GitHub Organization. The version of this data used for stock assessments can be found through the Alaska Fisheries Information Network (AKFIN). For questions about the eastern Bering Sea surveys, contact Duane Stevenson ([email protected]). For questions about the Gulf of Alaska or Aleutian Islands surveys, contact Ned Laman ([email protected]). For questions specifically about crab data in any region, contact Mike Litzow ([email protected]), the Shellfish Assessment Program lead.

For questions, comments, and concerns specifically about the Fisheries One Stop Shop (FOSS) platform, please contact us using the Comments page on the FOSS webpage.

U.S. Department of Commerce | National Oceanographic and Atmospheric Administration | NOAA Fisheries

data-requests's Issues

North Bering/Chukchi Seas RACE surveys not in FOSS

hello - looking for zero filled CPUE data for the north Bering Sea (NBS) and Chukchi surveys. Most are on FOSS (NBS); however, north Bering sea 2018 and the 2012 Chukchi surveys are not so thought I would request a package deal :).

Data Requested: NBS 2010, 2017-2022 and Chukchi 2012

Importantly, can you send metadata with NBS 2018, Chukchi 2012 surveys as to how they differ from standardized surveys (issues, gear, etc.).

Fields needed:
Haul
Species code (>=40000 - inverts only)
Species name (full taxonomic hierarchy: Phylum, Order, Family, etc. )
Common name
Start time (date, time)
Latitude (DD) (start)
Longitude (DD) (start)
Station ID
Bottom depth
Gear temp
Surface temp
CPUE_Kg_HA
CPUE_No_HA
Area swept

THANK YOU!!!!!!

EBS slope survey stratum shapefiles

Data product requested (stratum CPUE, etc.): EBS Slope survey shapefiles for use in 2022 stock assessment

Species: N/A

Region (GOA, AI, Bering Sea): Bering Sea

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.): Jane Sullivan(@JaneSullivan-NOAA) and Matt Callahan (@MattCallahan-NOAA)

PYCNOPODIA REQUEST

** Data Requested: YEAR, CRUISEJOIN, HAULJOIN ,CATCHJOIN, REGION, VESSEL,CRUISE,STRATUM,STATIONID,HAUL,HAUL_TYPE
,PERFORMANCE,START_TIME,START_LATITUDE,START_LONGITUDE,BOTTOM_DEPTH,SURFACE_TEMPERATURE,GEAR_TEMPERATURE,EFFORT,SPECIES_CODE,WEIGHT,wCPUE,NUMBER_FISH,nCPUE,SUBSAMPLE_CODE VOUCHER

Pycnopodia helianthoides species_code = 80160:

Region (GOA, AI, Bering Sea):

**2022 Request: Duane Stevenson "Could you provide a new data set with the same parameters of the one given to Gravem et al., but with the most recent surveys included?"

History: 2020 Original request was fufilled by Jason Conner and submitted to Sara by Nancy: " Hello, my name is Sara Hamilton. I’m writing on behalf of myself and my colleague Dr. Sarah Gravem, who have been contracted by The Nature Conservancy to conduct an IUCN Red List Assessment for Pycnopodia helianthoides.
We need to estimate Pycnopodia population densities across their entire range, both before the catastrophic outbreak in 2014/2015 and post outbreak. Since Pycnopodia go down to depths of around 600m, we are gathering trawl data to assess the population density at non-diveable depths. I found the Alaska Groundfish Bottom Trawl data (which includes sightings of Pycnos) on the AFSC website (https://www.fisheries.noaa.gov/alaska/commercial-fishing/alaska-groundfish-bottom-trawl-survey-data).

This data will be quite useful to us, particularly since it has a Weight CPUE metric. This data provides us with evidence of presence of Pycnopodia, but doesn’t tell us much about absence (aka, the stations that were trawled and no Pycnos were found). Is there any way you could help me find a trawl dataset that lists all the bottom trawls and an estimated area swept for each? If not, is there anyone you can suggest that might be able to help me? Any suggestions are greatly appreciated! Sara Hamilton (she/her) NSF-GRFP PhD Candidate Oregon State University 540-292-4313 https://hamiltsa9.wixsite.com/kelp"

Pycnopodia.csv
**HISTORY: provide a new data set with the same parameters of the one given to Gravem et al., but with the most recent surveys included

Temperature profile data request

Data product requested (stratum CPUE, etc.):
Temperature depth profiles at 1-m increments for all available years, such as the data in these profiles https://drive.google.com/file/d/1_BTjGDKm6iUoOoDkkz7nkwaT0gVGuLgj/view?usp=sharing
Can filter if easier: Date, latitude, longitude, temperature, depth of temperature, bottom depth

Species:
NA

Region (GOA, AI, Bering Sea):
GOA, AI, and Bering Sea

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Kevin Siwicke (@KSiwicke, [email protected]), ABL - MESA

JOIN_FOSS_CPUE_CATCH missing rows and a column

Thanks for separating out the haul and catch data for users to merge externally. 2 quick things:

1. When I try to query the JOIN_FOSS_CPUE_CATCH table from Oracle, I'm only getting 49567 records, so many are missing. No errors about connection timeouts or anything like that.

2. I know we will be revising the itis codes, but including them in the catch table would be helpful in the meantime

[Data product request]

Data product requested (stratum CPUE, etc.):

Species:

Region (GOA, AI, Bering Sea):

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

[Haul Data for 2022 EBS/NBS/AI; Catch Data for hauls where Pacific herring were caught ]

Data product requested (stratum CPUE, etc.): All Haul Data; Catch data for hauls with Pacific herring

Pacific herring:

Region (GOA, AI, Bering Sea ): AI, EBS shelf, NBS

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.): [email protected] [email protected] [email protected]

My name is Sydney Almgren, and I am a graduate student at the University of Alaska Fairbanks. I am working on a research project with Drs. Jessica Glass and Andrés López on Pacific herring genetics in the eastern Bering Sea. We have received herring samples for this project from the Aleutian Islands Bottom Trawl Survey, and I am looking for more data from the survey.

I see that there is some great background information about the survey goals on the NOAA website! I was wondering if there is any additional data from the survey that would give us more information on where our specific samples came from, such as ship/haul numbers, collection date, location, etc.

Is there data like this from the survey that you would be able to share with us? Our herring samples each have their own labels, but is there a larger database that these labels match up to?

EBS Pollock

Data product requested (stratum CPUE, etc.):
Model settings and data inputs for the density estimates used in the assessment

Species:
Walleye Pollock

Region (GOA, AI, Bering Sea):
Bering Sea

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Qi Lee at SAFS, working with @James-Thorson-NOAA and Alan Haynie ([email protected]) at AFSC.

Otolith Specimen Collection Report

Data product requested (stratum CPUE, etc.):
Having negotiated otolith requests with stock authors in the planning stages, we close the circle by reporting back to Sandra Lowe and Chris Lunsford on whether we met the targets for their collections (e.g., the negotiated requests was for 1000 otolith pairs and we collected 900). We have also typically determined how many otoliths we "left on the table" by counting up instances of oto specimens foregone when they would've otherwise qualified for collection based on catch numbers and collection rubrics (e.g., "all up to 5, 5 for > 5" and did we do this every time a species qualified on a haul?).

Species:
All otolith species with random collection rubrics

Region (GOA, AI, Bering Sea):
GOA and AI depending on the year

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

This report originates with the Gulf-Aleutian group and typically whoever was responsible that year for otolith request negotiations. Pass the results to the Program Leads (Ned L., Sandra L., and Chris L.)

Sleeper Shark Weight/ Measurements and Capture Info [Data product request]

Data product requested (stratum CPUE, etc.):
Physical data taken of caught sleeper sharks, as well as the associated catch data (location, time, etc)

Species:
Pacific sleeper shark

Region (GOA, AI, Bering Sea):
All

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Keith Fuller, NOAA affiliate and APU Postdoc, working with Cindy Tribuzio (of MESA), Craig Rose, and Brad Harris (of APU)

Trying to match AI size and age pop'n estimates prior to 2004

Data product requested (stratum CPUE, etc.):
Filtered length frequency, CPUE, and specimen data for AI bottom trawl surveys from 2004 and prior

Species:
All

Region (GOA, AI, Bering Sea):
AI

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Pete Hulson (@PeteHulson-NOAA, [email protected]) as part of a working group investigating the magnitude of sexed length samples. Others in the working group include Ben Williams (@ben-williams, [email protected]), Jason Conner ([email protected]), and Meaghan Bryant ([email protected])

Pcod, ATF and Kamchatka cpue for FEAST

Data product requested (stratum CPUE, etc.):
NumCPUE and WeightCPUE by year (all years), station and 1 cm length bins

Species:
Pacific Cod, Arrowtooth Flounder and Kamchatka flounder

Region (GOA, AI, Bering Sea):
EBS + NEBS

Research team making the request (PI /requester name if you are not the PI, and tag team members with github accounts):
Resource Ecology and Ecosystem Modeling (REFM), FEAST, Ivonne Ortiz and Kerim Aydin (PI). This is the same request as in past years. Thank you :)

2019 age comps for GOA FHS

Data product requested (stratum CPUE, etc.): Age comps

Species: Flathead sole

Region (GOA, AI, Bering Sea): GOA

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
@mkapur (will add NOAA gh later)

1983-2021 Surface and Gear Temperature Data

Data product requested (stratum CPUE, etc.): Surface and Gear Temperatures 1983-2021

Species: N/A

Region Chukchi Sea; EBS slope, EBS shelf; Northern Bering Sea

Research team making the request [email protected]

RESULTS and COMMENTS
KEARNEY_GROUNDFISH SURVEY TEMPERATURE DATA_1983-2021.xlsx

I used Oracle SQL below to query the temperature data.
1983 was the start point because we didn't employ standard methods for temperature measurements prior.
6 =Chukchi Sea Trawl Survey; 78=Eastern Bering Sea Slope Bottom Trawl Survey
98=Eastern Bering Sea Crab/Groundfish Bottom Trawl Survey; 143=Northern Bering Sea Crab/Groundfish Survey - Eastern Bering Sea Shelf Survey Extension
Abundance Haul YES means that it was a satisfactory haul and the data are can be used in abundance estimates. NO means that the haul was not satisfactory and the data shouldn't be used in abundance estimates. Both types are in the results.
18,422 records were returned.

SELECT
region,
cruise,
vessel,
haul,
to_char(start_time, 'YYYY-MM-DD HH24:MI:SS') start_time,
surface_temperature surface_temperature_celsius,
gear_temperature gear_temperature_celsius,
abundance_haul
FROM
racebase.haul
WHERE
cruisejoin IN (
SELECT
racebase_cruisejoin
FROM
race_data.cruises
WHERE
survey_id IN (
SELECT
survey_id
FROM
race_data.surveys
WHERE
survey_definition_id IN
( 98, 78, 143, 6 )
AND year > 1982))

Positional data

GPS position data is missing in the ES60 .raw files for 11 cruises. Requesting positional data so we can submit to NCEI bathymetry database.

Data product requested (stratum CPUE, etc.):

Date, Time, Latitude, Longitude

For each of the following cruises:
(Vessel name, GAP vessel code, region, year)
Morning Star, 57, GOA, 2001
Vesteraalen, 94, GOA, 2001
Vesteraalen, 94, GOA, 2007
Alaska Provider, 176, GOA, 2013
Alaska Provider, 176, GOA, 2015
Sea Storm, 143, AI, 2002
Gladiator, 147, AI, 2004
Alaska Provider, 176, AI, 2014
Morning Star, 57, EBS, 2002
Aldebaran, 89, EBS, 2003
Alaska Knight, 162, EBS, 2015

Species:
N/A

Region (GOA, AI, Bering Sea):
GOA, AI, Bering Sea

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Drew Stephens [email protected] and Bob McConnaughey [email protected]

Cod Abundance in the EBS

cod abundance data by year class, for all stations during the EBS summer surverys from 2014-2021.

Data product requested (stratum CPUE, etc.): numerical CPUE by age

Species: pcod

Region (GOA, AI, Bering Sea): EBS

Research team making the request: @Erin-Fedewa-NOAA, Maddie Shipley (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

[Data product request]

Data product requested (stratum CPUE, etc.):

Hi! I'm working with Kirstin Holsman, Andre Punt, John Reum, Cheryl Barnes and others on the ACLIM2 project, aiming to forecast changes in predator-prey overlap by building SDMs with ROMS-NPZ outputs. I need size structured data for several species, because we want to fit models to at least two size classes for each species. I know this is something of a large request, but the data I need are: biomass & biomass catch rate for Eastern Bering Sea trawl surveys (including NBS strata), from 1982 - 2021, in 1 or 5cm size bins at the coarsest, for the following seven species. If possible, it would be really helpful if there were explicit zeroes in these data - i.e., for every size bin, if that size bin was not observed in a surveyed station in that year, I would like biomass and biomass catch rate to be 0, including for survey stations where no individuals of any size bin were recorded.

Species:

(1) arrowtooth flounder, (2) Pacific halibut, (3) Pacific cod, (4) walleye pollock, (5) northern rock sole, (6) yellowfin sole, (6) chinook salmon, and (7) capelin.

Region (GOA, AI, Bering Sea):

Bering Sea (including NBS surveys when available).

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

ACLIM2 team (PI: Kirstin Holsman @kholsman)

Thank you!

Link to FOSS public data portal in readme

When the link is finalized, note this prominently in readme as the first place to look before making a data request.

[Data product request]

Data product requested (stratum CPUE, etc.):

Species:

Region (GOA, AI, Bering Sea):

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

NBS_Numerical CPUE by station all species

Data product requested: Numerical CPUE by station (full timeseries)

Species: all

**Region: **NBS

Research team making the request: Shellfish Assessment Program @Erin-Fedewa-NOAA @mikelitzow
datasets for a manuscript as well as the snow crab Ecosystem and Socioeconomic Profile

EBS-NBS-Pacific cod numerical CPUE by length class for all stns and years

Data product requested: numerical CPUE by pcod length class for all stations/all years in EBS and NBS (full timeseries for both regions)

Species: Pacific cod species code =21720

Region: EBS and NBS

Research team making the request: Shellfish Assessment Program @Erin-Fedewa-NOAA @mikelitzow
datasets for a manuscript as well as the snow crab Ecosystem and Socioeconomic Profile

[Data product request] Salmon Shark data

Data product requested (stratum CPUE, etc.):
tow data (length, weight, sex, haul location, gear type, date/time, gear depth)

Species:
Salmon Shark

Region (GOA, AI, Bering Sea):
all (GOA, AI, and Bering Sea)

timespan:
1982 - present

Research team making the request (PI /requester name if you are not the PI, and tag team members with github accounts):
Sabrina Garcia (ADF&G)

[HAUL DATA]

Data product requested: HAUL DATA from 2021 surveys. This is to support the voucher specimens that have been collected on the surveys and deposited here in the fish collection.

Region GOA, NBS, EBS

Research team making the request Division is nice too.): [email protected] University of Washington Fish Collection; School of Aquatic and Fishery Sciences and Burke Museum of Natural History and Culture
http://www.burkemuseum.org/research-and-collections/ichthyology

[Data product request]

Data product requested (stratum CPUE, etc.):

Species:

Region (GOA, AI, Bering Sea):

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

Add New Codes to race_data.BOTTOM_DEPTH_METHOD lookup table

To the race_data.BOTTOM_DEPTH_METHODS table:

Add:
Bottom Depth Methods 14 = CTD and net mensuration
Bottom Depth Methods 15 = CTD and estimated net height

Research team making the request (@Ned-Laman-NOAA @NancyRoberson ):

CPUE and numbers of walleye pollock + surface and bottom temp for Bering Sea

2021 CPUE biomass and numbers of walleye pollock, near surface temperature and bottom temperature, latitude and longitude for all stratum in the Bering Sea summer bottom trawl survey (stratum CPUE, etc.): The same data output made available to the public on NOAA's website.

Species: Walleye pollock

Region (GOA, AI, Bering Sea):Bering Sea

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):Jeremy Sterling Marine Mammal Laboratory

[Data product request] - MACE, EBS

Hello-
We'd like the Length at age data for summer EBS survey:
Unclear on what "stratum" means, but we'd like data from legs 1-3.
Time-frame- by 10/13 if at all possible.

Walleye Pollock:

** Bering Sea **:

MACE, Sarah Stienessen, [email protected]

Thanks!

Add New Code to race_data.GEAR_DEPTH_METHOD lookup table: Gear Depth Method 9 = Sea-Bird SBE 19 plus CTD

To the RACE_DATA.gear_depth_methods table:

Add Gear Depth Method 9 = Sea-Bird SBE 19 plus CTD

Update
Remove parentheses in (pendulum/tilt) Gear Depth Method 4 = Sea-Bird SBE-39 data logger pendulum/tilt -

Research team making the request (@Ned-Laman-NOAA @NancyRoberson ):

Add EDIT CHECKS: for hauls w/NULL net numbers, hauls with NULL door numbers, bottom depths<15m

ISSUE: ADD edit checks-

Level 99 for hauls w/NULL net numbers (need net number when doing spread estimation) NL

Level 50 for hauls w/NULL door numbers. NL

Level 50 for bottom depths < 15 m. Most of these should result in corrections, but rarely depths < 15 m have been sampled legitimately or at least exist uncorrected in RACEBase. NL

Level 50 or 99: If the Net Mensuration Method is 4 or 5, then the bottom depth method cannot be 5, 9, 11, 13, or 14

Research team making the request (@Ned-Laman-NOAA ):

FMP codes for forage and protected species: add to RACE_DATA.FMA_SPECIES_CODES?

Data product requested (stratum CPUE, etc.): add species to RACE_DATA.FMA_SPECIES_CODES?

Species: Multiple

Region (GOA, AI, Bering Sea): NA

MACE submits an annual report to the AK Regional Office accounting for our catch of 'Fishery Management Plan species'. We've long worked off a list at racebase_dev.fmp_species_list but Taina noticed this list was incomplete. We requested a current 2022 list from Cathy Tide, AK Regional Office [email protected].

Nancy Roberson suggested using the list at RACE_DATA.FMA_SPECIES_CODES; a comparison between the 2022 'FMP list' from Cathy Tide and the list maintained at RACE_DATA.FMA_SPECIES_CODES finds 59 species that are present on the 'FMP list' that aren't present on the RACE_DATA.FMA_SPECIES_CODES list. Those 59 are linked here in a google sheet to save space.

Would it be possible to add these species? I suppose, if so, we'd simply refer to the list at RACE_DATA.FMA_SPECIES_CODES for our annual reporting needs (and remember to update as needed).

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Mike Levine, MACE @mike-levine
Taina Honkalehto, MACE [email protected]

Duplicate records in RACEBASE.CATCH

There are 19 instances of duplicated records in RACEBASE.CATCH. Hopefully they can be resolved by double checking the catch forms in G:\CDMP_DATA HISTORIC SURVEY DATA SHEETS and updating the CATCH table.

SELECT vessel,cruise,haul,species_code,count(*)
FROM racebase.catch
GROUP BY vessel,cruise,haul,species_code having count(*) > 1
ORDER BY cruise,vessel,haul,species_code

Research team making the request @NancyRoberson
export.xlsx

RACEBase.CATCH correction: Big skate or skate egg cases?

Data product requested (stratum CPUE, etc.):

There is a mismatch between the catch records for big skate in RACEBASE.CATCH and the CPUE records in GOA.CPUE.

I am wondering whether there were some big skate eggs that were merged with or misID'd as the big skate species code in the RACEBASE.CATCH table that were then removed/modified from the GOA.CPUE tables.

Can you check the big skate records in the attached in the spreadsheet

Species: Big skate species_code 420

Region: GOA

Research team making the request @zoyafuso-NOAA

GOA management area biomass

Data product requested: Current VAST estimates produce biomass for the entire GOA. However, allocation is based upon spatial abundance (e.g., western, central, eastern - some species have additional spatial allocations). While a number of GOA species are using VAST to estimate survey abundance we then switch to the design-based abundance estimate to determine regional abundance (which is then run through a random effects model) to determine allocation.

It would be helpful if area abundance was also an output from the GAP group, additionally it would be helpful to examine what, if any differences, changing to VAST generated are abundance would have on allocation. This can be accomplished through collaboration with assessment authors. I'm happy to assist with this once assessment season has passed.

Species: Any using VAST estimates for the GOA

Region GOA

Research team making the request: @BenWilliams-NOAA, MESA

Population level age composition from slope survey

Hello,
I inherited population level age data for BSAI Kamchatka flounder and I would like to determine how they were derived.

Data product requested (stratum CPUE, etc.):
Population level age composition data from EBS slope bottom trawl survey
Species:
Kamchatka flounder
Region (GOA, AI, Bering Sea):
Bering Sea
Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
Meaghan Bryan, email: [email protected], @mdbryan

2022 EBS CPUE By Station For All Species

Data product requested (stratum CPUE, etc.):
EBS shelf CPUE by station

Including:

• Vessel/Cruise/Haul
• Latitude
• Longitude
• Station
• Stratum
• Year
• Datetime
• WTCPUE
• NUMCPUE
• Common_name
• Scientific_Name
• Species_code
• Bottom_Depth
• Bottom_Temperature
• Surface_temperature

Species:
All species caught

Region (GOA, AI, Bering Sea):
EBS shelf

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
[email protected] Kodiak Fisheries Research Center

Correction to RACEBase.HAUL 1980s hauls

@NancyRoberson
There are four locations in RACEBase.HAUL in the AI and GOA regions (and 69 loci in the BS region-check with @Duane-Stevenson-NOAA about how he wants to deal with those) where NET_WIDTH Is Null but ABUNDANCE_HAUL = 'Y'. This fails logic currently held in GIDES and conceptually in the steps to estimate biomass since without NET_WIDTH we cannot compute area swept to provide Effort for the Catch-per-Unit-Effort computation underlying our Biomass Estimates. My recommendation is that for these loci in the AI and GOA RACEBase.HAUL data the ABUNDANCE_HAUL field be changed to 'N'.

The SQL Plus showing that these hauls exist is here:

select region, cruise, performance, net_width, count(*) from racebase.haul
where region in ('BS','GOA','AI') and abundance_haul = 'Y'
and nvl(net_width,0) = 0
group by region, cruise, performance, net_width
order by region, cruise
/

The specific hauls where these conditions apply are listed by this code:

select hauljoin, region, vessel, cruise, haul, performance, net_width, abundance_haul
from racebase.haul
where region in ('BS','GOA','AI') and abundance_haul = 'Y'
and nvl(net_width,0) = 0
order by region, cruise, vessel, haul
/

1975-1981 CPUE data request

This data request was communicated with @RebeccaHaehn-NOAA via email and she will be fulfilling

**Data product requested (stratum CPUE, etc.): numcpue and wtcpue by station for all species caught on the EBS BT survey, 1975-1981 only

**Species: All species, by station

**Region: EBS

**Research team making the request: Erin Fedewa, SAP

Assistance designing a query that targets the EBS shelf records and excludes other BS surveys e.g. slope and NBS

Data product requested (stratum CPUE, etc.): Requester needs assistance designing a query that targets only the EBS shelf records and excludes other BS surveys e.g. EBS slope and NBS surveys

Species: None

Region (GOA, AI, Bering Sea): BS shelf only

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.): [email protected]

ATF, Kam, Shortracker Rockfish plots for SAFE reports

Due: Monday October 31, 2022

[Paraphrased from request in email 10/26 with Kalei and Meaghan] We discussed shooting for Friday, but totally ok if on Monday. Hope that timing is ok for you as well Meaghan but if not, then prioritize KAM first and then can do ATF as my reviewers already said Tuesday ok for them.

Data product requested (stratum CPUE, etc.):

[Paraphrased from request in email 10/26 with Kalei and Meaghan] I want to send a HUGE THANK YOU to Em for helping with all these graphics for arrowtooth (ATF), Kamchatka (KAM), and shortraker rockfish (SR). This is really helpful for us and very thankful for this. Also, I'm just a big fan of all the new awesome graphics from GAP and would love to give them more visibility where possible. Also I do want to reiterate, PLEASE say NO to any of this if the request is too much or you just don't have time for this. Totally OK. But if these are possible, here's what would be AMAZING to have (in order of priority, if that makes a difference):

1.) Eastern Bering Sea: ATF 1992-2022

• CPUE plots 3 row x 2 col plus NBS and BSS (one with coldpool outline in red or yellow, one without)
• M and F side by side length comps EBS only
• M and F side by side age comps EBS only
• M and F side by side length comps BSS only
• M and F side by side age comps BSS only

2.) Eastern Bering Sea: KAM 1991-2022 (although note from Lyle Britt that high confidence in speciation did not start until 1992 for ATF and KAM)

• CPUE plots 3 row x 2 col plus NBS and BSS (one with coldpool outline in red or yellow, one without)
• M and F side by side length comps EBS only
• M and F side by side age comps EBS only
• M and F side by side length comps BSS only
• M and F side by side age comps BSS only

3.) Aleutian Islands Survey: ATF 1991-2022

• Bubble plots 3 row x 1 col
• CPUE plots 3 row x 1 col
• M and F side by side length comps
• M and F side by side age comps

4.) Aleutian Islands Survey: KAM 1991-2022

• Bubble plots 3 row x 1 col
• CPUE plots 3 row x 1 col
• M and F side by side length comps
• M and F side by side age comps

5.) Aleutian Islands Survey: SR 1991-2022

• Bubble plots 3 row x 1 col
• CPUE plots 3 row x 1 col
• Totally forgot we already have the ridges plot for Shortraker lengths, so all good there!

6.) Eastern Bering Sea Slope (BSS): SR 2002-2016

• CPUE plots 3 row x 2 col, not sure how this will look, but might need an outline of EBS and NBS survey just for reference? This may be a really odd one to do, so no worries if it doesn't work.

Species:
ATF, Kam, Shortracker Rockfish

Region (GOA, AI, Bering Sea):
Eastern Bering Sea, northern Bering Sea, Bering Sea Slope, and AI

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
@kshotwell (kalei.shotwell AT noaa.gov)
@mdbryan (meaghan.bryan AT noaa.gov)

IPHC annual request: 2022 EBS/AI/NBS haul, catch, and length data for Pacific halibut

Data product requested (haul data, catch data, length data):

HAUL:

• CRUISEJOIN/HAULJOIN
• REGION
• VESSEL/CRUISE/ HAUL
• HAUL_TYPE
• PERFORMANCE
• START_TIME
• DURATION
• DISTANCE_FISHED
• NET_WIDTH
• NET_MEASURED
• NET_HEIGHT
• STRATUM
• START_LATITUDE/END_LATITUDE
• START_LONGITUDE/END_LONGITUDE
• STATIONID
• GEAR_DEPTH/BOTTOM_DEPTH
• BOTTOM_TYPE
• SURFACE_TEMPERATURE/GEAR_TEMPERATURE
• WIRE_LENGTH
• GEAR
• ACCESSORIES
• SUBSAMPLE
• AUDITJOIN

CATCH:

• CRUISEJOIN/ HAULJOIN/CATCHJOIN
• REGION
• VESSEL/CRUISE/HAUL
• SPECIES_CODE
• WEIGHT
• NUMBER_FISH
• SUBSAMPLE_CODE
• VOUCHER
• AUDITJOIN

LENGTHS:

• CRUISEJOIN/HAULJOIN/CATCHJOIN
• REGION
• VESSEL/CRUISE/HAUL
• SPECIES_CODE
• LENGTH
• FREQUENCY
• SEX
• SAMPLE_TYPE
• LENGTH_TYPE
• AUDITJOIN

Species requested (Pacific halibut):
Region (EBS Shelf):

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):
IPHC Lauri Sadorus

RACEBase.CATCH correction[Data product request]

We've identified an error in RACEBase.CATCH for a record in the GOA 2009 survey aboard Vesteraalen.
At HAULJOIN = -5945, the catch record for SPECIES_CODE = 420 w/weight 0.088 should be changed to SPECIES_CODE = 421 (otherwise that would be a really really small big skate!)

[Data product request]

Data product requested (stratum CPUE, etc.):

Species:

Region (GOA, AI, Bering Sea):

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

1982 - Present Specimen Data Request

**Data product requested (stratum CPUE, etc.): specimen data (sex, length, weight, age, + metadata (survey, cruise, region, stratum, haul, station ID, lat/long, bottom temp, surface temp, species code, species ID, tow_date))

**Species: All species

**Region: EBS, GOA, AI

**Research team making the request: Jennifer Bigman, EcoFOCI

• I am happy to include as many co-authors/collaborators as appropriate on this project.
• I wasn't exactly sure the time frame in which these data would be available. If possible, I would like data from all years that exist. Thank you!!

Specimen table access for food habits

Data product requested (stratum CPUE, etc.): Raw specimen data with NODC codes.

Species: pollock, cod

Region (GOA, AI, Bering Sea): All (?)

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account): Bridget Ferriss (@BridgetFerriss )

Note: NODC codes are available from FOODLAB.NODC in Oracle; the NODC lookup table with RACE species codes was added in this commit.

2019 EBS/NBS haul metadata for CTD samples

Data product requested (stratum CPUE, etc.):

EBS shelf and NBS haul metadata from 2019, including:

Haul:

• Vessel/Cruise/Haul
• Station ID
• Minimum bottom depth
• Maximum bottom depth
• Average bottom depth
• Surface temperature
• Gear temperature
• Wire out
• Performance

Event:

• Vessel/Cruise/Haul
• Doors down, doors up, on bottom, off bottom
• Latitude
• Longitude
• Date/Time

Species:

NA

Region (GOA, AI, Bering Sea):

Bering Sea

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

Ned Cokelet, PMEL

[Data product request]: data product acknowledgements

How do we want data we provide acknowledge in publications, presentations, or other completed products?

Pollock 1 cm estimates for FEAST

Data product requested (stratum CPUE, etc.):
Density dependent corrected NumCPUE by year, station and 1 cm length bins

Species:
Pollock

Region (GOA, AI, Bering Sea):
EBS + NEBS

Research team making the request (PI /requester name if you are not the PI, and tag team members with github accounts):
Resource Ecology and Ecosystem Modeling (REFM), FEAST, Kerim Aydin

[ANNUAL REQUEST: REFM: 2022 AI/GOA CPUE data ]

Data product requested (stratum CPUE, etc.):
The CPUE and the following fields from the 2022 AI survey
LATITUDE
LONGITUDE
STATION
STRATUM
YEAR
DATETIME
WTCPUE
NUMCPUE
COMMON
SCIENTIFIC
SID
BOT_DEPTH
BOT_TEMP
SURF_TEMP
VESSEL
CRUISE
HAUL

Species: All

Region (AI 2022):

Research team making the request ([email protected]/REFM):

These are the same data as those that used to be posted on the AFSC website. These data are used for indicators in the Ecosystem Status Reports.

When the data makes its way onto AKFIN and FOSS will it be in a similar format?

Last year's data request is attached below to serve as an guide for what is requested.
GOA 2021 Data update 092821.csv

2012 Arctic Eis 83-112 specimen data

Data product requested (stratum CPUE, etc.):

Species:

Region (GOA, AI, Bering Sea):

Research team making the request (PI /requester name, and tag team members with GitHub accounts, or email address if requestor does not have a GitHub account. Division is nice too.):

add metadata info

Should we add a version of the column explanations (units & code meanings) for racebase somewhere in the readme?