Description

This form provides for the reporting of operational and catch data from pole and line fisheries under the IOTC Regional Observer Scheme (ROS). The form is designed to capture verified information on fishing activity, catch composition, and bycatch associated with pole and line operations, including IOTC species, and other bycatch species.The reporting format follows the standards adopted by the IOTC Scientific Committee and includes multiple hierarchical data levels, ranging from trip and set information to species-specific catch and bycatch records. Data collected through this form contribute to scientific assessments of tuna and tuna-like species and support monitoring of the impact of pole and line fisheries on associated and dependent species. CPCs are required to complete the form for pole and line operations covered by the ROS, ensuring consistency, transparency, and quality of the data collected by scientific observers or with Electronic Monitoring Systems.

Click here to download a blank version of the ROS-PL form, or return to the list of all IOTC statistical data reporting forms.

Data content

Vessel and trip identifiers; effort and gear characteristics (poles, hooks, sighting cues); operational details of each event, catch and bycatch by species in number and weight; fate (retained/discarded). This form also includes details on bait fishing operations (gear, handling, weight).

Sheet Component Resolution Description
META Dataset Trip Information on data submission and main characteristics
O-INFO Observer & trip Trip Information on the observer and the fishing trip observed
V-INFO Vessel Trip Information on the fishing vessel, its gear, and personnel
V-TRIP Trip Trip Information on the fishing trip’s departure and return
V-ATTRIBUTES Vessel Vessel Information on the vessel’s attributes and equipment
G-GENERAL Equipments Trip Information on the fishing gear’s equipment and machinery
E-SET-TUNA Effort Set Information on effort (sets) and gear characteristics (materials, targeting)
E-SET-TUNA-FISHING-TRIP Effort Set Information on effort (sets) from the overall fishing trip
E-SET-TUNA-CATCH Effort Set Information on magnitude, composition, and fate of tuna catch
E-SET-TUNA-CATCH-SSI Catch Specimen Information on specimen condition, depredation, and technical details associated with the catch for Species of Special Interest during tuna fishing events
E-SET-CATCH-BIOMETRIC Catch Specimen Information on speciment details from a subsample of the catch
E-SET-BAIT Effort Set Information on effort (sets) and gear characteristics (materials, targeting) for bait fishing events
E-SET-BAIT-CATCH Catch Set Information on magnitude, composition, and fate of bait catch
E-SET-BAIT-CATCH-SPECIMEN-SSI Catch Specimen Information on specimen condition, depredation, and technical details associated with the catch for Species of Special Interest during bait fishing events
DAILY-ACTIVITY Trip Trip Information on the activities occurring throughout the fishing trip observed

META

Submission Information

Field Requirement Description Format Input value
Liaison officer full name M Name of the liaison officer in charge of the compilation of the data String e.g., John Doe
Liaison officer email M Email address of the liaison officer in charge of the compilation of the data Valid email address e.g., John.Doe@fao.org
Organisation name M Name of the organisation in charge of the compilation of the data String e.g., Institute of Fisheries
Organisation email O Email address of the organisation in charge of the compilation of the data Valid email address e.g., nif@gov.sc
Finalisation date M Date of finalisation of the dataset ISO 8601 e.g., 1996-03-27
Submission date M Date of submission of the dataset ISO 8601 e.g., 1997-03-21

General Information

Field Requirement Description Format Input value
Reporting year M Gregorian calendar year of the fishing activities reported through the dataset Integer e.g., 1996
Reporting entity M Three-letter (alpha-3) code of the entity reporting the dataset to the IOTC Secretariat Code from Entities e.g., ABW
Flag / Chartering state M The reporting flag or chartering state OR three-letter (alpha-3) code of the country registration of the fishing vessels Code from Countries e.g., FRA
Data source M The source of data provided Observer data or EM data e.g., OAS

O-INFO

Field Requirement Description Format Input value
observed_trip_id M Unique identifier of the fishing trip defined as the concatenation of (i) the observation or trip start date (YYYY-MM-DD), (ii) the IOTC observer number, (iii) the IOTC vessel identifier as per Record of Authorised Vessels (RAV) and the vessel gear group code as per IOTC classification Alphanumeric code e.g. 2024-01-23/IOTCFRA001/IOTC012345/PS

Observer Identification

