Offshore Fishery Effort by Gear Type

Open data API in a single place

Provided by Marine Institute

Get early access to Offshore Fishery Effort by Gear Type API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2026.04.07 15:11
Created
2019.11.19
Available languages
English
Keywords
environment
Quality scoring

Dataset description

This dataset shows the distribution of fishing effort by fishing vessels according to the gear type used. Fishing effort is defined as the time spent engaged in fishing operations or time spent at sea, this time may be multiplied by a measure of fishing capacity, e.g. engine power. In this dataset fishing effort is measured as average hours spent actively fishing per kilometre square, per year. Data from years 2014 to 2018 was used to produce this data product for the Marine Institute publication the “Atlas of Commercial Fisheries around Ireland, third edition“ (https://oar.marine.ie/handle/10793/1432). Effort for offshore fisheries is based on the following 2 primary data types - data on vessel positioning and data on gear types used: Vessel Monitoring Systems (VMS) supplied by the Irish Naval Service provide geographical position and speed of vessel at intervals of two hours or less (Commission Regulation (EC) No. 2244/2003). The data are available for all EU vessels of 12m and larger, operating inside the Irish EEZ; outside this zone only Irish VMS data are routinely available. VMS do not record whether a vessel is fishing, steaming or inactive. Logbooks collected by the Sea-Fisheries Protection Authority and supplied by the Department of Agriculture, Food and the Marine were the primary data source for information on landings and gear types used by Irish vessels. EU Fleet Register obtained from the EU fleet register (http://ec.europa.eu/fisheries/fleet/index.cfm) provides information for non-Irish vessels and for Irish vessels for which the gear was not known from the logbooks. Note that if vessels use more than one gear, it is possible that the gear type assigned to them was not the one that was actually used. The fishing gear data was classified into eight main groups: demersal otter trawls; beam trawls; demersal seines; gill and trammel nets; longlines; dredges; pots and pelagic trawls. The VMS data was analysed using the approach described by Gerritsen and Lordan (IJMS 68(1)). This approach assigns effort to each of the VMS data points. The effort of a VMS data point is defined as the time interval since the previous data point. Next the data are filtered for fishing activity using speed criteria, vessels were assumed to be actively fishing if their speed fell within a certain range (depending on the fishing gear used). The points that remain are then aggregated into a spatial grid to produce a raster dataset showing fishing effort (in hours) per kilometre square per year for each gear type group. The data is available for all countries combined and for Irish vessels only. None
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks