Inclusion of Base port in the CL and CE tables

[luciazarauz]

Dear coregroup,

We have found that we would need the inclusion of the variable Base Port, to reproduce the estimations we are doing.

The reason behind is that in Spain, AZTI is doing the following sampling:

• port sampling: we sample the landings sold in Basque Ports. And the proxi we use for this is to use the landings landed in Basque Ports plus the landings landed by Basque Vessels abroad (which are usually sold in the Basque Cuntry).

• onbopard sampling: we sample just Basque vessels (they are the ones we have access to)

We discussed this in yesterday's meeting. I am sorry we didn't raised it before. We just didn't realize...

If you need any further infromation, please, do not hesitate in asking

Best regards

Lucía

[HenrikK-N]

Hi Lucia Can you let us know what you suggest the field could be called, and what the description for the field could be? Br Henrik

[luciazarauz]

Dear Henrik,

After some discussions about this issue, we think that there may be better options to distinguish which samples are accessible to the IEO and which ones to AZTI, without adding complexity to the RDBES:

1. use the variable metier level6 to distinguish the two different fleets (it will work for most of the fleets, but not all).
2. use the variable nationalFishingActivity. It as the advantage that it is not so standardized than the RCG metier level 6 and could work for all fleets
3. use the variable CLsamplingScheme. It could serve as a link to length sampling schemes and it is similar to the solution we have in our own data base, where we indicate which trips are sampled by who

Thank you

[HenrikK-N]

Dear Lucia

Thanks for the information and good alternatives to have the information in existing fields; metier6, nationalFishingActivity or samplingScheme.

Br Henrik