Field Requirement Description Format Input value
IOTC_id M The unique registration identifier assigned to each observer by the IOTC Secretariat Alphanumeric e.g. IOTC_0976
full_name O The name of the scientific observer(s) that collected the data on-board the fishing vessel or EM reviewer Free entry. Plain text e.g., John Doe

Observer Trip Details

Embarkation: The starting port. If the first observation is available after the departure form the port while the vessel is within port limits, this is still recorded as the observation starting port. If the observation starts at sea outside port limits (onboard observer boarding the vessel via a vessel transfer or EM records not available at the trip starting date due to a recording failure), record “at sea”.
In port
Field Requirement Description Format Input value
country O The country or EEZ of the observation starting location. Code from Countries e.g., FRA
port O The port of the observation starting location Code from Ports e.g., REREU
At sea
Field Requirement Description Format Input value
latitude O The latitude of the observation starting location. Decimal degrees (two decimal places) e.g., -20.88
longitude O The longitude of the observation starting location. Decimal degrees (two decimal places) e.g., 55.53
Field Requirement Description Format Input value
date_time_utc O Record the date and time of the start of observations YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
Disembarkation: The ending port. If the last observation is available after a port launch while the vessel is within port limits, this is still recorded as the observation ending port. If the observation ends at sea outside port limits (onboard observer disembarking the vessel via a vessel transfer or EM records not available at the end of observations due to a recording failure) , record “at sea”
In port
Field Requirement Description Format Input value
country O The country or EEZ of the observation ending location. Code from Countries e.g., FRA
port O The port of the observation ending location Code from Ports e.g., REREU
At sea
Field Requirement Description Format Input value
latitude O The latitude of the observation ending location. Decimal degrees (two decimal places) e.g., -20.88
longitude O The longitude of the observation ending location. Decimal degrees (two decimal places) e.g., 55.53
Field Requirement Description Format Input value
date_time_utc O The date and time of the end of observations YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00

Observed Trip Summary

Number of fishing events: The total number of fishing events/sets conducted by the vessel from the observation starting date to the observation ending date, regardless their catch and data collection activities.
Field Requirement Description Format Input value
conducted M The total number of fishing sets conducted by the vessel from the observation starting date to the observation ending date, regardless their catch and data collection activities Integer e.g., tbd
observed M The total number of fishing sets/events monitored by the observer. In the case of Electronic Monitoring, only processed events to be included Integer e.g., tbd
Number of days: The number of hours/days the vessel spent on the following activities
Field Requirement Description Format Input value
searching M The number of hours/days searching during the observation period Integer e.g.,tbd
actively_fishing M The number of active fishing hours/days during the observation period Integer e.g.,tbd
in_fishing_area O The number of hours in the fishing area during the observation period Integer e.g.,tbd
transiting O The number of hours transiting during the observation period Integer e.g.,tbd
lost M The number of hours/days lost during the observation period Integer e.g., tbd
Reasons for lost days: Record the reason(s) a vessel was unable to fish: (i) adverse weather conditions, (ii) mechanical breakdown or inoperative gear or (iii) unforeseen events (specify).
Field Requirement Description Format Input value
reason O The main reasons for days at sea lost to fishing activity Code from Reasons for Days Lost e.g., AW

V-INFO

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric code e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL

Vessel Information

Identification:
Field Requirement Description Format Input value
name M The vessel full name as recorded on vessel official documentation or record the vessel full name as imprinted on the vessel itself or Electronic Monitoring records Strong e.g., PELICAN
flag_or_chartering_state M The country code of registration or chartering Code from Countries e.g., MDV
iotc_number M The unique identification number assigned to the vessel by the IOTC when it is included in the Record of Authorised Vessels Free entry, alphanumeric code e.g., IOTC016711
imo_number O The unique vessel identification number assigned by the International Maritime Organization Seven-digit number e.g., 8541701
ircs O The vessel International Radio Call Sign (IRCS) (when available) Alphanumeric code e.g., 8QE2264
Registration:
Field Requirement Description Format Input value
country O The code of vessel’s country of registry Code from Countries e.g., FRA
port O The code of vessel’s port of registry (also called home port) shown on its registration documents and lettered on the stern of the ship’s hull Code from Ports e.g., REREU
registration_number O The number issued by country in which the vessel is registered, shown on its registration documents and written on the hull of the vessel Alphanumeric or numeric according to CPC standards e.g., CBG303
Field Requirement Description Format Input value
licensed_target_species O The licensed target species as specified in vessel licences or permit conditions Code from Target Species e.g., AL
main_fishing_gear M The vessel main fishing gear Code from Fishing Gear e.g., DL
Vessel Personnel: Details of the individuals working onboard during the fishing trip as well as the total number of crew members onboard.
Field Requirement Description Format Input value
fishing_master_name M The full name of the fishing master recorded as first and last names String e.g., John Doe
fishing_master_nationality M The nationality of the fishing master Code from Countries e.g., FRA
skipper_captain_name M Name of the skipper or captain recorded as first and last names String e.g., John Doe
skipper_captain_nationality M Nationality of the skipper or captain Code from Countries e.g., FRA
crew_number O The number of crew onboard the vessel Integer e.g., 26

