Edit History
Filed as Ononis viscosa L. subsp. viscosa [family FABACEAE]
Date Updated: 19 January 2020
Herbarium
Botanische Staatssammlung München (M), M0232974
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Martius, C.F.P. von, #s.n.
Collection Date
1817
Country
Unknown (Unknown)
Identifications
Ononis viscosa L. subsp. viscosa [family FABACEAE] (stored under name); Verified by Širjaev, G.I.
Ononis viscosa L. [family FABACEAE]
Notes
Ononis viscosa var. floribus quam calyces majoribus, foliis rotundioribus.
Pages
1
Data last modified
2015-12-02
Date Updated: 10 April 2019
Herbarium
Botanische Staatssammlung München (M), M0232974
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Martius, C.F.P. von, #s.n.
Collection Date
1817
Country
Unknown (Unknown)
Identifications
Ononis viscosa subsp. viscosa L. [family FABACEAE] (stored under name); Verified by Širjaev, G.I.
Ononis viscosa L. [family FABACEAE]
Notes
Ononis viscosa var. floribus quam calyces majoribus, foliis rotundioribus.
Pages
1
Data last modified
2015-12-02
Date Updated: 4 February 2016
Herbarium
Botanische Staatssammlung München (M), M0232974
Collection
Herbarium Specimens
Resource Type
Specimens
Collector
Martius, C.F.P. von, #s.n.
Collection Date
1817
Country
Unknown (Unknown)
Identifications
Ononis viscosa subsp. viscosa L. [family FABACEAE] (stored under name); Verified by Širjaev, G.I.
Ononis viscosa L. [family FABACEAE]
Notes
Ononis viscosa var. floribus quam calyces majoribus, foliis rotundioribus.
Pages
1
Data last modified
2015-12-02
╳
We're sorry. You don't appear to have permission to access the item.
Full access to these resources typically requires affiliation with a partnering organization. (For example, researchers are often granted access through their affiliation with a university library.)
If you have an institutional affiliation that provides you access, try logging in via your institution
Have access with an individual account? Login here
If you would like to learn more about access options or believe you received this message in error, please contact us.