List of all metadata reports | This report's TOC | Previous Page | Next Page
Database Title |
7.1 Catch effort database |
|---|---|
| Keywords Type1. Type 11. |
New Zealand EEZ; Fisheries; catch effort |
| Abstract | This database details the catch effort data for commercial fishing operations.
It includes:
The second item includes the confirmed catch measured by the processor which theoretically includes the fate of all species caught. |
| Geographical Coverage | New Zealand EEZ |
| Dataset start date. | 1982-1989: this data is in a different format to later data and is harder
to access and query. Pre 1982 data is bitsy and probably will not be integrated into the main database. 1989-current: integrated data sets that can be queried& |
| Dataset end date. | Current |
| Status/currency. | In progress |
| Update frequency. | Regular |
| Maintenance. | The database itself is maintained by Fish Serve. The Ministry of Fisheries maintains the database system. |
Technical Evaluation |
|
|---|---|
| Parameters- what is measured |
|
| Parameters- what is calculated | An index of abundance is derived by dividing catch by effort. |
| Methods used to measure parameters | Fishers complete appropriate forms depending on what they are catching and
the methods used. The forms are:
Fishers also complete monthly quota management reports. Fish processors complete monthly licensed fish receivers returns. |
| Scale of use. | N/A |
| Number of records | This is a very large database with approximately 35 people employed full time programming, entering, validating, and extracting data. Approximately 200,000 forms are returned each year. |
| GIS compatibility. | Some data is spatially referenced using latitude and longitude. Other locational data refers to fisheries statistical areas which are specific to some fisheries. |
| Available formats for users. | This is a relational database. Information requests will be answered using a text file or Excel spreadsheet. |
| Access constraints. | The information in this database is commercially sensitive. This means that information requests will usually receive aggregated data. The level of aggregation will depend on the use of the data. |
| Measurement Accuracy | To be completed by database manager. |
| Completeness of dataset | To be completed by database manager. |
| Positional accuracy | To be completed by database manager. |
| Database steward | Ministry of Fisheries |
| Database custodian | Ministry of Fisheries and Fish Serve |
| Database custodian contact person | Kim Duckworth Research Data Manager |
| Database custodian Contact Address Phone Fax |
Ministry of Fisheries PO Box 1020 Wellington +64 4 460 4600 +64 4 460 4601 duckwork@fish.govt.nz |
| References | - |
| Date metadata record prepared. | June 2000 |
| Author of metadata record. | Victoria Froude |
Management Evaluation |
|
|---|---|
| Original purpose. | Research purposes |
| Relationships with classification systems. | N/A |
| Relationships with other databases | The database is used with a wide range of fisheries datasets. Eg. it is used with additional research data to improve fisheries population models and estimates of fish stock biomass. |
| Known relationships with proposed EPIP indicators. | This database can be used for a number of fisheries indicators. |
| Database uses? |
|
| Public awareness of the database | Very high amongst stakeholders. |
| Database strengths. |
|
| Database limitations. |
|
What are the Current and Emerging Uses of the Database for: |
|
|---|---|
| Assisting with determining historic state/baseline. | This is possible where the data exists. |
| Assisting with determining current state/baseline. | This is a strong point of the database. |
| Assisting with modeling possible future outcomes. | NIWA uses data from the database to assist with the modeling of fish stock populations and biomass. |
| Risk assessment. | The database contributes to formal risk assessments for fish stocks. |
| Monitoring site selection and sample design. | The database addresses all commercial fishing. |
| Aggregating and reporting data locally, regionally or nationally. | This is generally possible. For some data is not possible to go below the level of the fisheries statistical area. |