V-TRIP

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL

Trip Details

Vessel departure: Record the name and/or geographical coordinates of the port from where the vessel sailed – also include the country. If the vessel started a new trip at sea following transhipment record ‘at-sea’ plus the geographical coordinates corresponding to the location the trip started
In Port
Field Requirement Description Format Input value
country O The country or EEZ of the observation starting location Code from Countries e.g., FRA
port O The port of the observation starting location Code from Ports e.g., REREU
latitude O The latitude of the observation starting location Decimal degrees (two decimal places) e.g., -20.88
longitude O The longitude of the observation starting location Decimal degrees (two decimal places) e.g., 55.53
Field Requirement Description Format Input value
date_time_utc O The date and time the vessel departed from starting location YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
Vessel return: The name and/or geographical coordinates of the port where the vessel returned – also include the country. If the vessel arrived at a transshipment location record ‘at-sea’ plus the geographical coordinates corresponding to the location the transshipment started. If the observer disembarked before the vessel returned then record expected port of return as provided by the vessel
In port
Field Requirement Description Format Input value
country O The country or EEZ of the observation ending location Code from Countries e.g., FRA
port M The port of the observation ending location Code from Ports e.g., REREU
latitude M The latitude of the observation ending location Decimal degrees (two decimal places) e.g., -20.88
longitude M The longitude of the observation ending location Decimal degrees (two decimal places) e.g., 55.53
Field Requirement Description Format Input value
date_time_utc O The date and time the fishing vessel finishes its fishing campaign, i.e., returns to port or to a transshipment location for unloading. If is the expected date and time of arrival (ETA) if the observer disembarks before the vessel returns YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00

V-ATTRIBUTES

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL

Vessel Attributes

Field Requirement Description Format Input value
gross_tonnage O The vessel gross tonnage (no unit) as specified in vessel registration documents Float e.g., 33.09
loa_m O The vessel overall length (m) as specified in vessel registration documents Floats e.g., 27.38
hull_material O The vessel hull material Code from Hull Material Types e.g., AL
Main engines: The make (brand) and power of the main engines
Field Requirement Description Format Input value
make O String e.g., MAN Energy Solutions
power_value O Float e.g., 5000
power_unit O Power units code: kilowatts (kW), horsepower (hp), or break horsepower (bhp) e.g., kW
fish_storage_capacity_m3 O The vessel total maximum capacity (in cubic meters) to store catches Float e.g., 1100
Element Requirement Description Format Input value
preservation_method O The fish preservation methods used by the vessel to preserve the catch. Up to four preservation methods may be reported on the form Code from Fish Preservation Methods e.g., BR
Element Requirement Description Format Input value
storage_type O The type of structure(s) onboard used by the vessel to store its catch. Up to three storage types may be reported on the form. Code from Fish Storage Types e.g., BF
Autonomy range: Vessel autonomy, expressed by the time (days) a vessel can spend at sea without refuelling. If this information is not available then record vessel range expressed in cruising distance (nm). If a figure for the range cannot be obtained, the observer should calculate vessel range as follows: Vessel range (nm)> = <Vessel average cruising distance per metric tonne (nm/t)> : <Tonnage of fuel carried (t)> Note: specify units (days or nautical miles)
Field Requirement Description Format Input value
range_value O The vessel’s operational endurance, expressed either as the maximum number of days it can remain at sea without resupply, or as the maximum distance it can cover (in nautical miles, nm) Float e.g., 30
range_unit O The unit used to describe the value of autonomy range days or nm e.g., days

Vessel Electronics

