Home > Public Domain Data > My LANDFIRE Decade

My LANDFIRE Decade

By Randy Swaty, LANDFIRE Ecologist

When we try to pick out anything by itself, we find it hitched to everything else in the universe. — John Muir

The Nature Conservancy program that I work for just hit the ten-year mark, and that birthday got me to thinking. About origin stories. About ideas that are so simple, they’re obvious — but only after the fact. About how great need prompts great action. About how everything is hitched to everything else, once you look closely enough. Landmark birthdays are excellent prompts for us to connect the dots, to find out how we got here, and then look at where we can go.

First, the obvious: Our livelihood – our very lives — depends on grasslands, shrublands and forests, all kinds of living connections that have nothing to do with politics or ownership, that have their own integrity, that recognize no boundaries. Health and hardship spill over and swap across landscapes and watersheds all the time. At the Conservancy, we know that restoring, managing and conserving land and water requires knowledge and insight that extend beyond boundaries as well.  Then, the origin of my program — great need.

LANDFIRE data and project from The Nature Conservancy

LANDFIRE data and project from The Nature Conservancy.

At LANDFIRE’s decade mark, I’m proud to work with great people on a project that spans all 50 states. What I do is connected to my home, my neighborhood, my city, my state and beyond those boundaries. I make models that change the way people manage land, but before LANDFIRE made that possible, we worked with next-to-nothing in terms of scientifically based data. The fact that I did without that foundation makes me all the more appreciative.

In graduate school I studied soil fungi (mycorrhiza-see photo), assuming that U.S. ecosystems had already been mapped and described. Moving from researching microbes to conserving landscapes, I soon learned I was wrong.  My first job with The Nature Conservancy was to help large industrial land managers such as MeadWestvaco and International Paper explore opportunities across the Upper Peninsula of Michigan to conserve wildlife habitat, protect landscape features such as wolf dens, and insure that all ecosystems there had representation.

To do that, we needed a common vegetation dataset that covered both the lands that those managers owned and the lands in-between as well — something that told us, for example, which ecosystems were under- and which were over-represented on the landscape.  Data was either non-existent, or when it did exist, often collected in different ways for different reasons. But a common dataset did not exist. Instead, the situation for restoration in the U.S. prior to LANDFIRE was chaotic. To understand just HOW nuts it was, imagine a grocer stocking shelves using only information provided by a handful of vendors. Not only that, but recording the grocery stock varies — some vendors count individual cans, some count cases, some report by volume (quarts, liters) and others by weight (pounds, kilos). And just because vendors report inventory delivered, that doesn’t mean the totals are correct, or that the grocers who received the deliveries agree with the count.

In the MeadWestvaco and International Paper case, the companies had robust inventories of their own lands, but these datasets were not compatible, and there were no data for the private non-industrial lands. We could either compare cases to cans or make huge assumptions.

Making the ‘Encyclopedia of Ecosystems’

Then I heard about LANDFIRE. The idea was the brainchild of great scientific minds at The Nature Conservancy and federal agencies, and was envisioned as a suite of tools to support land management efforts that would reduce wildfire risk. I joined up as fast as I could, because it was not only the answer to my first job’s immediate problem, but I could see LANDFIRE’s huge potential to be beneficial to conservation and restoration in situations beyond fire as well.

The Conservancy’s first major role in the LANDFIRE project was to describe how all 1,800+ ecosystems in the U.S. looked and worked when functioning “naturally,” i.e., before invasives, fire suppression or large-scale logging.  The result was the first national “Encyclopedia of Ecosystems,” and it was initially used to create a dataset called “Vegetation Departure” that compared current conditions for these ecosystems to the “natural” or “reference” conditions.

Vegetation Departure has been immensely significant to the cause of conservation. For instance, it informed the creation in 2000 of the U.S. National Fire Plan — a long-term national strategy for reducing the catastrophic impacts of wildfires. It also continues to provide conservationists targets for their restoration work.

The Pressure Cooker of Creating Reference Condition Info

