UC1/US5 - Create a composite map derived from relevant national soil data

[pvgenuchten]

As a software developer of a web application for arable farmers, '

We would like Soilwise to produce and provide a composite map derived from relevant national collections, addressing the challenges posed by fragmented soil data and formal reference boundaries in countries like Germany,

So I can enhance and maintain our platform. This effort is crucial for our international expansion, as it will significantly reduce development time and costs associated with country-specific intricacies. We anticipate a 20% increase in market share in Germany, building on the positive reception experienced in other European countries. This enhancement will not only streamline software development but also deliver substantial value and relevance to our international user base.

Extended user story description

I am a software developer, without much in-depth knowledge of soils. I work at Crop-X, a software company that combines agronomic knowledge with advanced analytics and machine learning. Our target group are farmers. We offer a user-friendly platform that brings together agricultural data from different sources. Our tool collects data from the soil to the air, and transforms it into useful information, helping farmers monitor the health of fields and crops. This leads to higher yields and minimizes the impact on the environment.

Crop-X is an international operation. In Europe we are active in countries such as the Netherlands, Denmark, Flanders and Germany. Open access repositories are an important resource for our commercial products. However, differences in sampling strategies, designs and protocols make soil data difficult to compare across member states. Our global platform would benefit from a useful map. Currently we use LUCAS-wrb with USDA classification. This USDA texture classification for Europe is open, but very coarse (10x10k grid) and relevant characterization on organic matter is missing ("peat" does not exist, for example). So I use maps that are in line with Dutch practice in the Netherlands. But these are often missing in other countries, or they are created in a completely different classification manner.

Current soil maps, like the one for the Netherlands, include excessive details with 150 classes and Latin names, making it impractical for practical agricultural use. We require a streamlined system that prioritizes information essential for crop planning and management, which also harmonizes current soil monitoring systems (e.g. by developing transfer functions) Also very relevant are official maps with classifications on regulations. For the Netherlands for instance we have important regulations regarding manure, erosion-sensitive areas, nitrate-sensitive areas, etcetera. These have a direct influence on what a farmer is allowed to do. For farmers this type of information is not known, it is hard to find and keep track of.

Furthermore, when considering the entire EU, there's a crucial gap in formal boundaries of crop fields. While some countries like the Netherlands provide this data, others like Germany and Spain have fragmented data, and Poland, Italy, and Hungary lack it altogether. Manual registration is the fallback, but it's laborious and lacks precision. A comprehensive solution is needed to address this inconsistency in field boundary data across different EU countries.

Acceptance criteria

• [ ] In our European platform we are able to present soil maps with a focus on essential classifications relevant to agronomic perspectives, eliminating unnecessary details such as excessive classes and Latin names.
• [ ] We are able to integrate official soil maps that include classifications based on relevant European regulations, such as nitrate-sensitive areas.
• [ ] Our system is able to provide automated updates for soil maps and regulatory classifications to ensure that farmers have access to the latest information without manual intervention.
• [ ] With our software we can ensure consistency in field boundary data across different EU countries, addressing fragmentation issues in countries like Germany and Spain and providing comprehensive coverage, even in countries like Poland, Italy, and Hungary. (eliminating the need for manual registration).
• [ ] The solution should be scalable to accommodate data from various EU countries and regions, ensuring that it can adapt to evolving agricultural needs and regulatory changes.

[chlebas]

Who will define the essential classifications relevant to agronomic perspectives? Does SWR need to provide a delineation of agricultural parcels in Europe? With its evolution in time? How to do it?

[KathiSchleidt]

Extracted Requirements:

• 01.1 - Data Discovery - Query Catalogue: topic query integrating relations from vocabularies and knowledge (e.g. including narrower terms and synonyms)
• 01.2 - Data Discovery - map preview: overview of a specific property/indicator (map and graphs)
• 04 - Download data: data download with an API
• 04 - Download data: data subscription - allow user to subscribe to a specific topic, be informed of updates
• 06 - Data quality checks: ensure consistency in field boundary data across different EU countries 
• 08 - Vocabulary: Enablement of rich vocabulary including broader/narrower terms and synonyms
• 09 - Knowledge: Integration of Knowledge with Vocabularies
• 10 - Data harmonization: Standardized formats and APIs for data exchange 
• 11 - Processing: Creation of composite maps (soil classification maps) (out-of-scope)