Main data elements
| Element | Requirement | Description | Input value |
|---|---|---|---|
| Month | M | Month of fishing activities | Integer 1..12 |
| Grid | M | Fishing area | Code from Grid codes |
| Species | M | Species caught and discarded | Code from Species |
This form provides for the reporting of estimates of geo-referenced species-specific catches and efforts by fishing fleet, fishery, and space and time strata.
Click here to download a blank version of Form 3-CE-update, or return to the list of all IOTC statistical data reporting forms. The form allows reporting updated data for a single fishery. Click here to download a blank version of Form 3-CE which has been designed to report data for multiple fisheries simultaneously.
Total number and/or live weight of retained catches by species and effort by stratum, along with information on the value (%) and type of sampling coverage used for the estimations by month, year, fleet, fishery, raising status, and fishing area.
| Element | Requirement | Description | Input value |
|---|---|---|---|
| Reporting year | M | Gregorian calendar year of the fishing activities | Integer |
| Reporting entity | M | Code of the entity reporting the dataset to the IOTC Secretariat | Code from Entities |
| Flag state | M | Code of the country registration of the fishery vessels | Code from Countries |
| Fisheries | M | Type of fishing practices based on several factors | Code from Fisheries |
| Element | Requirement | Description | Input value |
|---|---|---|---|
| Month | M | Month of fishing activities | Integer 1..12 |
| Grid | M | Fishing area | Code from Grid codes |
| Species | M | Species caught and discarded | Code from Species |
| Element | Requirement | Description | Input value |
|---|---|---|---|
| Original data type | M | Preliminary/final status of the data | Code from Types of data |
| Original data source | M | Source of information | Code from Catch and effort data sources |
| Original data processing | M | Processing applied to the data | Code from Catch and effort data processings |
| Data raising | M | Level of raising (i.e., extrapolation) | Code from Raisings |
| Source coverage type | M | Variable used for data coverage | Code from Types of coverage |
| Source coverage value | M | Value of coverage | in percentage |
| Catch unit | M | Units used to report the level of catches of a given species | Code from Catch units |
| Element | Requirement | Description | Input value |
|---|---|---|---|
| Primary | M | Primary effort unit | Code from Effort units |
| Secondary | O | Secondary effort unit (if any) | Code from Effort units |
| Tertiary | O | Tertiary effort unit (if any) | Code from Effort units |
| Element | Requirement | Description | Input value |
|---|---|---|---|
| Estimation | M | Indicates whether the data were estimated or actual recorded data | Code from Estimations |
| Element | Requirement | Description | Format | Example |
|---|---|---|---|---|
| Liaison officer full name | M | Name of the liaison officer in charge of the compilation of the data | Plain text | John Doe |
| Liaison officer email | M | Email address of the liaison officer in charge of the compilation of the data | Valid email address | John.Doe@fao.org |
| Organisation name | M | Name of the organisation in charge of the compilation of the data | Plain text | National Institute of Fisheries |
| Organisation email | O | Email address of the organisation in charge of the compilation of the data | nif@gov.sc | |
| Finalisation date | M | Date of finalisation of the dataset | ISO 8601 | 1996-03-27 |
| Submission date | M | Date of submission of the dataset | ISO 8601 | 1997-03-21 |
Effort units must be consistent with the recording requirements established in Res. 15/01 complemented by numbers of fishing operations for longline fisheries and surface fisheries (IOTC-2022-SC25-R). For coastal fisheries, it is recommended that effort data be submitted in the same units as those prescribed for longline fisheries and surface fisheries characterised by the same fishing gear.
| Gear group | Primary effort | Secondary effort |
|---|---|---|
| Gillnets (GI) | Number of fishing days | Number of fishing operations |
| Hooks and lines (HL) | Number of fishing days | Number of fishing operations |
| Longlines (LL) | Number of hooks deployed | Number of fishing operations |
| Other gears (OT) | Number of days at sea | Number of active gears/fishing operations |
| Pole-and-lines (PL) | Number of fishing days | Number of fishing operations |
| Purse seines (PS) | Number of fishing hours | Number of fishing operations |
From a general perspective, using trips as a unit of effort is not recommended because trip duration can vary widely due to factors such as vessel size, fishing success, and technical considerations (e.g., fuel availability).
Additional units may be considered to refine and standardise the estimation of nominal fishing effort:
In gillnet fisheries, the surface area of the nets deployed may better reflect effort intensity by accounting for differences in net length and height;
In hooks and line fisheries, the number of hooks may be used as required for longline fisheries;
In pole-and-line fisheries, the number of day-poles used may help account for differences in the number of fishers onboard the vessels;
In purse seine fisheries, the numbers of successful and null fishing operations, searching time, and surface area explored may complement the information provided by fishing time and the total number of fishing sets.
The spatial and temporal resolutions, catch units, and level of extrapolation vary according to the fishery category.
| Category | Temporal resolution | Spatial resolution | Catch unit | Extrapolation |
|---|---|---|---|---|
| Surface fisheries | Month | 1° grid area | Live weight equivalent | M |
| Longline fisheries | Month or finer for the SC | 5° grid area or finer for the SC | Numbers or live weight equivalent | M |
| Coastal fisheries | Year or finer | Irregular areas | Numbers or live weight equivalent | O |
## Warning in instance$preRenderHook(instance): It seems your data is too big for client-side DataTables. You may
## consider server-side processing: https://rstudio.github.io/DT/server.html