Table 1 Summary of data sources for each member state.<\/b><\/p>\n
The compiled data inventory includes 19 EU member states with varying levels of spatial and temporal coverage, as well as differences in thematic detail (Fig.\u00a02<\/a>). In most member states, the data are administered at the national level and cover the entire member state; however, in a few cases, the subsidy applications are managed at sub-national administrative levels, and thus, the data are managed and stored at the level of federal states (Germany), regions (Belgium), or provinces (Spain). For Spain, we provide the data for all provinces, while in Belgium, only data for Flanders is available for sharing. In Germany, we currently present data for three federal states (Brandenburg, Lower Saxony and North Rhine-Westphalia); for the other federal states, we either cannot share data or requests are still pending at the time of writing. One German federal state, Schleswig-Holstein, refused to share the data due to data privacy issues. Furthermore, the three city-states, Berlin, Bremen, and Hamburg, do not collect the data but are included in the datasets of neighbouring federal states. Additionally, in France and Portugal, the spatial availability of the data varies across the years, with more recent data being provided at the national level, while older data were available at the regional level for Portugal and the provincial level for France. For France, we have complete national coverage for all years presented. In contrast, a full national coverage for Portugal is only available from 2020 onwards.<\/p>\n For most member states, only crop-specific information is available for sharing. However, six of the 19 member states (Czechia, Denmark, Estonia, Ireland, Portugal and Spain) provide a farm identifier, and five of them (Austria, Flanders in Belgium, Denmark, Ireland and Bulgaria) disclose information on organic management (Fig.\u00a02a<\/a>). Temporally, the data coverage varies between one year (2024 for Lithuania) and 17 years (2007\u20132023 for France and 2008\u20132024 for Flanders in Belgium). For seven member states, federal states, or regions, we obtained time series of up to five years; for six, up to ten years; for four, up to 15 years; and for another four, up to 17 years (Fig.\u00a02b<\/a>).<\/p>\n The original national crop classifications vary from 19 classes in Croatia to 963 classes in France (Fig.\u00a03<\/a>). The crop classification usually consists of a crop code and an assigned crop name. However, the meaning of crop codes can change between years, crop codes can be added or removed, and the crop names can be written differently in different years. We only reported the unique combinations of crop codes and crop names.<\/p>\n Fig. 3<\/b> The number of different crop entries of the member states, federal states, and regions within our data inventory.<\/p>\n Pre-processing and harmonisation<\/p>\n To harmonise the datasets across all member states, we developed a uniform data structure of the spatial information and harmonised the information on crops and organic cultivation. The harmonisation was done separately for each member state, federal state, and region. Our harmonisation workflow included the following steps:<\/p>\n First, to explore the data and understand the meaning of data table columns, we listed all column names from the original vector data for each year, along with examples of the values stored in each column. This provided us with an understanding of the data structure and content. Additionally, we manually explored the data in QGIS.<\/p>\n To automate the subsequent steps, we created column-name lookup tables for each member state. This was necessary to automate the assignment of all the original columns to the harmonised column names (Table\u00a02<\/a>). The table included a separate column with the translation for each year, as column labels varied between years.<\/p>\n Table 2 Structure of the harmonised spatial data.<\/b><\/p>\n To harmonise the crops, we listed all available \u2018crop code – crop name\u2019 combinations in the vector data. In some cases, the meaning of the crop codes could change between years, or their descriptions could change. Working with the \u2018crop code \u2013 crop name\u2019 combinations ensured avoiding inconsistencies and misclassifications between the years. We then translated all crop names into English. In cases when a translation was not possible, we conducted a web search using the original crop entry.<\/p>\n For the harmonisation of the crop codes and crop names, we build on the proposed crop harmonisation of the EuroCrops project16<\/a>. Therefore, when available, we used the crop-mapping tables from the EuroCrops project to categorise the \u2018crop code \u2013 crop name\u2019 combinations (https:\/\/github.com\/maja601\/EuroCrops\/tree\/main\/csvs\/country_mappings<\/a>). In most cases, not all entries could be categorised automatically as the data include crops from multiple years, in contrast to EuroCrops. Hence, we manually expanded the existing EuroCrops tables and categorised all crops that had not been previously categorised. In cases where no crop-mapping table was available from EuroCrops, we manually categorised the crops. To reduce the workload, we used a string-matching algorithm on the English crop names, applying the Jaro-Winkler distance metric to associate unclassified entries with classified entries from other member states. The Jaro-Winkler metric measures string similarity based on the number of matching characters and transpositions (i.e., swapped letters). It is particularly useful for record matching and is therefore well-suited for matching crop type names19<\/a>,20<\/a>. All matching was performed on the English crop names. Manual verification of the matched entries and classification of any potentially remaining unclassified entries were still necessary; however, the workload was substantially reduced. Once the crop-mapping tables were finalised, we used them to harmonise the crop codes and names into the EuroCrops HCAT.<\/p>\n As described above, the EuroCrops HCAT consists of six hierarchical levels with increasing thematic details, but the original crop classifications of the member states provide different levels of detail. Sometimes, the crop codes of a member state fall into higher levels of the HCAT, while in other cases, they fall into lower levels. We extended the HCAT by including crop-mapping tables of nearly all EU member states (excluding Luxembourg and Malta) and by including historical data, in some cases going back to 2007, into our inventory. To facilitate interoperability with the EuroCrops database, we used the same column names as in the HCAT.<\/p>\n Across member states, there were differences in how the crop-specific information was stored in the data. In some member states, applicants can only declare a single crop at the parcel level, while in others, spatial data are only available at the reference-parcel level. Here, multiple crops can be declared within a reference parcel. When multiple crops were reported per reference parcel, our harmonised geospatial data only contain the crop information of one crop within the reference parcel. In such cases, the \u2018field size\u2019 refers to the entire reference-parcel area, while the \u2018crop area\u2019 refers to the area of the dominant crop reported in the crop columns. For example, if two crops are reported, with one crop covering 70% of the reference parcel and the other crop covering 30%, then the crop covering 70% is considered the dominant crop, and its area would be reported in the \u2018crop area\u2019 column. The additional crop data were saved in a complementary table linked to the reference parcel via the field ID.<\/p>\n Furthermore, we used the column-name translation tables to harmonise the column names. In most cases, the data included a unique national field ID. However, in cases where this ID was missing, we generated a running ID to ensure\u00a0that all parcels have a unique identifier per member state. Where information was available, we extended the datasets by adding columns for farm identifiers or information on whether a parcel was managed organically. To harmonise the information on organic farming, we classified the parcels into three categories: \u2018conventional\u2019, \u2018organic\u2019, and \u2018in conversion\u2019 using the codes 0, 1, and 2, respectively. In some member states, this information was provided at the parcel level; in others, it was available only at the farm level. For the latter, we assigned the farm-level information to the respective parcels. Future versions of the harmonised inventory will include information on agri-environmental measures, eco-schemes, and animal numbers per farm. All geospatial data were transformed into a projected coordinate system (ETRS89-extended \/ LAEA Europe \u2013 EPSG:3035), and the files were saved as geoparquets.<\/p>\n","protected":false},"excerpt":{"rendered":"Data collection Collecting IACS data is tedious due to the varying levels of data accessibility among EU member…\n","protected":false},"author":2,"featured_media":200163,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5174],"tags":[3971,80937,2000,299,5187,1699,39037,3965,3966,70],"class_list":{"0":"post-200162","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-eu","8":"tag-agriculture","9":"tag-databases","10":"tag-eu","11":"tag-europe","12":"tag-european","13":"tag-european-union","14":"tag-geography","15":"tag-humanities-and-social-sciences","16":"tag-multidisciplinary","17":"tag-science"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@uk\/114716352805428038","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/200162","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/comments?post=200162"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/200162\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media\/200163"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media?parent=200162"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/categories?post=200162"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/tags?post=200162"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"figure](\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/06\/41597_2025_5210_Fig3_HTML.png\")
<\/a><\/p>\n