Detailed history of areas, flocks and number of operators per EPCI

Open data API in a single place

Provided by Agence Bio

Get early access to Detailed history of areas, flocks and number of operators per EPCI API!

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

Dataset information

Country of origin
Updated
2025.07.21 12:08
Created
2024.07.08
Available languages
English
Keywords
Quality scoring

Dataset description

Source: BIO Agency / Certification Bodies These data on the number of operators, areas and herds are derived from the annual checks carried out by the approved certifying bodies on farms and processing companies, which are engaged in organic distribution. **Geographical precision** The agricultural parcels of the same holding may be distributed over several EPCIs, but are all declared in the EPCI where the place of activity is located or, failing that, the place of business of the holding. **Operator data** Number of operators per municipality, or alternatively by postal code. All operators are located by their postal code, almost all by the municipality of their head office ActiviteBio: _P _: producers (incl. producers with another activity: processing on the farm, store on the farm...) _T _: processors or restaurants (incl. processors with another activity: processor-distributors or processor-importers) _D _: distributors (including distributors with an import activity: distributor-importers...) _I _: importers **Surface data** Areas certified organic or in conversion at the end of the year _nb \_exp _ : Number of holdings engaged (with or without area engaged (yc beekeepers etc …) _SurfAB _ : Areas under organic farming which have reached the end of their conversion period _SurfC1 _ : Areas in the first year of conversion _SurfC2 _ : Areas in second year of conversion _SurfC3 _ : Surface in third year of conversion _SurfC123 _ : Total area in conversion _SurfBIO _ : Total area committed in organic (AB and in conversion) Crop groups: _AU _: Other of which (fallows, green manure, flowers, mushrooms etc …)\* _SF _: Forage crops (including permanent and temporary grassland, but forage other forage crops, ranges, etc.) _FR _: Fruit (arboriculture including nuts, fresh fruit and processing fruit) _GCU _: Field crops (including pulses) _LE _: Fresh vegetables (greenhouse market gardening or field pein (including potato) _PP _: PPAM _VI _: Viticulture (of which 4% table grapes at national level) _HSAU _: Excluding utilised agricultural area: the surfaces of collective estives, wild harvesting, wood, marshes ... are not taken into account **Hive and flock data** Number of animals (or hives) committed at the end of the year (excluding aquaculture) _nb \_exp _: Number of holdings engaged (with or without area engaged (yc beekeepers etc …) _CheptelAB _: Heads or hives having reached the end of their conversion _CheptelConversion _\*: head or hives in conversion (simultaneous or not) Group of animal species _VA _: Breastfeeding cows _VL _: Dairy cows _PO _: Laying hens _PC _: Broiler chickens _AUVOL _: Other broiler poultry _BL _: Milk ewes _BV _: Meat ewes _CH _: Goats _TR _: Breeding sows _LAR _: Rabbits _LA _: Rabbits _AUPA _: Other animal production (deer, … snails) _API _: Beekeeping: in number of Ruches
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