|
Catch and Effort Returns – Fishing Details |
Sample of data | Sample of data - from few key tables in the catch effort database is available on this CD. |
Description of data collection system
|
Catch and effort returns are required for all commercial fishing inside the New Zealand EEZ and New Zealand vessels fishing on the high seas[1]. The high seas reporting requirement was introduced during 2001. There are six types of catch and effort (fishing details) forms in use. These are:
In addition to these form types there are versions of four of these forms specifically for reporting fishing by New Zealand vessels on the high seas. These are known as the HS-TCEPR (High Seas TCEPR), HS-CELR, HS-TLCER, and the HS-SJCER. These are nearly identical to the standard version of the form, but the reporting requirements may differ slightly. For example, some species codes may be permitted on high seas forms that would not be valid species codes on a standard form. |
Purpose of the data collection
|
The purposes of the catch and effort returns are to provide information for: 1) Stock assessment 2) Monitoring environmental performance 3) Policy evaluation 4) Operational functions (such as fulfilling international reporting obligations) 5) Enforcement 6) Fisheries administration Of these the fishing details sections of the forms are mainly provided for the purposes of:
The catch effort returns relate details about the fishing activity (including information about the location of fishing) directly to an estimate of the amount of fish caught. However catch and effort returns are not normally used to estimate the total harvest (extraction's) of a species. This type of information is usually more accurately determined from other data such as Catch Landing Returns, Licensed Fish Receiver Returns and Monthly Harvest Returns (and previously Quota Management Reports). |
Coverage of data set
|
This data set is a total coverage data set in which the entire New Zealand commercial catch is required to be reported with the exception of catches from high seas fishing where there may be alternative reporting obligations. The permit holder should be reporting both QMS and non-QMS species in this system. However fish caught in very small quantities (not one of the top five catches in the unit of effort being reported) will not be recorded (except on TLCER forms). Fish that are not landed (for example fish that are later discarded) should be reported through this system (provided they are in the top five species), although there may be some underreporting. |
Reporting requirements
|
The permit holder is required to fill in fishing detail forms:
|
Temporal Resolution
|
|
Spatial Resolution
|
|
Date of first available historic data
|
In some cases data back to the early 1980’s exists, but is not accessible from Ministry databases. Work is currently underway to convert this older data into a more readily available format |
Timeframe for data availability
|
This depends on the level of quality and completeness required. (1) A scanned version of the form should be available to Ministry staff with access to the Catch Effort Application 2 days after receipt (which may be up to 46 days after the end of the trip without being overdue) (2) Entered data should be available 10 days after receipt (receipt may be up to 46 days after the end of the trip without being overdue). To ensure that data from late returns is included in the dataset, data should not be extracted until 2 to 3 months after the fishing occurred. (3) Data from first level checking (for data entry errors etc.) should be available 20 days after data entry (data entry may be up to 56 days after the end of the trip without being overdue); (4) Complete data (after follow-ups for late returns) and data from final data checking, (involving contact with fishers) should be available within 4-6 months. |
Extent of validation/checking
|
Prior to 2001, data checking of the database was largely limited to referential integrity on certain “coded” fields (e.g. species codes, fishing method codes etc.) and dates. No active checking was conducted on effort data, nor on most catch data. A significant upgrade occurred between September 2000 and September 2001. From mid-2001 onwards, checks were also conducted on improbable values of primary fields (such as fishing method specific and species-specific checks on the main effort and catch information fields). As a consequence data quality is significantly better from 2001 onwards. The full suite of checks is described in the document “Catch Effort Data Quality Specifications and Standards”. |
Limitations of the data
|
There are a number of limitations and problems in this data set that need to be considered. When you run reports through the Reporting Tool within FIS a number of these problems which are likely to be relevant to your query will be brought to your attention. In general, remember that:
|
Stewardship of the data |
The MFish Research Data Manager within the Science Group is the Steward of the data (the Ministry’s guardian of the information on behalf of the Crown). The catch effort computer system is controlled and maintained by the Ministry of Fisheries. Services such as data entry and validation (the correction of errors and anomalies detected in the data after data entry) are handled by FishServe under contract to the Ministry of Fisheries. Books of forms are available from FishServe. |
Access to the data
|
Data from this data collection system is available either:
Contact Co-ordinator for more information on how to get access to any of these systems |
|
Catch and Effort Returns - Landing Details |
Description of data collection system
|
Catch landing returns are required for all commercial fishing inside the New Zealand EEZ. Landing returns record the catch that is landed, lost, discarded at sea, or retained on board after a landing. Landing returns are required from all commercial fishing operations for all species, and hence, this is theoretically the most comprehensive source of information for commercial harvest levels in New Zealand. There are four types of catch landing forms in use, these being:
|
Purpose of data collection
|
The purposes of the landing returns are to provide information for: 1) Stock assessment 2) Monitoring environmental performance 3) Policy evaluation 4) Operational functions (such as meeting international reporting requirements) 5) Enforcement 6) Fisheries administration Of these the landings forms are particularly important for:
|
Coverage of data set
|
This data set is a total coverage data set in which the entire New Zealand commercial catch is required to be reported with the exception of fish that are both caught on the high seas and are landed outside of New Zealand. Fish that are not part of the QMS system and fish that are not landed to a LFR are still required to be reported in this system. |
Reporting requirements
|
The permit holder is required to complete landing details returns:
|
Temporal Resolution |
The temporal resolution is the precise date of landing. However, a single landing could cover catches that have been obtained from a long trip of weeks to months in duration. |
Spatial Resolution |
The catch dataset is reported to the level of a Fishstock (e.g. CRA1, ORH2B etc.). For non-QMS species this would locate the catch to within one of the ten Fisheries Management Areas. Contact Fishserve if you would like copies of the maps. |
Date of first available historic data
|
In some cases data back to the early 1980’s exists, but is not accessible from Ministry databases. Work is currently underway to convert older data (back to the early 80’s) into a more readily available format. |
Timeframe for data availability
|
This depends on the level of quality and completeness required. (1) A scanned image of the form should be available to MFish staff with access to the Catch Effort Application 2 days after receipt (which may be up to 46 days after the landing without being overdue) (5) Entered data should be available 10 days after receipt (receipt may be up to 46 days after the landing without being overdue). To ensure that data from late returns is included in the dataset, data should not be extracted until 2 to 3 months after the fishing occurred. (2) Data from first level checking (for data entry errors etc.) should be available 20 days after data entry (which may be up to 56 days after the landing without being overdue); (3) Complete data (after follow-ups for late returns) and data from final data checking, (involving contact with fishers) should be available within 4-6 months. |
Extent of validation/checking
|
Prior to 2001, data checking of the database was largely limited to referential integrity on certain “coded” fields (e.g. species codes, processed state codes etc.) and to checks for overdue returns. A significant upgrade to the validation system occurred between September 2000 and September 2001. From mid-2001 and onwards, checks were also conducted on improbable values of primary fields (such as species specific checks on the landed weight etc.) As a consequence, data quality is significantly better from 2001 onwards. The full suite of checks is described in the document “Catch Effort Data Quality Specifications and Standards”. |
Limitations of the dataset
|
There are a number of problems in this data set that need to be considered. When you run reports through the Reporting Tool within FIS a number of these problems which are likely to be relevant to your query will be brought to your attention. In general, remember that:
|
Stewardship of the data |
The MFish Research Data Manager within the Science Group is the Steward of the data (the Ministry’s guardian of the information on behalf of the Crown). The catch effort computer system is controlled and maintained by the Ministry of Fisheries. Services such as data entry and validation (the correction of errors and anomalies detected in the data after data entry) are handled by FishServe under contract to the Ministry of Fisheries. Books of forms are available from FishServe. |
Access to the data
|
Data from this data collection system is available either:
Contact Co-ordinator for more information on how to get access to any of these systems |
[1] An exception may exist for high seas catches in cases where the vessel is required to report their high seas catch to another jurisdiction