27.12.2014 Views

Ohio subset of Plant Communities of the Midwest ... - NatureServe

Ohio subset of Plant Communities of the Midwest ... - NatureServe

Ohio subset of Plant Communities of the Midwest ... - NatureServe

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

− The USFS (U.S. Forest Service) Ecoregions field gives information on <strong>the</strong> presumed pre-European<br />

settlement distribution <strong>of</strong> <strong>the</strong> type using <strong>the</strong> province, section, and subsection levels <strong>of</strong> <strong>the</strong> U.S.<br />

Forest Service ECOMAP (Bailey et al. 1994, Keys et al. 1995). A map showing <strong>the</strong> province and<br />

section level units is provided in Plate 11 <strong>of</strong> <strong>the</strong> main report.<br />

− The Conservation Regions field provides <strong>the</strong> presumed pre-European settlement distribution using<br />

codes for <strong>the</strong> ecoregional units used by The Nature Conservancy’s ecoregional conservation planning<br />

teams (TNC 1997). These units are based on <strong>the</strong> U.S. Forest Service map but are grouped to facilitate<br />

conservation planning across <strong>the</strong> country. A map showing <strong>the</strong> Conservancy’s ecoregions and codes is<br />

provided in Plate 12 <strong>of</strong> <strong>the</strong> main report.<br />

In <strong>the</strong> above two fields, each ecoregion is followed by a colon and a confidence level code.<br />

Confidence levels are as follows:<br />

C = Confident: > 95% certain that <strong>the</strong> type occurs in <strong>the</strong> specified ecoregion.<br />

P = Probable: 80-95% certain that <strong>the</strong> type occurs in <strong>the</strong> specified ecoregion.<br />

= Questionable: 10-80% certain that <strong>the</strong> type occurs in <strong>the</strong> specified ecoregion.<br />

X = Extirpated/presumed extirpated from <strong>the</strong> specified ecoregion.<br />

For example, 47:C in <strong>the</strong> Conservation Regions field means that <strong>the</strong> association confidently occurs in<br />

<strong>the</strong> Conservancy’s ecoregion 47. For USFS Ecoregions, <strong>the</strong> first character after <strong>the</strong> colon goes with<br />

<strong>the</strong> Forest Service province, <strong>the</strong> second with <strong>the</strong> Forest Service section within that province, and <strong>the</strong><br />

third with <strong>the</strong> subsection within that section. Thus, “212He:CC” means that <strong>the</strong> association<br />

confidently occurs in province 212, confidently occurs in section 212H, and questionably occurs in<br />

subsection 212He.<br />

− The States and Provinces fields give information on <strong>the</strong> distribution <strong>of</strong> <strong>the</strong> association in <strong>the</strong><br />

United States and Canada. The standard U.S. Postal Code abbreviation is given for each state or<br />

province. Uncertainty about <strong>the</strong> occurrence <strong>of</strong> a type in a state or province is shown as a question<br />

mark after <strong>the</strong> abbreviation.<br />

• The <strong>Midwest</strong> Heritage Synonymy field provides <strong>the</strong> cross-walk between <strong>the</strong> U.S. National Vegetation<br />

Classification (USNVC) association and <strong>the</strong> <strong>Midwest</strong> state name used by a state Natural Heritage<br />

program only for states with a classification that differs from <strong>the</strong> USNVC. Currently Illinois, Indiana,<br />

Michigan, Minnesota, Missouri, Nebraska, <strong>Ohio</strong>, and Wisconsin have such independent state-level<br />

classifications, and <strong>the</strong>ir types are reported in this field. Iowa, Kansas, North Dakota, and South Dakota<br />

use <strong>the</strong> USNVC associations as <strong>the</strong>ir state types, so <strong>the</strong>ir type names are identical to <strong>the</strong> USNVC name<br />

and <strong>the</strong>re is no need to report <strong>the</strong>m here. This field, <strong>the</strong>n, illustrates how, for those states retaining an<br />

independent state-level classification, <strong>the</strong> state types are linked to <strong>the</strong> USNVC through <strong>the</strong> cross-walk.<br />

Uncertainty about <strong>the</strong> occurrence <strong>of</strong> a type in a state or province is shown as a question mark after <strong>the</strong><br />

state abbreviation. The following codes are used to show <strong>the</strong> relationship <strong>of</strong> <strong>the</strong> state type to <strong>the</strong><br />

USNVC type:<br />

+ <strong>the</strong> type is more broadly defined than <strong>the</strong> USNVC type<br />

- <strong>the</strong> type is more finely or narrowly defined than <strong>the</strong> USNVC type<br />

= <strong>the</strong> type is equivalent or identical to <strong>the</strong> USNVC type<br />

I <strong>the</strong> types intersect, but <strong>the</strong> relationship is not simple<br />

A reference for each state classification used by <strong>the</strong> Natural Heritage programs is given in Box 2. It<br />

should be noted that some states are actively revising <strong>the</strong>ir classifications, and <strong>the</strong> names used here may<br />

be more current than those listed in <strong>the</strong> referenced classifications. It is possible to generate reports using<br />

a state or provincial classification as <strong>the</strong> starting point, and to show <strong>the</strong> relation <strong>of</strong> <strong>the</strong> state or provincial<br />

types to <strong>the</strong> USNVC associations. Such reports are available upon request from ABI or individual<br />

programs.<br />

PLANT COMMUNITIES OF THE MIDWEST – 2001. APPENDIX: ASSOCIATION DESCRIPTIONS<br />

3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!