Plant Taxon (Scientific Name) Lookup
Lookup Latin plant names in internationally recognized plant lists either
WCVP (Kew POWO) or WFO.
You are encouraged to experiment with the lookup, it will not change any of your own plant data.
Cannot lookup cultivars, ex: Aeonium 'Kiwi'.
For hybrids use multiplication sign × not x.
The main purpose of 'Taxon Lookup' is to check that your plant names are considered 'accepted' (see below).
In addition lookup can point out any spelling mistakes or syntax errors in your plant names.
The lookup does not find plant names from images, you can use an online application like Google Lens to find the names of plants from photos.
The lookup uses one of two sets of data, WCVP (World Checklist of Vascular Plants) or WFO (World Flora Online).
WCVP is administered by Kew Gardens, new data sets are released about every 4 months.
WFO is administered by a consortium of Taxonomic Experts, new data sets are released about every 6 months.
Although WCVP is considered the standard WFO is offered because there are a few differences between the two.
Both data sets are stored within MOPDB and are optimized for speed.
Each has information for about 1.5 million plants.
In order to stay current MOPDB intends to grab the lists from WCVP and WFO when new ones are released.
Note that neither data set contains cultivars like Aeonium 'Kiwi'.
Whether the lookup should consider upper and lower case when searching.
If you are logged in the default value is taken from your personal settings, see
Settings in the main Help.
When this is checked and a plant name is not found in the authority's data set some alternative suggestions will be made. Depending on the situation making suggestions can make the lookup slower.
If you are logged in the default value for 'Suggestions' is taken from your personal settings, see Settings in the main Help.
The first suggestion stage analyzes the scientific name and breaks it into it's parts - genus, epithet, infra-epithet, etc. Those parts are then run through a spell checker that uses dictionaries built from the authorities' data. Like any spell checker a list of alternative spellings is produced, these alternatives are looked up in the authority's data and any that are found are shown. The number of spellings used depends on the 'Depth' setting.
The next stage looks up just the genus, epithet, and infra-epithet. Connecting terms like 'var.' are ignored which can result in finding plants that have been renamed slightly. A recent renaming trend is to change 'var.' to 'subsp.' this stage will find those.
The following stages use the combinations 'genus + epithet', 'genus + empty epithet', and 'epithet + infra-epithet' to find results.
When using 'Single' mode only 'Scientific Name' will be used to make suggestions and only if an exact match for that 'Scientific Name' is not found.
This setting limits the number of results to show per plant name. It is used in 'Single' mode and when
'Suggestions' are produced. If you are logged in the default is taken from your personal settings, see
Settings in the main Help.
Note that using a higher value will take more time.
'Depth' controls the number of spell checker suggestions to try when a plant name is not found. It is only used when
'Suggestions' is checked. The higher the value the more attempts are made to find the plant name therefore the
longer it will take, although in some circumstances the extra time is negligable. If the name you are looking up has
multiple spelling mistakes raising the value of 'Depth' might produce a hit.
Selecting a Depth value of 10 or more invokes a more verbose spell check mode which can take longer but might
produce more results.
If you are logged in the default value is taken from your personal settings, see
Settings in the main Help.
MOPDB has a notion of comments within a Scientific Name. Comments are removed before looking up the plant name.
There are two types of comment ...
a) A comma and anything after it is considered a comment. Ex: "Aloe arborescens, Yellow form" will be looked up as
just "Aloe arborescens".
b) Parentheses and anything between them is considered a comment. Ex: "Aloe (#2) vera" will be looked up as "Aloe vera".
These can be difficult. There are several different syntax methods to describe hybrids.
Both WCVP and WFO only include interspecific hybrids that have been given a new name, ex: Aloe ×
chludowii which is a named hybrid between Gonialoe variegata and Kumara plicatilis.
MOPDB tries to help with hybrids that follow the forms Genus epithet1 × epithet2 or Genus epithet1 × G. epithet2 by splitting and looking up each species, first Genus epithet1 and then Genus epithet2. That is effective for first crosses (Species × Species) a.k.a. F1, but not for double crosses (F1 × F1) or three way crosses (F1 × Species) or triple crosses (three-way × three-way).
Within the WCVP data there is a field "hybrid_formula" which contains the names of the parents. However WFO data does not have that field and there are only a few plants in WCVP that have it filled in so MOPDB does not use it except to show it in the lookup results.
Intergeneric hybrids are between two different genera, ex: × Gasteraloe is a cross between a Gasteria and an Aloe. They appear in the data under the name given to the cross known as the nothogenus, ex: × Gasteraloe. However there are too many nothogenera for MOPDB to attempt to expand them.
A culltivar is a variation of a species, subspecies, or variety, being created by man and not found in nature.
They can be created by means that include, selection, cross-pollination, and various forms of hybridization.
A cultivar name is written between single quotes, for example 'Sunburst' or 'Tom Thumb'. They are usually in English, not Latin. Cultivars are given names by the growers that create them but those names are not accepted as species by authorities like WCVP and WFO.
MOPDB removes any cultivar name from a taxon before looking it up.
"Taxon Status" is the term used in the data to describe the validity of each plant name.
Each plant in the WCVP data has a status of 'Accepted', 'Artificial Hybrid', 'Illegitimate',
'Invalid', 'Local Biotype', 'Misapplied', 'Orthographic', 'Synonym', or 'Unplaced'.
Each plant in the WFO data has a status of 'Accepted', 'Synonym', or 'Unchecked'.
For the results from 'File' or 'All my plants' lookups MOPDB maps those to 'Accepted', 'Renamed', or 'Not Found'.
If the plant is a cultivar or hybrid 'Accepted' is remapped to 'Cultivar', 'Hybrid', or 'Hybrid cv.' although they are not truly accepted because the plant is only found after either the cultivar part was removed or the hybrid was split into parents. However hybrids that have been given a new name can be truly accepted, ex: Aloe × caesia.
1) Lookups currently do not find scientific plant names that include English, examples: 'Aloe Hybrid' or 'Cereus forbesii monstrose'.
2) Lookups will often not find names with cristata, monstrosa, etc. although they are Latin words the WCVP and WFO
data doesn't always include those forms of a plant, probably because they are just a growth form rather than a
seperate plant.
However 'Suggestions' comes to the rescue; with it enabled further lookups will be made ignoring the extra words.
3) There are plants in WCVP and WFO that have a status of 'Invalid', 'Illegitimate', 'Misapplied', 'Unchecked', or 'Unplaced', one can only assume that they are there because, although incorrect, they have information that needs to be retained. MOPDB also keeps those plants in its lists which can lead to confusion at times. When your lookup only has results with a status being one of the above you can assume the name is not valid. However your lookup might also find a name with a status of 'Accepted' which should be considered valid.
4) It's possible to create filter rules that are impossible to fulfill.
As an obvious example: Genus equal Aloe AND Genus not equal Aloe.
The only solution is don't do that.
See the page on this website Plant Nomenclature Syntax or see the main help section called Plant Scientific Names. Both can also be accessed using help in the main menu.
When a lookup finds a plant with a status of 'Accepted' it is the recommended name to use. Obviously plants you obtained in the past may have been renamed, but it is also possible that you were given the wrong name, nurseries are not always accurate with their names.
The 'accepted' name of a plant is not necessarily either unique or static. Organizations like WCVP and WFO are
attempting to manage lists of the accepted names of all known plants, however they don't always agree.
Now that we have molecular analysis enabling us to see the DNA of plants we are finding there are plants that need to be
moved from their current species or even genus to another, hence they need to be renamed.
When a DNA researcher proposes a rename it has to be agreed by the authorities before they will publish it.
If you have a mind to keep the names of your plants up to date you can run a lookup of all your pants each time MOPDB grabs a new list.
Driven by the results of molecular analysis (DNA), many species have been re-named recently. Name changes have been dubbed with the terms lumping and splitting, used by Charles Darwin back in 1857.
Lumping is when it is found that two plants are actually the same species, resulting in both being given the
same (scientific) name.
Splitting is when it is found that two plants that had been given the same name are different, one of them is
given a different name, possibly an already existing name.
The trend in the early 2020's is towards lumping, perhaps driven by the idea that unless DNA shows differences between
species then they are the same. However there are many folks in plant collection and production who are of the opinion
that lumping has been over-zealous and that DNA analysis is not yet sufficiently advanced to make such decisions.
On the other hand there is an opportunity for DNA analysis to show us when two previously considered different species
are really the same leading to a much needed reduction in the number of names being used.
This error can occur when the list of plants found cannot fit in available memory. The error is fatal meaning the lookup cannot continue. If you get this error use your back button to return to this page and narrow the search criteria.
TBD