Back to the Table of Contents
4.2 Polygon Data for Additional Interpretations
Ecosystem mapping projects often focus on specific topics such as wildlife
habitat suitability or forest site productivity. Ecological interpretations
for such projects may require information about attributes not on the core
attribute list. For example, information about tree crown closure,
stand composition modifiers, and site disturbance may be required
to rate habitat capability and suitability for certain wildlife species.
These attributes would therefore have to be included in the database so
that the ecosystem map could be interpreted adequately. A different data
set (including soil and humus form attributes) would be required
to determine forest site sensitivity.
Additional attributes that may be useful to enhance specific interpretations
are presented in Table 4.2. The attributes are listed below the column heading
for each particular type of interpretation. For example, detailed interpretations
for site productivity may require information about some, or all,
of the additional attributes listed under that column heading. Wildlife
suitability and capability interpretive mapping will require a separate
set of data attributes, and each species may even require different attributes.
In most cases, more than one management interpretation will be required to meet a project's objectives.
Careful planning at the outset will ensure that all necessary data attributes
are collected to meet these requirements.
The lists presented in Table 4.2 provide guidelines only. An initial step
in every mapping project should be to determine the desired uses of an ecological
map and the interpretations required. Data attributes for specific projects
should be worked out with the client and other users at the early project
planning stages. Ecological mappers can choose to collect (in conjunction
with the core polygon information) data for an entire subject area (e.g.,
forest management), or only data associated with a specific interpretation
(e.g., forest site sensitivity). The data requirements should always be
determined by the scope and objectives of the project.
Table 4.2 shows only a sample of potential management interpretations. The
attributes included are based on our existing knowledge and understanding
of ecosystem complexities. Required data attributes may also vary by region,
locality, or, in the case of wildlife, by the particular species of interest.
Other forestry interpretations not listed here might be pest susceptibility
or potential growth-limiting factors for individual tree species. As mentioned
above, selected wildlife species or species groups may also necessitate
the collecting of data attributes not listed (e.g., arboreal lichen abundance,
a significant forage requirement for caribou in certain areas). Other attributes
and interpretations will undoubtedly be considered as we increase our knowledge
of biodiversity and ecosystem dynamics.
| Table 4.1 | Core polygon
attributes required for terrestrial ecosystem mapping |
Project- or Mapsheet-Specific Attributes - repeated for all polygons
Project name
Ecosystem mapper
Terrain mapper
Survey intensity level
Polygon-Specific Attributes - unique for each polygon
Record one
of each of the following elements or classes per polygon:
Mapsheet number
Polygon number
Data source
Ecosection unit
Biogeoclimatic unit (zone
and subzone; variant and phase required if present)
Geomorphological processes (when present)
Soil drainages
Record up to three ecosystem and/or terrain units per polygon (see Figure
3.8):
Ecosystem attributes
- Decile
- Site series
- Site modifier(s)
- Structural stage
Terrain attributes
- Decile
- Terrain texture (optional but should be done where possible; record
up to three for each component)
- Surficial material (record one for each component; could include a
surficial subtype)
- Qualifiers (when present, record one for each component)
- Surface expression (record up to three for each component)
| Table 4.2 |
Possible
Terrestrial Ecosystem Mapping interpretations and the associated attributes |
[Back to TOC] [Previous] [Next]