Error message

  • Notice: Undefined variable: node in include() (line 18 of /Applications/MAMP/htdocs/sites/all/themes/framework/page.tpl.php).
  • Notice: Undefined variable: tags in include() (line 32 of /Applications/MAMP/htdocs/sites/all/themes/framework/page.tpl.php).
  • Notice: Undefined variable: tags in include() (line 61 of /Applications/MAMP/htdocs/sites/all/themes/framework/page.tpl.php).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).

You are here

  > Speakers > Olander
Lydia Olander
Lydia Olander
Director, Ecosystem Services Program
Nicholas Institute

Lydia Olander is Director of the Ecosystem Services Program at the Nicholas Institute. She has worked on a range of issues for the Institute, including national energy and transportation policy and their linkages with climate change and climate policy; oil and energy security; clarifying new science relevant to climate change policy for decision makers; and water issues for a rapidly developing North Carolina. Currently she is focused on developing the Institute’s expanding initiative on ecosystem services and working on the burgeoning multinational effort to add avoided deforestation into future international climate agreements. Olander joined the Nicholas Institute after spending a year as an AAAS Congressional Science and Technology Fellow working with Sen. Joseph Lieberman on environmental and energy issues. Before moving to Washington, D.C., she was a researcher with the Carnegie Institution of Washington’s Department of Global Ecology, where she studied the biogeochemical impacts of logging in the Brazilian Amazon and worked with new techniques to extrapolate impacts regionally using remote sensing. She received her PhD from Stanford University, where she studied nutrient cycling in tropical forests, and has a master’s degree in forest science from Yale University. She has published in professional journals, including Ecosystems, Biogeochemistry, Soil Biology and Biochemistry, Forest Ecology and Management, and Earth Interactions.

New Ground: New Protocol Types and Offset Supply

Published by anongost on January 12, 2012 - 5:49pm

Although regulated entities in California will be able to use carbon offsets to meet only eight percent of their compliance obligation under cap-and-trade, many observers are concerned that offsets will be in short supply, especially after 2014. Amid these concerns, there is much speculation around possible domestic project types that California and WCI may add to their programs to boost supply. This session will examine the prospects for including additional offset types in the California and WCI programs and their potential for addressing supply concerns.

1:30pm
3:00pm
Program Path Text: 
Path 2: Offsets and Other Mitigation