Fisheries control statistics

Open data API in a single place

Provided by Ministère de la Transition écologique

Get early access to Fisheries control statistics API!

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

Dataset information

Country of origin
Updated
2026.03.27 02:15
Created
2022.11.22
Available languages
English
Keywords
peche, biodiversite, peche-halieutique, gestion-de-la-peche, controle, environnement
Quality scoring

Dataset description

In order to protect fisheries resources, marine biodiversity and long-term fishing-related economic activity, the State Startup [MonitorFish & MonitorEnv](https://beta.gouv.fr/startups/monitorfish.html) is developing tools to improve the targeting and monitoring of fisheries controls and controls of the marine environment. On the fisheries side, the State Startup has defined indicators to assess its impact, including: — the **infringement rate** on checks carried out: the more checks are carried out on these relevant targets, the higher the proportion of checks involving an infringement must be — the **part of controls carried out on a high-risk fleet segment**: the [European Regulation 2018/1986](https://eur-lex.europa.eu/legal-content/FR/TXT/?uri=CELEX%3A32018D1986&qid=1668767130195) sets a 60 % target for controls on a ‘high’ or ‘very high’ risk fleet segment according to the risk analysis carried out in accordance with the EFCA methodology(https://www.efca.europa.eu/en/content/guidelines-risk-assessment-methodology-fisheries-compliance). This objective reflects a desire for efficiency in the use of State resources, focusing the use of means of control on fleet segments with real challenges for the protection of the resource. For this purpose, the State Startup publishes: — the **definition of EFCA fleet segments** by which France is concerned — of **fisheries control statistics** For the **control statistics** file, the columns of the file are as follows: — **control_year**: year of inspection — **control_type**: type of control. Possible values: — Landing control — Control at sea — Air traffic control — **facade**: maritime control facade (see map below). For metropolitan facades (SA, NAMO, MEMN, MED), the areas have been extended beyond the boundaries of the French EEZ. Possible values: — NAMO: North Atlantic-West Channel — SA: South Atlantic — MEMN: Sleeve-Est-Mer-du-Nord — MED: Mediterranean — Martinique — Guyana — Guadeloupe — South Indian Ocean — Off facade — **segment**: fleet segment of the vessel, determined on the basis of catches (species, catch areas and fishing gear used) in hold at the time of control. — **control_month**: month of inspection — **number_controls**: number of inspections carried out this month for this segment, this type of inspection and on this facade — **number_controls_ytd**: number of checks carried out since the beginning of the year for this segment, this type of inspection and on this facade — **target_number_of_controls_year**: objective of checks to be carried out over the year for this segment, this type of inspection and on this facade — **infringement_rate**: infringement rate on the inspections carried out this month for this segment, this type of inspection and on this facade — **infringement_rate_ytd**: infringement rate on controls carried out since the beginning of the year for this segment, this type of inspection and on this facade For the file of **definition of fleet segments**, the columns of the file are as follows: — **segment**: code of the segment used in the control statistics file — **segment_name**: intuitive description of the segment — **Gears**: list of FAO codes of gear concerned by the segment — **fao_areas**: lists of FAO Areas Affected by the Segment — **Species**: list of FAO codes of species concerned by segmen — **impact_risk_factor**: segment risk factor according to EFCA methodology, on a scale of 1 (low) to 4 (very high) — *Map of maritime facades* [enter image description here](https://github.com/MTES-MCT/monitorfish/blob/master/datascience/docs/source/_static/img/facade-areas.png?raw=true “enter image title here”)
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