Field Requirement Description Format Input value
gnss O Indicates whether or not one or more Global Navigation Satellite System systems (GNSS) such as the US Global Positioning System (GPS) were present on the vessel (Yes/No/Unk) String e.g., Yes
vms O Indicates whether or not one or more Vessel Monitoring Systems (VMS) were present on the vessel (Yes/No/Unk) String e.g., Yes
ais O Indicates whether or not one or more Automatic Identification Systems (AIS) were present on the vessel (Yes/No/Unk) String e.g., Yes
radars O Indicates whether or not one or more radars were present on the vessel (Yes/No/Unk) String e.g., Yes
track plotter O Indicates whether or not one or more track plotters were present on the vessel (Yes/No/Unk) String e.g., Yes
depth sounder O Indicates whether or not one or more depth sounders were present on the vessel (Yes/No/Unk) String e.g., Yes
sonar O Indicates whether one or more sonars were present on the vessel (Yes/No/Unk) String e.g., Yes
doppler current meter O Indicates whether one or more doppler current meters were present on the vessel String e.g., Yes
xbt O Indicates whether or not one or more expendable bathythermographs (XBT) were present on the vessel String e.g., Yes
vhf radios O Indicates whether or not one or more VHF radios were present on the vessel String e.g., Yes
hf radios O Indicates whether one or more HF radios were present or not on the vessel String e.g., Yes
satellite comms O Indicate whether or not one or more satellite communication systems were present on the vessel String e.g., Yes
fis O Indicates whether or not one or more Fisheries Information Services were present on the vessel String e.g., Yes

Waste Management Details

Waste Management Details: Up to four categories of waste and storage disposal may be reported on the form.
Field Requirement Description Format Input value
waste_management_category O The category of the waste produced by the vessel Code from Waste Categories e.g., CP
waste_storage_disposal_method O The method used to dispose of the waste Code from Storage / Disposal Methods e.g., AS

G-GENERAL

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric

Special Equipment Or Machinery

Field Requirement Description format Input value
live_bait_tank_capacity_m3 M The vessel total maximum capacity to store live bait, in cubic metres (m3) Float e.g., ADD
number_of_automatic_poles M The total number of automatic poles fixed on a vessel Integer e.g., ADD

General Gear Attributes

Field Requirement Description Format Input value
number_of_anglers M The maximum number of anglers observed during the trip Integer e.g., 25
Pole material: The material the pole is made of, including, but not limited to bamboo, fibre glass or carbon
Field Requirement Description Format Input value
material O The material of the poles used Code from Pole Material Types e.g., BM
description O Description of alternative pole material Free entry. Plain text e.g., tbd
Hook:
Field Requirement Description Format Input value
type O The type of hooks used for the observed trip. Up to 4 hook types may be reported on the form Code from Hook Types e.g., C11

E-SET-TUNA

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL
event_id M The event identifier of the observed event. This should be a four digit numerical code 0001. A unique identifier should be allocated to each individual event 4-digit-number e.g., 0004

Setting Operations

Start setting
Field Requirement Description Format Input value
date_time_utc M For the observed event, the date and time the first line enters the water YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
Position
Field Requirement Description Format Input value
latitude M The latitude at the start of the setting operation Decimal degrees (two decimal places) e.g., -20.88
longitude M The longitude at the start of the setting operation Decimal degrees (two decimal places) e.g., 55.53
End setting
Field Requirement Description Format Input value
date_time_utc M For the observed event, the time the last line comes out of the water YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
School sighting cues:
Field Requirement Description Format Input value
cue_1 O The cues that lead the vessel to detect the presence of a tuna school. Up to 3 cues can be reported on the form Code from School Sighting Cues e.g., AF
Target species:
Field Requirement Description Format Input value
species_1 M For the observed event, the species in the school being targeted. Up to 4 target species can be reported on the form Code from Target Species e.g., AG01
maximum_lines_fishing_at_the_same_time M For the observed event, the maximum number of lines fishing at the same time. These should include lines deployed from manual and automatic poles. If other lines are deployed, it should be specified, and then included in the total count Integer e.g., 150
Bait
Field Requirement Description Format Input value
used O Indicates whether any bait was used during the fishing event (Yes/No) String e.g., Yes
type O Indicates the bait types used during the fishing event Code from Bait Types e.g., FF
condition O Indicates the bait condition used during the fishing event Code from Bait Conditions e.g., DE
species O The species of bait used during the fishing event Code from Bait Species e.g., ANX
weight O The estimated quantity (kg) of bait used in the poling operation. If no bait, then would be zero (0) Float e.g., tbd
number_of_hooks_lost O The total number of hooks lost during the poling operation Integer e.g., 10
object_id O For every activity involving artificial FAD (DFAD/AFAD), there is a FAD identifier. This includes FAD markings, beacon IDs, or any information that can be used to identify the owner Alphanumeric e.g., ADD

E-SET-TUNA-CATCHES-FISHING-TRIP

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL

Catch Details

Field Requirement Description Format Input value
species M The species/species group of bait used Code from All Species e.g., ABL
Fate: The fate which includes whether an individual was retained or discarded and the reason
Field Requirement Description Format Input value
type M The type of fate Code from Types of Fate e.g., DI
code M Further description of the details associated with the type of fate Code from Fates e.g., DL
sampling_method M The sampling method used to obtain total catch estimates per species for the event Code from Sampling Methods for Catch Estimation e.g., EP
number_of_fish M The numbers of individuals observed/caught by species and fate (including if recording at an individual animal level) Integer e.g., tbd
Weight: The catch weight corresponding to the specified product type recorded in ‘weight code’. If the fish has not been processed, it corresponds to the unprocessed weight.
Field Requirement Description Format Input value
processing_type O Code from Fish Processing Types e.g., DR
value_kg O Float tbd
estimation_method O Code from Total Catch Estimation e.g., EP

E-SET-TUNA-CATCHES

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL
event_id M The event identifier of the observed event. This should be a four digit numerical code 0001. A unique identifier should be allocated to each individual event 4-digit-number e.g., 0004
specimen_id M The parent specimen identifier 4-digit number e.g., 0005
Field Requirement Description Format Input value
species O The species/species group of bait used Code from All Species e.g., ABL
Fate: The fate which includes whether an individual was retained or discarded and the reason
Field Requirement Description Format Input value
type O The type of fate for individuals Code from Types of Fate e.g., DI
code O Further description of the details associated with the type of fate Code from Fates e.g., DL
sampling_method O The sampling method used to obtain total catch estimates per species for the event Code from Sampling Methods for Catch Estimation e.g., EP
number_of_fish O Record the number of individuals per species for each specified fate. If weight is recorded, insert NA here. Integer e.g., tbd
Weight: The catch weight corresponding to the specified product type recorded in ‘weight code’. If the fish has not been processed, it corresponds to the unprocessed weight.
Field Requirement Description Format Input value
processing_type O Code from Fish Processing Types e.g., DR
value_kg O Float e.g., tbd
estimation_method O Code from Total Catch Estimation e.g., EP
Depredation details
Field Requirement Description Format Input value
depredation_source O For depredated specimens/or catch, record the depredation source based on depredation scar characteristics. For non-depredated specimens record NA Code from Depredation Sources e.g., BA
observed_predator O For depredated specimens/or catch, the predator species directly observed and identified. If the predator was not observed record UNK (unknown). For non-depredated specimens record NA Code from Predator Species e.g., AG15
Additional details
Field Requirement Description Format Input value
condition_at_capture O The condition of the specimen at capture Code from Individual Conditions e.g., A0
condition_at_release O The condition of the specimen at the time of release Code from Individual Conditions e.g., A0

E-SET-TUNA-CATCHES-SSI

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL
event_id M The event identifier of the observed event. This should be a four digit numerical code 0001. A unique identifier should be allocated to each individual event 4-digit-number e.g., 0004
specimen_id M The parent specimen identifier 4-digit number e.g., 0005

Specimen Details > Additionl Catch Details SSI

Field Requirement Description Format Input value
gear_interaction O The type of interaction of the specimen with the fishing gear (“UK” if unknown as not possible to collect) Code from Gear Interactions e.g., EF
brought_onboard O Indicates whether or not the specimen was brought onboard (Yes/No/Unk) String e.g., Yes
handling_method O Details how the specimen was brought onboard Code from Handling Methods e.g., AN
revival O Indicates whether or not the release took place with resuscitation for turtles (Yes/No/Unk) String e.g., Yes
photo_id O The unique identifier of the photo taken of a specimen Alphanumeric e.g., Doe_Hawwa_20260302_1435_hawksbill.png

