Data was using PacFIN data to explore the sampling distribution of lingcod ages relative to the lengths. The data he was using was not pulled using the PacFIN bds pull function from the main branch of this package; however, WDFW pointed out something that I want to make sure we double check. Apparently identifying all Washington special samples requires checking more than one column in PacFIN. Lisa Hillier (WDFW) writes:
"Based on the spreadsheet from Jim this morning, it looks like the WA data from 2016-2019 includes special project samples that should not be included as comm. fishery samples. Special projects are coded as Market samples for WA (this may be the issue if the data is filtered based on this category) but should be filtered based on special_project_name too."
I am opening an issue here as a reminder to double check our pulling and cleaning processes to ensure that all WDFW special samples are being removed from the bds data.
Data was using PacFIN data to explore the sampling distribution of lingcod ages relative to the lengths. The data he was using was not pulled using the PacFIN bds pull function from the main branch of this package; however, WDFW pointed out something that I want to make sure we double check. Apparently identifying all Washington special samples requires checking more than one column in PacFIN. Lisa Hillier (WDFW) writes:
"Based on the spreadsheet from Jim this morning, it looks like the WA data from 2016-2019 includes special project samples that should not be included as comm. fishery samples. Special projects are coded as Market samples for WA (this may be the issue if the data is filtered based on this category) but should be filtered based on special_project_name too."
I am opening an issue here as a reminder to double check our pulling and cleaning processes to ensure that all WDFW special samples are being removed from the bds data.