Peat Irrigation Ditches

Lowland agricultural peatlands are among the UK’s most productive soils, but their drainage for farming contributes significantly to greenhouse gas emissions and long-term soil degradation. These areas are increasingly the focus of research into sustainable land management practices that maintain productivity while reducing environmental impact. 

Wetter farming raises the water table on drained lowland peat to reduce greenhouse gas emissions whilst keeping land in agricultural production. Drainage causes peat to oxidise and decompose, releasing greenhouse gases and gradually destroying the soil itself; potentially threatening the future of farming on these valuable soils. 

Wetter farming typically maintains water tables between 31–50 cm below the surface—shallower than conventional systems, but not as wet as paludiculture, which usually operates at 10–30 cm. This approach allows farmers to grow certain conventional crops while lowering emissions. Crops currently being trialled include celery, Chinese leaf, and lettuce, which show potential under these wetter conditions. 

Wetter farming may be implemented at the field or farm scale, but involves active water level management to maintain water tables. It is also being explored as part of a broader mosaic approach—a concept that combines different land uses, such as regenerative agriculture, paludiculture, and restoration, to reflect the varied conditions and constraints of lowland peat landscapes. 

Support is currently available through Countryside Stewardship (Higher Tier), with payment options for maintaining water tables at either 10–30 cm or 31–50 cm depths. This provides farmers with viable, tiered options for transitioning towards lower-emission land management. 

Peat Diagram

https://assets.publishing.service.gov.uk/media/649d6fe1bb13dc0012b2e349/lowland-agricultural-peat-task-force-chairs-report.pdf  

Resources: 

Lowland Agricultural Peat Task Force report: https://assets.publishing.service.gov.uk/media/649d6fe1bb13dc0012b2e349/lowland-agricultural-peat-task-force-chairs-report.pdf  

IUCN UK Peatland Programme: 

https://www.iucn-uk-peatlandprogramme.org/  

Fenland soil: 

https://www.fenlandsoil.org/  

Related Organisations

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

Connected Content

Lowland Agricultural Peat

Lowland agricultural peats represent some of the most productive farming areas in the UK, supporting high-value horticultural crops and key staples such as wheat, potatoes, and sugar beet.

Paludiculture

Paludiculture is the practice of growing crops in wetland conditions, typically with a water table maintained at 10–30 cm below the soil surface.

Managing for a sustainable future: Cropping systems on drained lowland peat

Niab has been working with WWF and Fenland Soil to explore and support more sustainable cropping systems on lowland peat soils. This work follows up work completed in 2023 to explore the future of vegetable production on lowland peat.

About text formats
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
File

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 will go to an admin for approval before going live.

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.
Basic tags

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.
Advanced

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.
Sets a cookie on the visitor's browser. Can be in either NAME=VALUE format, or a more verbose format including the path and expiration date; see the link for full details on the syntax.
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.
Open Graph

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.
Links an article to an author's Facebook profile, should be either URLs to the author's profile page or their Facebook profile IDs. Multiple values may be used, separated by a comma. Note: Tokens that return multiple values will be handled automatically.
The date this content was published on, with an optional time value. Needs to be in ISO 8601 format.
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.
Twitter Cards

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.