Will Ecuador benefit from wild tomato genes?

A tweet alerted me to a story about the value of genes in crop wild relatives.

The source headline is “Galapagos tomato provides key to making cultivated tomatoes resistant to whitefly,” and though it reads like a press release 1 I have so far been unable to run down the original. I did, however, locate the event of note.

By now, Syarifin Firdaus should have successfully defended his graduate thesis on Whitefly Resistance In Tomato and Hot Pepper, which was due to take place today and which I imagine created all the interest.

My interest stemmed from the Twitterer’s question: “Will Ecuador benefit?”

The blurb for Firdaus’ talk makes it clear that after sampling almost 100 genebank accessions, wild Solanum galapagense had the strongest resistance and this seemed to be down to a single gene on chromosome 2. But it also pointed out that resistance was found in two other wild Solanum species, and in several Capsicums.

With these results, introduction of the resistance into modern tomato varieties is feasible and within a few years the first commercial, resistant tomato cultivars are expected on the market.

And that is a good thing not so much because whitefly damage the crop, but because they transmit virus diseases that are really harmful.

The release, which lists all the private sector companies involved in the research, strongly suggests that it will be genes from S. galapagense that will be bred into commercial varieties “within two years”. It also says that “resistance was also found in China, Indonesia and Thailand,” presumably in local tomato varieties rather than wild relatives.

Will Ecuador benefit? I seriously doubt it. Other wild relatives from Ecuador (and elsewhere) have already donated genes worth millions of dollars to the tomato industry, and no precedent has been set.

Should Ecuador benefit? Hard to see why. It isn’t as if S. galapagense (which until relatively recently was treated as a form of S. cheesmaniae, a well-established source of good tomato genes) has been maintained by farmers since time immemorial.

Best yet, tomato isn’t even listed on Annex 1 of the International Treaty on Plant Genetic Resources for Food and Agriculture. Solanum section tuberosa, sure; Solanum melongena, you bet. But Solanum lycopersicum and its wild relatives, outta luck.

Of course, the genetic resource in question might just be covered by the Convention on Biological Diversity, which offers Ecuador and its supporters a glimmer of hope, but I wouldn’t hold my breath.

What I really want to know is why S. galapagense is resistant? What are the insect pests on the Galapagos that exerted such strong selection pressure? Perhaps @WayOfThePanda can find out.

IUCN and Microsoft map threats to biodiversity

“We’re building an application that allows people to map those threats spatially,” Joppa explains. “We’re trying to provide a repository of evidence for threats to species.”

Lucas Joppa is talking about a collaboration between Microsoft and IUCN to map threats to biodiversity. Worth keeping an eye on. But I wonder if they’ll consider agrobiodiversity too. If so, we have some ideas here at the blog. Anyway, presumably the thing will link up with GeoCAT in some clever way.

LATER: And also link to this? Or at least suck in the data?

Brainfood: Wild soybean, Leafy vegetables collection gaps, Banana drought tolerance screening, Chinese soybean breeding, Malagasy coffee collections, Bacteria on beans

Geospatial Conservation Assessment Tool put through its paces

A random tweet from Stefano Padulosi at the big IUCN conference in Korea alerted me to the existence of something called GeoCAT. Funny how you can follow a topic assiduously and still miss important stuff and then come across it entirely by chance. Anyway, GeoCAT is an online tool developed by Kew and Vizzuality, with support from IUCN and others, that “performs rapid geospatial analysis for Red List assessment.” 2

It all starts by providing some species occurrence data. You can import data from GBIF or, interestingly, Flickr. Or you can upload your own data. Or you can add or edit points on the map itself. All three options seem to work fine. Then you have to click on a little button labelled “Enables EOO/AOO.” It took me some time to figure that out. What that does is it uses the occurrence data to calculate two things: Extent of Occurrence (EOO) and Area of Occupancy (AOO). “These two measures are the foundation of the ‘B’ criterion of the IUCN Red List system.” I’ll let Wikipedia define them:

The EOO can best be thought of as the minimum convex polygon encompassing all known normal occurrences of a particular species, and is the measure of range most commonly found in field guides. The AOO is the subset of the EOO where the species actually occurs. In essence, the AOO acknowledges that there are holes in the distribution of a species within its EOO, and attempts to correct for these vacancies. A common way to describe the AOO of a species is to divide the study region into a matrix of cells and record if the species is present in or absent from each cell.

That done, you click on “Print complete report” and that opens another browser tab which has a map of the occurrences, the EOO and AOO figures, and a preliminary assessment of threat, according to the IUCN system. What it doesn’t have, is a reference to what species you’re dealing with, but the thing is still in Beta, they’ll work such things out in due course. You can also download the results for use in Google Earth, from whence I derived the following, for Cicer judaicum, as it happens.

No, I don’t know if that lone record off to the east is valid, but fear not, if you think it’s suspect, you can easily edit it out. Not bad. Not bad at all.

Nibbles: IUCN conference tweep, ICARDA move, Adaptation stories, Branding and market chains, Tree farming