You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ashley Park (DFO) pointed out that length_type is not populated for certain projects and years. Her inquiry focussed on sablefish, but need to check length_method for all species in all projects, and create crosswalk table including species, project, year to populate length methods.
The text was updated successfully, but these errors were encountered:
I have see databases where, in an attempt at standardization, they have a fork length column and another column that informs when the FL has been calculated from TL. That doesn't cover the Dogfish's natural length. More generally, a length column name could make reference to standardization within species (e.g. 'Length_Standardized_within _Species') . Then 2 more columns would be needed, one to tell the standardization (e.g. FL, Natural_Length) and the second how the standardized value was obtained (e.g. 'Field_Measurement', 'Converted_from_TL_Field_Measurement_using_Ref_XXX'). Perhaps a bridge too far, but something to consider.
The URL links for the old AFSC codebooks keep breaking, so I have copied you my collection and other reports here:
\nwcfile.nmfs.local\FRAM\Users\Curt.Whitmire\RACE Surveys Info
It would be good for the Data Warehouse to have a reference area for this metadata.
Ashley Park (DFO) pointed out that length_type is not populated for certain projects and years. Her inquiry focussed on sablefish, but need to check length_method for all species in all projects, and create crosswalk table including species, project, year to populate length methods.
The text was updated successfully, but these errors were encountered: