-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
possible new haul-level fields #76
Comments
Door spread would be great. I can get you the column names and tables if that's helpful. Thanks! |
Yes column names and tables would be great, we can put them all in here and add as necessary |
I think the door/wing spread are embedded in an "operation_code" with values 1 - 4, where each operation_code value has a range of values relating to wing/door spread. Let me know if you are aware of something different. |
I believe the values you're referring to are whether the tow meets thresholds to classify it as a "good tow". What I needed to include in my last data request were salinity, depth, tow duration, distance traveled and values from net mensuration gear (only available since 2009) from svdbs.TOW_EVALUATION. Example code: from svdbs.UNION_FSCS_SVLEN b, svdbs.UNION_FSCS_SVCAT p, svdbs.UNION_FSCS_SVSTA s, svdbs.mstr_cruise c, svdbs.TOW_EVALUATION e And pre-2010: from svdbs.UNION_FSCS_SVLEN b, svdbs.UNION_FSCS_SVCAT p, svdbs.UNION_FSCS_SVSTA s, svdbs.mstr_cruise c |
Could be useful to add tow-level fields optionally:
month of tow
day of tow
tow distance
wing spread
@Laurels1 please add others
The text was updated successfully, but these errors were encountered: