Skip to content
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

FTlandingDate needed #200

Open
nmprista opened this issue Feb 27, 2024 · 1 comment
Open

FTlandingDate needed #200

nmprista opened this issue Feb 27, 2024 · 1 comment
Assignees
Labels
CS issue New feature request New feature request On ICES to-do-list ICES will work on this as soon as possible

Comments

@nmprista
Copy link
Collaborator

Estimates are frequently calculated based on landing date (e.g., by landing quarter, landing month).

In e.g., H1, H2 or H3 there is no possibility of declaring that date, only arrival date (which may fall on a different quarter).

We need an FTlandingDate (e.g., defined as the date of most landings) to account for such cases

@HenrikK-N HenrikK-N self-assigned this Mar 6, 2024
@HenrikK-N HenrikK-N added New feature request New feature request On ICES to-do-list ICES will work on this as soon as possible labels Mar 6, 2024
@HenrikK-N
Copy link
Collaborator

'Dominant landing date' should be in the Trip table, (dominant; because there could be more landing dates). The field should be added as an Optional field, after the arrival time (field 16). Having the landing data on the Sample table as 'Landing date' could be an option, but the CL data differs up to 4 days, and it is not always possible to distinguish landing data from the different fishing operations. Therefore it is not good to have the landing data on the Sample table. This should be implemented in the next possible update version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CS issue New feature request New feature request On ICES to-do-list ICES will work on this as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants