Monarthrum lobellum Wood 2007  


Show Images   Images: Displaying 1 to 8 of 24 Go to information summary   Go to distribution map  Go to table of records   



Show Summary   Summary of Information Go to images  Go to distribution map   Go to table of records   


SYNONYMY


Taxonomic Comments.   Listed as Monarthrum lobatum by Noguera & Atkinson (1994: 466), subsequently described as new by Wood.


  • Monarthrum lobatum Noguera & Atkinson & not Ferrari 1990. Ann. Ent. Soc. Amer. 83(3): 466
  • Monarthrum lobellum Wood 2007. M.L. Bean Life Sci. Mus.: 737

DISTRIBUTION.

Numbers in parentheses after each geographic unit are the number of distinct collection events in the database for that unit. For exotic species generally only countries are listed for localities outside the New World. For further information on published sources of distribution, check the REFERENCES section.


Distribution Comments.   Known only from the type locality near Xalapa.


  • North America (3)
    México (3): Veracruz (3);


HOSTS

Numbers in parentheses after each host family, genus, or collection method are the number of distinct collection events in the database for that host or method.


  • No host information (1);
  • Lauraceae (1): Persea (1): americana (1);
  • Leguminosae (1) Leucaena (1): pulverulenta (1);


REFERENCES

The following are important recent monographs, catalogs, and supplements to catalogs that refer to this species. The specific page on which the reference is made is shown in pink at the end of the reference. In the case of Wood (1982) and Wood & Bright (1992) clicking on the reference page will link to a digital version of the work in question.


  • Wood, S.L. 2007. Bark and ambrosia beetles of South America (Coleoptera: Scolytidae). Monte L. Bean Sci. Mus.,Provo, Utah. 900 pp. [737]. (data capture complete)
  • 503 Service Unavailable

    Service Unavailable

    The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

    Additionally, a 503 Service Unavailable error was encountered while trying to use an ErrorDocument to handle the request.