Creation of these reference conditions was a wild ride, starting with the sheer volume of information.  Working with more than 700 experts via 40+ workshops, 35+ WebExes, and innumerable phone calls and individual visits, the six-person Conservancy LANDFIRE team assembled, wrote and delivered seven ecosystem descriptions and models each week — 100-300 pages — for 183 weeks running.

The pressure was on: a number of important products (such as the map of these ecosystems and their associated fire regimes) were relying on fast delivery of the information, and every bit of it had to be peer-reviewed and checked for accuracy.  Being late or wrong threw off the whole process. In the end of the first phase, we had an amazing record, delivering “final” or at the least “workable” drafts on schedule and within budget every time.

On the flip side, people were suddenly jockeying to sit next to me, a budding ecologist, at meals during my first LANDFIRE workshop for experts. I wondered what was going on until I learned that the outcomes of our models and descriptions had important budget implications for these managers.

But LANDFIRE’s rigorous system of workshops, peer review, QA/QC and internal review gave us a strong scientific buffer from the pressure we all felt. Additionally, our models were and are informed by literature review, local datasets and general ecological principles. At last, grocers, vendors, inventories and deliveries were all on the same page, and data sheets could be balanced with a high degree of accuracy and agreement.

Mapping Bighorn Sheep Viability to Pollinator Habitat and More

The models and descriptions the LANDFIRE team developed not only fed into the Vegetation Departure dataset, but also contributed to building other important ecological datasets, including three for historic fire regimes and the current data showing the developmental stages of each ecosystem in the United States.

These datasets paint a picture of the entire landscape. They are not only beautiful, but allow conservationists to understand what they are dealing with. For example, the current data has allowed agency, academic and NGO partners to better monitor conditions along the Appalachian Trail — a huge area covering many ownerships and political boundaries (see LANDFIRE data in Appalachian Trail Mapping Viewer). LANDFIRE data spans them all.

Our colleagues at the U.S. Forest Service and U.S. Geological Survey then took our work and turned it into a staggering output of maps — 2.43 billion acres mapped in total (that’s 44,000 satellite images processed), including 25 spatial datasets, each covering the United States. A visit to our WHAM! (Web Hosted Applications Map) offers a snapshot of some of our favorite LANDFIRE data uses, ranging from understanding bighorn sheep viability in Idaho to mapping wildland fire potential for the entire country to understanding wildland habitat value for pollinators in California.

The bottom line: the Conservancy believes that conservation must be practiced within context. It’s not just about special plants, wildlife and services that nature might provide in a particular place, but how they fit into the entire landscape and how all the activities on that landscape impact its ecological function. LANDFIRE products have and still are enabling that approach.

While the process was stressful for all of us, I can’t help but think of those crazy early days as rewarding. We were doing something that had never been done before. Along the way we forged great friendships and learned a lot about ecology and ourselves.

Data + Maps = Collaboration

LANDFIRE’s work didn’t end with that first great push. All this great data doesn’t sell or explain itself, so the Conservancy’s LANDFIRE team works hard to promote appropriate and innovative uses for LANDFIRE products that also have conservation benefits. For example, LANDFIRE recently has filled data gaps for forest restoration in Colorado’s Upper Monument Creek (UMC), a high-priority landscape for conservation within the Pike National Forest that has also experienced some severe and expensive wildfires such as the infamous “Waldo Canyon Fire” of 2012.

After that fire, the UMC Landscape Restoration Initiative was launched to accelerate the pace of forest restoration through data-informed prioritization of “what to do where.”

—–

Editor’s Note:  This week’s post is guest written by The Nature Conservancy’s Landfire team, which includes Kori Blankenship, Sarah Hagen, Randy Swaty, Kim Hall, Jeannie Patton, and Jim Smith. The Landfire team is focused on data, models, and tools developed to support applications, land management and planning for biodiversity conservation. If you would like to guest write for the Spatial Reserves blog about geospatial data, use the About the Authors section and contact one of us about your topic.

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: