OSR aerial

Oilseed Rape is the most widely grown break crop in the UK. The seed is crushed to produce vegetable oil and the remaining rapeseed meal is a high protein animal feed. 

Share resources and initiatives related to OSR here

Related Organisations

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

Connected Content

Pollen beetles (Meligethes aeneus) are prevalent during Spring and Summer months and are a significant pest of European oilseed rape.  

The major commodity crops in the UK are wheat, barley, oilseed rape, field beans, sugar beet and potatoes, but around half of agricultural land grows grass.   

Rapid crop disease detection. SwiftDetect can reveal the level of disease in your crop even in the latent period, with results in 1 business day.

The AHDB Recommended Lists for cereals and oilseeds (RL) publications and resources provide information on yield and quality performance, agronomic features and market options to assist with variety selection. The RL is updated annually with the latest update for 2023/24 being published on 28th November 2022. The latest lists can be accessed online here.

The Claydon Opti-Till® System, is a holistic approach to crop establishment which delivers consistent, high yielding crops at low cost, providing maximum profitability. At the centre of Opti-Till® Seed Drilling System is the Claydon direct strip Hybrid drill, with its unique leading tine technology.

Arable crops in the UK make up just under half of the farmed area (3.9M ha out of 9M ha)

The Cabbage Stem Flea Beetle (CSFB)  Psylliodes chrysocephala is a key pest on OSR in the UK and across the EU. They are specialist herbivores of plants in the crucifer's family.

At the root of all the best seed varieties.

DSV has been established in the UK for over 40 years with an exemplary track record of providing the best seed for many popular agricultural crops including oilseed rape, grasses, winter wheat, barley, maize, cover crops, lupins and linseed.

Light leaf spot (LLS) is a disease of oilseed rape and some vegetable brassicas, caused by the fungus, Pyrenopeziza brassicae. This major foliar pathogen is notoriously difficult to identify with an airborne polycyclic lifecycle – capable of several infection cycles a season, making it hard to control as reinfection is constantly occurring. Severity can be suppressed through monitoring, cultural controls, and targeted fungicide applications.

Oilseed rape diseases can be caused by a variety of factors, including fungal, bacterial or viral infections, pests and insects, and environmental stress.

Establishment in Oilseed Rape key - this extension to the Oilseed YEN aims to encourage growers to share what works in successfully establishing OSR crops, with a 'Beauty Contest' to make it fun. 

The encyclopedia of oilseed rape diseases is a guide that was created by ADAS and BASF to help growers identify and understand diseases of OSR. As well as highlight emerging threats such as Verticillium wilt and raise awareness of other economically damaging diseases. 

AHDB Project PR623 - Integrated pest management of cabbage stem flea beetle in oilseed

The AHDB Recommended Lists for cereals and oilseeds (RL) publications and resources provide infor

Leaf disease may have been the least of oilseed rape growers’ problems recently but remain a pote

Phoma stem canker is a damaging disease of oilseed rape (Brassica napus) that causes annual yield

Five organic farmers in North East Scotland have launched a pilot project with a comm

The Oilseed YEN network is striving to help the whole industry to successfully grow Oilseed rape (OSR) and Linseed from start to finish – providing a better outlook for both crops into the future. 

Oilseeds plants are plants that containing seeds or fruits with a high level of oils and other food fat, used as an energy reserve (Samouco, 1998).

At present, we are leaders in the spring field bean market, including varieties such as Lynx, Vertigo, Fanfare and newer varieties including Yukon, Macho and Victus. We also have competitive oilseed rape varieties, for example Clubroot resistant varieties Crome and Croozer, HEAR OSR varieties including Resort and Ergo, all of which help the UK farmer to maximise their yield.  

Corteva is a global R&D focused agribusiness

A TOOLKIT FOR BREEDING RESISTANCE TO ADULT AND LARVAL HERBIVORY BY THE CABBAGE STEM FLEA BEETLE. BBSRC Industrial Partnership project led by Rachel Wells at JIC looking to breed oilseed rape with resistance to CSFB.

The Defra Pest and Disease survey has been running for approximately 50 years and monitors endemic pests and diseases in winter wheat and winter oilseed rape, along with accompanying information about agronomic practice and pesticide inputs to the crop.

Phoma leaf spot and stem canker is one of the most damaging diseases in oilseed rape, caused by two closely related fungal pathogens: Leptosphaeria maculans (Plenodomus lingam) and L. biglobosa (P. biglobosus).

Verticillium stem stripe is a challenge to identify, especially when other diseases are present. However, because of a lack of chemical control, it is important to locate high-risk fields, so rotational strategies can be adapted.

This guide outlines oilseed rape’s key growth stages and can provide a foundation for management.

Several diseases affect oilseed rape. However, it is possible to suppress the risk of economic damage by combining non-chemical and chemical approaches.

From Crop Action Feb 2022: Sulphur is an essential plant nutrient and

AHDB fungicide performance work provides high-quality, independent information on the efficacy of

Project report from FERA (James Rainford, Glyn Jones, Roy Macarthur & David Garthwaite) for D

https://twitter.com/sarahkendall10/status/1488976013824512012

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.