Skip to main content

Encyclopedia of Life - by the World's Leading Scientists

An epic effort to promote biodiversity and document all 1.8 million named species on the planet.

When completed, http://www.eol.org will serve as a global biodiversity tool, providing scientists, policymakers, students, and citizens information they need to discover and protect the planet and encourage learning and conservation.

The Encyclopedia of Life is a collaborative scientific effort led by the Field Museum of Natural History, Harvard University, Marine Biological Laboratory, Missouri Botanical Garden, Smithsonian Institution, and Biodiversity Heritage Library, a consortium including the core institutions and also the American Museum of Natural History (New York), Natural History Museum (London), New York Botanical Garden, and Royal Botanic Gardens (Kew).
clipped from www.eol.org
Connected Life: Encyclopedia of Life
clipped from www.eol.org

"Imagine an electronic page for each species of organism on Earth, available everywhere by single access on command." - Edward O. Wilson



The Encyclopedia of Life (EOL) is an ambitious project to organize and make available via the Internet virtually all information about life present on Earth.
At its heart lies a series of Web sites—one for each of the approximately 1.8 million known species.
Each site is constantly evolving and features dynamically synthesized content ranging from historical literature and biological descriptions to stunning images, videos and distribution maps. Join us as we explore the richness of Earth’s biodiversity!
clipped from www.eol.org
Amanita phalloides (Vaill. ex Fr.) Link 1833

Death Cap Mushroom

Anolis carolinensis VOIGT 1832

Green anole

Aedes aegypti (Linnaeus, 1762)

Yellow fever mosquito

Falco peregrinus Tunstall, 1771

Peregrine falcon

Hecastocleis shockleyi Gray

Prickleleaf

Jalmenus evagoras Donovan 1805

Imperial Blue Butterfly

Solanum tuberosum L.

Potato

Theobroma cacao L.

Cacao

Chromis abyssus Pyle, Earle & Greene, 2008

Deep Blue Chromis

Catharanthus roseus (L.) G. Don

Madagascar periwinkle

clipped from www.eol.org
A conversation with Chris Anderson
The Encyclopedia of Life, video demo
clipped from www.ted.com

Talks
E.O. Wilson: TED Prize wish: Help build the Encyclopedia of Life

clipped from video.msn.com
advertisement
 blog it

Comments

Popular posts from this blog

Dotnet, .Net 3.5, 2.0, C# Interview Questions

Few questions on dotnet, C# 2.0, 3.5 On Object oriented concepts 1)What is inheritance with e.g 2)What is polymorphism -function overloading -Function overriding -virtual keyword use -Static keyword and use -Abstract classes -Interface -Object 3)What is threading and how do we use in realtime application(cognizant) 4)What is threadpooling, lock, monitor(write code sample) 5)Architecture of current project 6)Session state, diffrent types of state management. 7)What is Application_Start, how it works. 8)Type of authentication in asp.net 9)How to configure ASP.NET application. 10) What is Impersonation. 11) What is WebService, WSDL, UDDI, Discovery, asmx files. 12) How to implement WebService and use it. 13) When to use WebServices. 14) WPF, how to implement(BOA) 15) Testing concvepts. 16) Test attributes 17) Flow of Automation Test Method execution 18) Features of dotnet 3.5 19) CLR, garbage collection 20) Finally block 21) Manifest, Metadata, MSIL 22) Assemblies, Type of assemblies, str...

Remote debugging for ARM target board

Remote debugging for ARM target board With GDB one can both trace and modify code and data flow, and otherwise analyze the behavior of code, without explicitly changing any of it. Rather than run a full-blown instance of GDB on the target platform, you can use GDBserver , a program that lets you run GDB on a different machine than the one on which your program is running. The advantage of using GDBserver is that it needs just a fraction of the target resources that GDB consumes, because it implements only the low-level functionality of the debugger -- namely setting breakpoints and accessing the target processor registers and read/write application memory. GDBserver takes control of the application being debugged, and then waits for instructions from a remote instance of GDB running on a development workstation. Remote target needs to have debugging stub (gdbserver), The gdbserver is also referred to as the 'stub' and must be cross-compiled for that targ...