E-SET-CATCHES-BIOMETRIC

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL
event_id M The event identifier of the observed event. This should be a four digit numerical code 0001. A unique identifier should be allocated to each individual event 4-digit-number e.g., 0004
specimen_id M The parent specimen identifier 4-digit number e.g., 0005

Specimen Details - All species

Field Requirement Description Format Input value
sampling_method M The sampling method used for the collection of biological sub-sample(s) Code from Biological Sampling Method e.g., ES
Length 1: Length of individual specimen
Field Requirement Description Format Input value
type M The length code used for the measurement Code from Length Measurements e.g., CF
value M The length (cm) corresponding to the length type taken rounded to the lower centimetre Float e.g., 34
measuring_tool M Specify the tool code used for the measurement Code from Length Measurement Tools e.g., CA
is_straight M Indicates whether the size measurement was made straight (Yes/No/Unk) String e.g., Yes
Length 2:
Field Requirement Description Format Input value
type M The length code used for the measurement Code from Length Measurements e.g., CF
value M The length (cm) corresponding to the length type taken rounded to the lower centimetre Float e.g., 34
measuring_tool M Specify the tool code used for the measurement Code from Length Measurement Tools e.g., CA
is_straight M Indicates whether the size measurement was made straight (Yes/No/Unk) String e.g., Yes
Weight: The specimen’s weight corresponding to the specified product type recorded in ‘weight code’. Unprocessed weight when the fish has not been processed
Field Requirement Description Format Input value
processing_type O The processing code used for the weight measurement Code from Weight Measurements e.g., GG
value O The weight corresponding to the measurement type code Float e.g., 43.2
estimation_method O Method used to estimate weight of specimen Code from Weight Estimation Methods e.g., BR
sex O The sex of the sampled fish specimen. If unknown record “U” Code from Sex e.g., F
Maturity: The stage of maturity of the specimen according to standard maturity scales approved by the IOTC. If unknown record UNK..
Field Requirement Description Format Input value
scale O Code list being developed
stage O Code list being developed
Sample collected: The following details on the collection of samples: a) type (e.g., otoliths, spine clippings, and genetic samples), b) preservation method (e.g., alcohol, frozen, etc.), c) destination (i.e., location to be sent/stored)
Field Requirement Description Format Input value
type O code list being developed
preservation_method O code list being developed
Destination O code list being developed
Tag details
Field Requirement Description Format Input value
release O Indicates whether or not the individual was re-released with a tag attached (Yes/No/Unk) String e.g., No
recovery O Indicates whether or not the individual was recovered with a tag attached (Yes/No/Unk) String e.g., Yes
type O The type of tag used Code from Tag Types e.g., CP
tag_number_1 O The tag identifier(s) Alphanumeric EXAMPLE TO ADD
tag_number_2 O The tag identifier(s) Alphanumeric EXAMPLE TO ADD
finder_name O DESCRIPTION TO ADD String e.g., Jane Doe
finder_contact_details O DESCRIPTION TO ADD String e.g., 345 Spear Street, San Francisco, CA 94105, USA | (650) 214-6369 | jane.doe@fishing.org

E-SET-BAIT

Field Requirement Description Format Input value
observed_trip_id O The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL
set_id O The parent set identifier

Setting Operations

Start setting
Field Requirement Description Format Input value
date_time_utc O Record the data and time when chumming for bait starts YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
Position: Record the data and time when chumming for bait starts
Field Requirement Description Format Input value
latitude O The latitude of the position at the start of the setting operation Decimal degrees (two decimal places) e.g., -20.88
longitude O The longitude of the position at the start of the setting operation Decimal degrees (two decimal places) e.g., 55.53
End setting
Field Requirement Description Format Input value
date_time_utc O The date and time at the end of the bait fishing event, when the last brail is scooped from the net YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
Position:
Field Requirement Description Format Input value
latitude O The latitude of the position at the end of the setting operation Decimal degrees (two decimal places) e.g.,-20.88
longitude O The longitude of the position at the end of the setting operation Decimal degrees (two decimal places) e.g., 55.53
Depth:
Field Requirement Description Format Input value
value O The depth of the place where the net is being deployed. Float e.g., tbd
unit O Indicate units (FT or M) String e.g., ft
fishing_gear O The fishing gear during the specific bait fishing event Code from Fishing Gear e.g., DL
number_of_fishers O The number of fishers that participate to the bait fishing event Integer e.g., 25

