Related Organisations

Content below is from across the PEP community and is not necessarily endorsed by Stewards or by PEP

Connected Content

Agriculture now generates vast amounts of data of different types and at different scales. The ownership, access, control, sharing, value, permissioning, intergration, security, safeguarding and sovereignty of this data represent multiple challenges and opportunities for the sector.

We help farmers improve their soil health by enabling them to benchmark their existing soil data.

YEN Zero is a recently established network in the ADAS YEN Family, with the overarching aim of creating a net-zero community. It aims to bring key players from across the agricultural industry together to meet the industry’s target of achieving net zero emissions by 2040.

We deliver transformational projects to drive productivity and boost farming and supply chain businesses. We want the industry to thrive in a rapidly changing world and continue to produce high quality food, maintain our beautiful landscape and leave a legacy for generations to come. 

Soil health has been broken down into measurable parts to help farmers optimise crop and grassland productivity. As part of the Soil Biology and Soil Health Partnership, a project in the AHDB & BBRO GREAT Soils programme, guidance and protocols have been issued to help practitioners benchmark their soils

The number of tools and calculators available can be daunting. None are necessarily right or wrong, the appropriate tool for you depends on the question you are asking.

The standard way to measure and monitor soils has been through soils samples taken to 15-30cm in representative W patterns. A range of technologies are now available commercially and in development to provide higher resolution data across a wider range of metrics. This page provides a space to share and discuss the available and coming tools, services and technologies.

To celebrate 10 years of the YEN, we are hosting a YEN conference that brings together learnings from across our networks. 

Farmers, advisors and researchers working together to understand and improve crop nutrition on-farm

Analysing grain for all 12 nutrients can be an effective tool to improve nutrient management, providing information on crop nutrient status and nutrient offtakes.  It can indicate whether your crops are getting hold of the nutrients they need, or whether you can save on future fertiliser use.

Farm carbon calculator to lower emissions and increase productivity

Introducing Naturestimeline and Tony William Powell. Benchmarking Birds. A Freelance Contractor offering clients bespoke Avian conservation monitoring projects.  

My take on the risks of farming, personal risk appetite, and how access to on-farm an

GrassCheckGB is a grass monitoring project involving 50 dairy, beef and sheep farms.   Growth and quality data is published weekly throughout the growing season

Data & technology for the business of farming.

The Wheat Growth Guide was first published in 1999, following extensive measurement of a range of reference crops in HGCA funded projects. The AHDB Wheat growth guide allows crop progress, structure and final performance to be measured and compared against a series of UK benchmarks. To manage crops effectively, it is important to set targets, assess progress, adjust inputs and monitor success. Our wheat growth guidance outlines the main crop growth stages and components of yield, as well as the opportunities for management.

Farmers Weekly article by Mike Abram exploring four carbon calculators

The SMI Agribusiness Task force makes clear what the private sector can do to make regenerative agriculture a 'no-brainer' for farmers and accellerate its adoption worldwide. 

Calling all agronomists! Sign up for the last few places at Soil Benchmark's event at NIAB on 7th December - hear from Dr Elizabeth Stockdale and join some of the UK's leading agronomists in the discussion on Farm Data and the Future of Agronomy

Mark Topliff, AHDB Lead Analyst – Farm Economics, uses Farmbench data to illustrate how crops

A joint report from Crop Health and Protection (CHAP) and AHDB, that aimed to determine a baselin

Anonymised YEN report from 2021 showing what each YEN entrant recieves for their crop.

Share resources, ideas and experiences on running successful agri-businesses.

Benchmarking is at the core of the YENs and the FarmPEP approach

Farmbench is a website based benchmarking programme.

HESTIA – Harmonized Environmental Storage and Tracking of the Impacts of Agriculture – is an online platform to enable the sharing of food sustainability data in a structured, open source and standardised way. Please visit https://www.hestia.earth for more information.  

An overview of the greenhouse gas costs of cropping, including an analysis of YEN data in lead up to establishing YEN Zero.  Also includes an analysis of the relationship between nitrogen fertiliser, GHG costs, yield, GHG intensity and potential indirect land use change (ILUC) consequences.  

Powerful long-term drivers are increasing both the demand and supply of quantified environmental impact information in food systems. 

YEN Nutrition's Grain analysis & Benchmarking service

Marking a huge advance in improving crop health and nutrition worldwide, the Consortium for Preci

Write whatever you want here - this is the main section. You can add links, add pictures and embed videos. To paste text from elsewhere use CTRL+Shift+V to paste without formatting. Add videos by selecting 'Full HTML' below, copying the 'embed html' from the source page (eg Youtube), clicking 'Source' above and pasting where you want the video to appear.
You can upload an image here. It can be jpg, jpeg, gif or png format.
Upload requirements

You can upload a file here, such as a pdf report, or MS Office documents, Excel spreadsheet or Powerpoint Slides.

Upload requirements
Authors Order
Add Authors here - you can only add them if they already exist on PEP. Just start writing their name then select to add it. To add multiple authors click the 'Add another item' button below.

Please ensure that you have proof-read your content. Pages are not edited further once submitted and will go live immediately.

Configure the meta tags below.

Use tokens to avoid redundant meta data and search engine penalization. For example, a 'keyword' value of "example" will be shown on all content using this configuration, whereas using the [node:field_keywords] automatically inserts the "keywords" values from the current entity (node, term, etc).

Browse available tokens.

Simple meta tags.

The text to display in the title bar of a visitor's web browser when they view this page. This meta tag may also be used as the title of the page when a visitor bookmarks or favorites this page, or as the page title in a search engine result. It is common to append '[site:name]' to the end of this, so the site's name is automatically added. It is recommended that the title is no greater than 55 - 65 characters long, including spaces.
A brief and concise summary of the page's content, preferably 150 characters or less. Where as the description meta tag may be used by search engines to display a snippet about the page in search results, the abstract tag may be used to archive a summary about the page. This meta tag is no longer supported by major search engines.

Meta tags that might not be needed by many sites.

Geo-spatial information in 'latitude; longitude' format, e.g. '50.167958; -97.133185'; see Wikipedia for details.
Geo-spatial information in 'latitude, longitude' format, e.g. '50.167958, -97.133185'; see Wikipedia for details.
Robots
A comma-separated list of keywords about the page. This meta tag is used as an indicator in Google News.
Highlight standout journalism on the web, especially for breaking news; used as an indicator in Google News. Warning: Don't abuse it, to be used a maximum of 7 times per calendar week!
This meta tag communicates with Google. There are currently two directives supported: 'nositelinkssearchbox' to not to show the sitelinks search box, and 'notranslate' to ask Google not to offer a translation of the page. Both options may be added, just separate them with a comma. See meta tags that Google understands for further details.
Used to rate content for audience appropriateness. This tag has little known influence on search engine rankings, but can be used by browsers, browser extensions, and apps. The most common options are general, mature, restricted, 14 years, safe for kids. If you follow the RTA Documentation you should enter RTA-5042-1996-1400-1577-RTA
Indicate to search engines and other page scrapers whether or not links should be followed. See the W3C specifications for further details.
Tell search engines when to index the page again. Very few search engines support this tag, it is more useful to use an XML Sitemap file.
Control when the browser's internal cache of the current page should expire. The date must to be an RFC-1123-compliant date string that is represented in Greenwich Mean Time (GMT), e.g. 'Thu, 01 Sep 2016 00:12:56 GMT'. Set to '0' to stop the page being cached entirely.

The Open Graph meta tags are used to control how Facebook, Pinterest, LinkedIn and other social networking sites interpret the site's content.

The Facebook Sharing Debugger lets you preview how your content will look when it's shared to Facebook and debug any issues with your Open Graph tags.

The URL of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Should not be used if og:image:url is used. Note: if multiple images are added many services (e.g. Facebook) will default to the largest image, not specifically the first one. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The URL of an video which should represent the content. For best results use a source that is at least 1200 x 630 pixels in size, but at least 600 x 316 pixels is a recommended minimum. Object types supported include video.episode, video.movie, video.other, and video.tv_show. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
A alternative version of og:image and has exactly the same requirements; only one needs to be used. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly.
The secure URL (HTTPS) of an image which should represent the content. The image must be at least 200 x 200 pixels in size; 600 x 316 pixels is a recommended minimum size, and for best results use an image least 1200 x 630 pixels in size. Supports PNG, JPEG and GIF formats. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically. This will be able to extract the URL from an image field if the field is configured properly. Any URLs which start with "http://" will be converted to "https://".
The type of image referenced above. Should be either 'image/gif' for a GIF image, 'image/jpeg' for a JPG/JPEG image, or 'image/png' for a PNG image. Note: there should be one value for each image, and having more than there are images may cause problems.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format. Can be the same as the 'Article modification date' tag.
The date this content was last modified, with an optional time value. Needs to be in ISO 8601 format.
The date this content will expire, with an optional time value. Needs to be in ISO 8601 format.

A set of meta tags specially for controlling the summaries displayed when content is shared on Twitter.

Notes:
  • no other fields are required for a Summary card
  • Photo card requires the 'image' field
  • Media player card requires the 'title', 'description', 'media player URL', 'media player width', 'media player height' and 'image' fields,
  • Summary Card with Large Image card requires the 'Summary' field and the 'image' field,
  • Gallery Card requires all the 'Gallery Image' fields,
  • App Card requires the 'iPhone app ID' field, the 'iPad app ID' field and the 'Google Play app ID' field,
  • Product Card requires the 'description' field, the 'image' field, the 'Label 1' field, the 'Data 1' field, the 'Label 2' field and the 'Data 2' field.
A description that concisely summarizes the content of the page, as appropriate for presentation within a Tweet. Do not re-use the title text as the description, or use this field to describe the general services provided by the website. The string will be truncated, by Twitter, at the word to 200 characters.
By default Twitter tracks visitors when a tweet is embedded on a page using the official APIs. Setting this to 'on' will stop Twitter from tracking visitors.
The URL to a unique image representing the content of the page. Do not use a generic image such as your website logo, author photo, or other image that spans multiple pages. Images larger than 120x120px will be resized and cropped square based on longest dimension. Images smaller than 60x60px will not be shown. If the 'type' is set to Photo then the image must be at least 280x150px. This will be able to extract the URL from an image field if the field is configured properly.
The MIME type for the media contained in the stream URL, as defined by RFC 4337.