E-SET-BAIT-CATCHES

Weight: The specimen’s weight corresponding to the specified product type recorded in ‘weight code’. Unprocessed weight when the fish has not been processed
Field Requirement Description Format Input value
processing_type O The processing code used for the weight measurement Code from Weight Measurements e.g., GG
value O The weight corresponding to the measurement type code Float e.g., 43.2
unit O Unit of weight (kg or t) String e.g., kg
measurement_tool O Method used to estimate weight of specimen Code from Weight Estimation Methods e.g., BR

E-SET-BAIT-CATCHES-SPECIMEN-SSI

Specimen Details - Additional Catch Details SSI

Field Requirement Description Format Input value
gear_interaction O The type of interaction of the specimen with the fishing gear (“UK” if unknown as not possible to collect) Code from Gear Interactions e.g., EF
brought_onboard O Indicates whether or not the specimen was brought onboard (Yes/No/Unk) String e.g., Yes
handling_method O Details how the specimen was brought onboard Code from Handling Methods e.g., AN
condition_at_capture O The condition of the specimen at capture Code from Individual Conditions e.g., A0
condition_at_release O The condition of the specimen at the time of release Code from Individual Conditions e.g., A0
revival O Indicates whether or not the release took place with resuscitation for turtles (Yes/No/Unk) String e.g., Yes
photo_ID O The unique identifier of the photo taken of a specimen Alphanumeric e.g., Doe_Hawwa_20260302_1435_hawksbill.png

D-ACTIVITIES

Field Requirement Description Format Input value
observed_trip_id M The parent observed trip identifier Alphanumeric e.g., 2024-01-23/IOTCFRA001/IOTC012345/PL

Activity Details

Field Requirement Description Format Input value
date_time_utc M The date and time of a specific vessel activity YYYY-MM-DD hh:mm e.g., 2025-09-15 12:00
latitude M The location of a specific vessel activity Decimal degrees (two decimal places) e.g.,-20.88
longitude M The location of a specific vessel activity Decimal degrees (two decimal places) e.g., 55.53
activity_type O The depth of the place where the net is being deployed vessel activity at the start of every fishing activity and every two hours from sunrise to sunset Code from Surface Fishery Activities e.g., BA
Comments O Free entry. Plain text.

Reporting deadlines

  • Surface fisheries: 30 June (final)

Reference Code Lists

Entities

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Countries

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Ports

  • Permalink
  • Version: 1.0.0
  • Last update: 2025-08-25

Reasons for Days Lost

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Target Species

  • Permalink
  • Version: 1.0.1
  • Last update: 2025-06-27

Fishing Gear

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Hull Material Types

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Vessel Size Types

  • Permalink
  • Version: 1.0.0
  • Last update: 2025-06-26

Fish Preservation Methods

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Fish Storage Types

  • Permalink
  • Version: 1.0.3
  • Last update: 2025-05-29

Waste Categories

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Storage/Disposal Methods

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Pole Material Types

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Hook Types

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

School Sighting Cues

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Target Species

  • Permalink
  • Version: 1.0.1
  • Last update: 2025-06-27

Bait Types

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Bait Conditions

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Bait Species

  • Permalink
  • Version: 1.0.1
  • Last update: 2025-06-27

All Species

  • Permalink
  • Version: 1.0.1
  • Last update: 2025-06-27

Types of Fate

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

##Fates {#fates}

  • Permalink
  • Version: 1.0.1
  • Last update: 2024-02-01

Sampling Methods for Total Catch Estimation

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Weight Measurement Tools

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Depredation Sources

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Predator Species

  • Permalink
  • Version: 1.0.1
  • Last update: 2025-06-27

Individual Conditions

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Gear Interactions

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Handling Methods

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Biological Sampling Methods

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Length Measurements

  • Permalink
  • Version: 1.0.6
  • Last update: 2024-09-28

Length Measurement Tools

Weight Measurements

  • Permalink
  • Version: 1.0.6
  • Last update: 2024-09-28

Sex

  • Permalink
  • Version: 1.0.2
  • Last update: 2023-06-15

Tag Types

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12

Surface Fishery Activities

  • Permalink
  • Version: 1.0.0
  • Last update: 2023-05-12