# SUGGESTED STEPS IN ORGANIZING VEGETATION MAPPING & CLASSIFICATION PROJECTS (prepared by Angela Evenden, Northern Colorado Plateau Network)

+-------------+---------------------------------------------+----------+
| **STEP 1:   |                                             |          |
| PROJECT     |                                             |          |
| SCOPING AND |                                             |          |
| PLANNING**  |                                             |          |
+-------------+---------------------------------------------+----------+
| The         |                                             |          |
| important   |                                             |          |
| first step  |                                             |          |
| is to       |                                             |          |
| formulate   |                                             |          |
| and         |                                             |          |
| organize    |                                             |          |
| the         |                                             |          |
| vegetation  |                                             |          |
| mapping     |                                             |          |
| project at  |                                             |          |
| either a    |                                             |          |
| single park |                                             |          |
| or          |                                             |          |
| multi-park  |                                             |          |
| level. This |                                             |          |
| involves    |                                             |          |
| bringing    |                                             |          |
| together    |                                             |          |
| park and    |                                             |          |
| network     |                                             |          |
| staff,      |                                             |          |
| potential   |                                             |          |
| partners    |                                             |          |
| and         |                                             |          |
| cooperators |                                             |          |
| to          |                                             |          |
| determine   |                                             |          |
| the scope   |                                             |          |
| and details |                                             |          |
| of the      |                                             |          |
| anticipated |                                             |          |
| mapping     |                                             |          |
| project(s). |                                             |          |
| WASO NPS    |                                             |          |
| Veg Map     |                                             |          |
| Program     |                                             |          |
| Staff are   |                                             |          |
| available   |                                             |          |
| to provide  |                                             |          |
| guidance    |                                             |          |
| during the  |                                             |          |
| scoping     |                                             |          |
| process.    |                                             |          |
| Suggested   |                                             |          |
| topics to   |                                             |          |
| address     |                                             |          |
| during      |                                             |          |
| initial     |                                             |          |
| scoping     |                                             |          |
| meeting are |                                             |          |
| listed      |                                             |          |
| below.      |                                             |          |
| Please keep |                                             |          |
| in mind     |                                             |          |
| that each   |                                             |          |
| project     |                                             |          |
| will be     |                                             |          |
| unique and  |                                             |          |
| that a park |                                             |          |
| or group of |                                             |          |
| parks may   |                                             |          |
| have        |                                             |          |
| additional  |                                             |          |
| questions   |                                             |          |
| depending   |                                             |          |
| on the      |                                             |          |
| overall     |                                             |          |
| scope of    |                                             |          |
| the desired |                                             |          |
| project. It |                                             |          |
| will be     |                                             |          |
| important   |                                             |          |
| to identify |                                             |          |
| anticipated |                                             |          |
| timeframes  |                                             |          |
| for the     |                                             |          |
| overall     |                                             |          |
| project at  |                                             |          |
| this time.  |                                             |          |
| Vegetation  |                                             |          |
| mapping     |                                             |          |
| projects    |                                             |          |
| for a       |                                             |          |
| mid-sized   |                                             |          |
| park may    |                                             |          |
| take 3 to 4 |                                             |          |
| years from  |                                             |          |
| start to    |                                             |          |
| completion, |                                             |          |
| depending   |                                             |          |
| on overall  |                                             |          |
| complexity  |                                             |          |
| and         |                                             |          |
| resolution  |                                             |          |
| of          |                                             |          |
| cla         |                                             |          |
| ssification |                                             |          |
| and         |                                             |          |
| mapping.    |                                             |          |
|             |                                             |          |
| Project     |                                             |          |
| planning    |                                             |          |
| also        |                                             |          |
| involves    |                                             |          |
| obtaining   |                                             |          |
| and         |                                             |          |
| reviewing   |                                             |          |
| existing    |                                             |          |
| vegetation  |                                             |          |
| data (e.g.  |                                             |          |
| plant       |                                             |          |
| association |                                             |          |
| lists,      |                                             |          |
| vegetation  |                                             |          |
| plot data). |                                             |          |
| The results |                                             |          |
| of this     |                                             |          |
| review will |                                             |          |
| help        |                                             |          |
| determine   |                                             |          |
| the scope   |                                             |          |
| of work     |                                             |          |
| associated  |                                             |          |
| with the    |                                             |          |
| project.    |                                             |          |
|             |                                             |          |
| Sources of  |                                             |          |
| funding     |                                             |          |
| need to be  |                                             |          |
| identified  |                                             |          |
| and matched |                                             |          |
| with the    |                                             |          |
| scope of    |                                             |          |
| the         |                                             |          |
| project(s). |                                             |          |
| Parks and   |                                             |          |
| networks    |                                             |          |
| should work |                                             |          |
| with WASO   |                                             |          |
| NPS Veg Map |                                             |          |
| Staff (Karl |                                             |          |
| Brown and   |                                             |          |
| Chris Lea)  |                                             |          |
| in          |                                             |          |
| developing  |                                             |          |
| overall     |                                             |          |
| project     |                                             |          |
| proposals.  |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Task**                     | **Who    |
|             |                                             | might be |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ##          | [Address during scoping]{.underline}:       | Park     |
|             |                                             | Staff    |
| ## In       | -   Determine whether the project will be   |          |
| itial Proje |     NPS only or conducted in partnership    | Network  |
| ct Scoping  |     with adjacent landowners (BLM, USFS,    | Staff    |
|             |     TNC etc.).                              |          |
| Meeting or  |                                             | WASO Veg |
|             | -   Determine project mapping area boundary | Map      |
| Conference  |     (include park unit plus area in the     |          |
| Call(s)     |     environs, include partner lands if      | Partners |
|             |     applicable).                            |          |
| Single or   |                                             | Coo      |
| Multi-park  | -   Determine whether the project will be a | perators |
|             |     'basic' veg map project or if it will   |          |
|             |     include more detail on specific         | Nat      |
|             |     ecosystem attributes (e.g. fire and     | ureServe |
|             |     fuels data, special biological or       |          |
|             |     ecological features).                   |          |
|             |                                             |          |
|             | -   Determine level of resolution of        |          |
|             |     mapping & classification effort         |          |
|             |     (association vs. alliance vs.           |          |
|             |     ecological system).                     |          |
|             |                                             |          |
|             | -   Determine what will be used as base map |          |
|             |     (orthophotography, satellite imagery or |          |
|             |     other alternative). Select scale (1:10K |          |
|             |     to 1:12K), and type of photography      |          |
|             |     (true color, infrared, platform).       |          |
|             |                                             |          |
|             | -   Determine plot and observation point    |          |
|             |     field sampling approach.                |          |
|             |                                             |          |
|             | -   Determine methods for mapping and       |          |
|             |     spatial database development            |          |
|             |     (traditional photo interpretation,      |          |
|             |     automated image analysis, or hybrid     |          |
|             |     approach).                              |          |
|             |                                             |          |
|             | -   Identify base cartographic layers       |          |
|             |     available for the veg map project area  |          |
|             |     (e.g. soils, geology, roads, trails,    |          |
|             |     DEMs, park boundary etc.).              |          |
|             |                                             |          |
|             | -   Determine remaining project tasks and   |          |
|             |     timeframes (see other steps below --    |          |
|             |     vegetation classification, description  |          |
|             |     & key development, accuracy assessment, |          |
|             |     final products).                        |          |
|             |                                             |          |
|             | -   Identify who could accomplish the work  |          |
|             |     and possible cooperators                |          |
+-------------+---------------------------------------------+----------+
| **Assemble  | -   Compile preliminary list of plant       | NPS      |
| Existing    |     associations for project area (used to  | Staff or |
| Information |     estimate number of plots needed for     | Co       |
| and Data**  |     classification)                         | operator |
|             |                                             |          |
|             | -   Identify, obtain and review existing    |          |
|             |     plot data for project area and          |          |
|             |     determine whether suitable for use in   |          |
|             |     project - follow guidelines developed   |          |
|             |     by TNC for assessing utility of         |          |
|             |     existing data.                          |          |
+-------------+---------------------------------------------+----------+
| **Project** | -   Identify potential funding resources    | NPS      |
|             |     (look for opportunities to leverage and | Staff    |
| **Funding   |     partner)                                |          |
| Proposal**  |                                             | WASO     |
|             | -   Work with WASO NPS Veg Map Staff in     |          |
| **and       |     developing a project funding proposal   | VegMap   |
| Workplan**  |                                             | Staff    |
|             | -   Develop a project workplan identifying  |          |
|             |     tasks and detailed information on       | Partners |
|             |     accomplishing the work (who, what,      |          |
|             |     where and when).                        |          |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| **STEP 2:   |                                             |          |
| AQUIRE      |                                             |          |
| AERIAL      |                                             |          |
| PHOTOGRAPHY |                                             |          |
| OR OTHER    |                                             |          |
| MAPPING     |                                             |          |
| BASE**      |                                             |          |
+-------------+---------------------------------------------+----------+
| During      |                                             |          |
| scoping,    |                                             |          |
| project     |                                             |          |
| members     |                                             |          |
| will have   |                                             |          |
| identified  |                                             |          |
| the type of |                                             |          |
| imagery     |                                             |          |
| desired as  |                                             |          |
| the base    |                                             |          |
| map for the |                                             |          |
| vegetation  |                                             |          |
| mapping     |                                             |          |
| effort.     |                                             |          |
| This step   |                                             |          |
| involves    |                                             |          |
| acquiring   |                                             |          |
| the         |                                             |          |
| imagery.    |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Task**                     | **Who is |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ##          | Veg Map project staff will procure existing | NPS      |
|             | imagery or contract for services to acquire | Staff    |
| ## Acqu     | new imagery/photography to use as a base    |          |
| ire Imagery | map. Imagery specifications will need to be | Coo      |
|             | determined, such as:                        | perators |
|             |                                             |          |
|             | -   Type of imagery -- true color or        |          |
|             |     infrared aerial photography, satellite  |          |
|             |     platform,etc.                           |          |
|             |                                             |          |
|             | -   Timing of photography/imagery --        |          |
|             |     seasonally and time of day (e.g. near   |          |
|             |     summer solstice and noon to minimize    |          |
|             |     shadow effects in terrain with extreme  |          |
|             |     vertical relief; or a certain season to |          |
|             |     capture phenology which maximizes       |          |
|             |     expression of vegetation patterns)      |          |
|             |                                             |          |
|             | -   Format -- film, digital, etc.           |          |
|             |                                             |          |
|             | -   Scale (e.g. 1:12,000)                   |          |
|             |                                             |          |
|             | In some cases parks may choose to           |          |
|             | orthorectify existing aerial photography    |          |
|             | and create a new digital coverage (this may |          |
|             | work for small project areas)               |          |
|             |                                             |          |
|             | [Imagery Area Considerations]{.underline}.  |          |
|             | It is helpful to consider the ground area   |          |
|             | for the imagery to be acquired in relation  |          |
|             | to the defined veg map project area.        |          |
|             | Ultimately the base imagery is used for     |          |
|             | many more purposes than just the veg map    |          |
|             | project. With this in mind the              |          |
|             | networks/parks may want the base imagery to |          |
|             | extend beyond the vegmap project area       |          |
|             | boundary. Aerial flights for                |          |
|             | orthophotography are typically flown at     |          |
|             | fairly high elevations and the photography  |          |
|             | taken usually encompasses an area exceeding |          |
|             | the veg map project mapping area. For very  |          |
|             | little additional cost networks/parks could |          |
|             | acquire a slightly larger surrounding area  |          |
|             | in the orthophoto coverage. The point here  |          |
|             | is carefully think about the imagery        |          |
|             | coverage boundaries and what will best      |          |
|             | serve the parks in the long term.           |          |
|             |                                             |          |
|             | Some veg map projects have conducted a      |          |
|             | QA/QC procedure on the digital base ortho   |          |
|             | coverage.                                   |          |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| **STEP 3:   |                                             |          |
| FIELD PLOT  |                                             |          |
| AND         |                                             |          |
| OBSERVATION |                                             |          |
| POINT DATA  |                                             |          |
| COLLECTION  |                                             |          |
| AND ENTRY** |                                             |          |
+-------------+---------------------------------------------+----------+
| In the      |                                             |          |
| scoping     |                                             |          |
| step, based |                                             |          |
| on the      |                                             |          |
| analysis of |                                             |          |
| existing    |                                             |          |
| data,       |                                             |          |
| net         |                                             |          |
| works/parks |                                             |          |
| will have   |                                             |          |
| determined  |                                             |          |
| whether new |                                             |          |
| vegetation  |                                             |          |
| data is     |                                             |          |
| needed to   |                                             |          |
| support     |                                             |          |
| cla         |                                             |          |
| ssification |                                             |          |
| and mapping |                                             |          |
| efforts.    |                                             |          |
| Most        |                                             |          |
| projects    |                                             |          |
| will rely   |                                             |          |
| entirely on |                                             |          |
| or          |                                             |          |
| partially   |                                             |          |
| on new      |                                             |          |
| field data  |                                             |          |
| being       |                                             |          |
| collected.  |                                             |          |
| Several     |                                             |          |
| tasks       |                                             |          |
| related to  |                                             |          |
| collecting  |                                             |          |
| vegetation  |                                             |          |
| field data  |                                             |          |
| are         |                                             |          |
| identified  |                                             |          |
| below.      |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Task**                     | **Who is |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ## Identif  | Determine types of field data to be         | NPS      |
| y Types of  | collected: vegetation plots (releves);      | Staff    |
|             | fire/fuels data, observation points, other. |          |
| ##          |                                             |          |
| Field Data  |                                             |          |
+-------------+---------------------------------------------+----------+
| ##          | For vegetation plots:                       | NPS      |
|             |                                             | Staff    |
| #           | -   Estimate the number of vegetation plots |          |
| # Plot Samp |     needed (e.g. 3 to 5 plots for each      | and/or   |
| ling Design |     expected plant association)             |          |
|             |                                             | Coo      |
|             | ```{=html}                                  | perators |
|             | <!-- -->                                    |          |
|             | ```                                         |          |
|             | -   Determine sampling approach for         |          |
|             |     vegetation plot locations (e.g.         |          |
|             |     gradsect or other)                      |          |
|             |                                             |          |
|             | -   If applicable, develop sampling         |          |
|             |     framework (e.g. conduct gradsect        |          |
|             |     analysis)                               |          |
+-------------+---------------------------------------------+----------+
| ##          | [Protocols]{.underline}. This task involves | NPS      |
|             | documenting field sampling protocols for    | Staff    |
| ## Fie      | the types of data identified above (e.g.    |          |
| ld Sampling | plots, observation points, fire/fuels,      | and/or   |
|  Protocols  | accuracy assessment). Protocols should not  |          |
| & Database  | only address what data are collected but    | Coo      |
| Development | how the data are collected (e.g. GPS use,   | perators |
|             | data loggers, etc.) Although core data      |          |
|             | components have been standardized at the    |          |
|             | national program level, specific            |          |
|             | documentation for use by field crews has    |          |
|             | not been standardized. Parks may desire     |          |
|             | additional field data. A field manual and   |          |
|             | accompanying field forms documenting field  |          |
|             | sampling protocols should be developed,     |          |
|             | tested and finalized well in advance of the |          |
|             | field season. There are several examples of |          |
|             | existing veg map project field manuals and  |          |
|             | forms from completed veg map projects.      |          |
|             |                                             |          |
|             | [Databases]{.underline}. A database matched |          |
|             | to the field forms needs to be in place     |          |
|             | prior to field work. The NPS/USGS veg map   |          |
|             | program developed a database to house plot  |          |
|             | data (but not other types of field data).   |          |
|             | More recently some networks and parks have  |          |
|             | developed other more flexible Access        |          |
|             | database applications to house all types of |          |
|             | field data (plots, observation points, AA   |          |
|             | points, fuels). Ground photos (or digital   |          |
|             | movies) are taken as part of the field      |          |
|             | sampling effort. A database and protocol    |          |
|             | for managing project photographs needs to   |          |
|             | be developed.                               |          |
+-------------+---------------------------------------------+----------+
| ##          | Conduct pre-field season planning with      | NPS      |
|             | parks and veg map project staff; secure     | Staff    |
| **Conduct** | necessary research permits, backcountry     |          |
|             | permits, campsites, etc.                    | and/or   |
| **Field     |                                             |          |
| Data        | Assemble field manuals, field forms, maps,  | Coo      |
| C           | photography and equipment to conduct field  | perators |
| ollection** | work.                                       |          |
|             |                                             | Nat      |
|             | Hire field crew (can be NPS and/or          | ureServe |
|             | cooperator crews)                           | (?)      |
|             |                                             |          |
|             | Provide field based training for all crew   |          |
|             | members in the protocols (the more emphasis |          |
|             | put on this step the higher quality the     |          |
|             | data and products). It may be helpful to    |          |
|             | have NatureServe participate in the         |          |
|             | training session, given their involvement   |          |
|             | in the classification work.                 |          |
|             |                                             |          |
|             | Oversee and manage field data collection    |          |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| ##          | Enter field data into the project database  | NPS      |
|             | either electronically (e.g. downloads of    | Staff    |
| ## Fiel     | GPS or data logger units) and/or manually.  |          |
| d Data Entr |                                             | and/or   |
| y and QA/QC | Develop and implement a thorough QA/QC      |          |
|             | procedure for ensuring that electronic data | Coo      |
|             | field data are complete and accurate.       | perators |
|             |                                             |          |
|             | Ensure proper storage of original field     |          |
|             | forms.                                      |          |
|             |                                             |          |
|             | Process all project photography, ensure     |          |
|             | that slides or print photos are             |          |
|             | sufficiently labeled and archived and that  |          |
|             | digital photos/movies are fully documented  |          |
|             | with associated information (e.g. plot      |          |
|             | number, photographer, caption, etc.)        |          |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| **STEP 4:   |                                             |          |
| PLANT       |                                             |          |
| ASSOCIATION |                                             |          |
| CLA         |                                             |          |
| SSIFICATION |                                             |          |
| ANALYSIS,   |                                             |          |
| DESCRIPTION |                                             |          |
| AND KEY**   |                                             |          |
+-------------+---------------------------------------------+----------+
| Once the    |                                             |          |
| field data  |                                             |          |
| (or         |                                             |          |
| previously  |                                             |          |
| existing    |                                             |          |
| data) are   |                                             |          |
| in          |                                             |          |
| electronic  |                                             |          |
| form the    |                                             |          |
| cla         |                                             |          |
| ssification |                                             |          |
| analysis    |                                             |          |
| can         |                                             |          |
| proceed.    |                                             |          |
| During this |                                             |          |
| analysis    |                                             |          |
| plant       |                                             |          |
| a           |                                             |          |
| ssociations |                                             |          |
| are         |                                             |          |
| classified  |                                             |          |
| according   |                                             |          |
| to the      |                                             |          |
| National    |                                             |          |
| Vegetation  |                                             |          |
| Cla         |                                             |          |
| ssification |                                             |          |
| Standard    |                                             |          |
| (NVC).      |                                             |          |
| NatureServe |                                             |          |
| is a        |                                             |          |
| primary     |                                             |          |
| partner in  |                                             |          |
| analyzing   |                                             |          |
| and/or      |                                             |          |
| reviewing   |                                             |          |
| cla         |                                             |          |
| ssification |                                             |          |
| results and |                                             |          |
| in          |                                             |          |
| developing  |                                             |          |
| global      |                                             |          |
| d           |                                             |          |
| escriptions |                                             |          |
| for the     |                                             |          |
| as          |                                             |          |
| sociations. |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Task**                     | **Who is |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ##          | Electronic vegetation plot data are         | Nat      |
|             | subjected to multivariate classification    | ureServe |
| #           | procedure (ordination and clustering        |          |
| # Conduct C | algorithms). This step is typically by an   | NPS      |
| lassificati | academic or ecological services             | Staff    |
| on Analysis | contractor).                                |          |
|             |                                             | and/or   |
|             | The classification is first produced in a   | Other    |
|             | 'preliminary' form and may not be finalized |          |
|             | until the entire project is complete.       | Coo      |
|             |                                             | perators |
|             | Develop crosswalk of final plant            |          |
|             | associations to plots/observation points    |          |
|             | used for classification.                    |          |
+-------------+---------------------------------------------+----------+
| ##          | For the final classified plant associations | Nat      |
|             | prepare local and global descriptions.      | ureServe |
| **Plant     | Typically NatureServe ecologists are        |          |
| Association | responsible for the global portion of the   | NPS      |
| Des         | descriptions, where other cooperators or    | Staff    |
| criptions** | NPS staff may develop the local             |          |
|             | descriptions. These descriptions will be    | Other    |
|             | included in the final report.               | Coop     |
|             |                                             | erators? |
+-------------+---------------------------------------------+----------+
| ##          | Develop dichotomous key to plant            | Coo      |
|             | associations (illustrated is good). The key | perators |
| **Plant     | will be used by field crews during accuracy |          |
| Association | assessment and included as a product in the | and/or   |
| Field Key** | final report.                               |          |
|             |                                             | NPS      |
|             |                                             | Staff    |
|             |                                             |          |
|             |                                             | Nat      |
|             |                                             | ureServe |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| **STEP 5:   |                                             |          |
| VEGETATION  |                                             |          |
| MAPPING AND |                                             |          |
| SPATIAL     |                                             |          |
| DATABASE    |                                             |          |
| DE          |                                             |          |
| VELOPMENT** |                                             |          |
+-------------+---------------------------------------------+----------+
| Ideally the |                                             |          |
| field plot  |                                             |          |
| data        |                                             |          |
| collection  |                                             |          |
| and         |                                             |          |
| cla         |                                             |          |
| ssification |                                             |          |
| steps are   |                                             |          |
| completed   |                                             |          |
| prior to    |                                             |          |
| initiation  |                                             |          |
| of mapping. |                                             |          |
| However, in |                                             |          |
| some cases  |                                             |          |
| these steps |                                             |          |
| are         |                                             |          |
| conducted   |                                             |          |
| co          |                                             |          |
| ncurrently. |                                             |          |
| It is       |                                             |          |
| useful to   |                                             |          |
| have the    |                                             |          |
| cla         |                                             |          |
| ssification |                                             |          |
| results to  |                                             |          |
| help inform |                                             |          |
| development |                                             |          |
| of map      |                                             |          |
| class       |                                             |          |
| concepts.   |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Task**                     | **Who is |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ##          | Develop clear documentation for photo       | NPS      |
|             | interpreters and cartographers to use in    | Staff    |
| ## Mapp     | attributing vegetation map polygons (e.g.   |          |
| ing Protoco | density, height, pattern, other modifiers,  |          |
| ls and Spat | etc.).                                      |          |
| ial Databas |                                             |          |
| e Structure | Determine upfront all data fields that will |          |
|             | be linked to the final spatial database     |          |
|             | (e.g. map class code & name, NVC            |          |
|             | classification, information, etc.)          |          |
+-------------+---------------------------------------------+----------+
| ##          | Examine aerial photography or satellite     | NPS      |
|             | imagery to identify signatures for mapping  | Staff    |
| ## Photo    | purposes (either determined through manual  |          |
| Signature D | photo interpretation techniques or computer | Coo      |
| evelopment  | assisted image analysis such as             | perators |
|             | eCognition).                                |          |
|             |                                             | Nat      |
|             |                                             | ureServe |
+-------------+---------------------------------------------+----------+
| ##          | Based on the interpretable signatures       | NPS      |
|             | develop legend describing the concept of    | Staff    |
| **MapClass  | the map class.                              |          |
| Legend,     |                                             | Coo      |
| Crosswalk   | Develop a crosswalk between the map classes | perators |
| and         | and classified plant associations.          |          |
| Des         |                                             |          |
| criptions** | Hold a map legend meeting with network      |          |
|             | and/or park staff and other cooperators to  |          |
|             | solicit agreement regarding map class       |          |
|             | concepts.                                   |          |
|             |                                             |          |
|             | Develop map class descriptions including    |          |
|             | the visual signature, ecological concepts   |          |
|             | of the map classes, corresponding plant     |          |
|             | associations -- illustrated with ground     |          |
|             | (plot photos) and photo signature           |          |
|             | 'snapshots' from the imagery. These         |          |
|             | descriptions will be included in the final  |          |
|             | report.                                     |          |
+-------------+---------------------------------------------+----------+
| ##          | Conduct vegetation mapping per identified   | NPS      |
|             | protocol (e.g. traditional photo            | Staff    |
| **Conduct   | interpretation, digitize & transfer; image  |          |
| Mapping**   | analysis/hybrid approaches, etc.)           | and/or   |
|             |                                             |          |
| **Spatial   | Document in written form (w/illustration    | Coo      |
| Database    | and/or photos) the mapping protocol used.   | perators |
| De          | This will be included in the final report.  |          |
| velopment** |                                             |          |
+-------------+---------------------------------------------+----------+
| ##          | Develop draft final digital map with        | NPS      |
|             | associated attribute data.                  | Staff    |
| **Draft Map |                                             |          |
| P           |                                             | and/or   |
| roduction** |                                             |          |
|             |                                             | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| **STEP 6:   |                                             |          |
| ACCURACY    |                                             |          |
| ASSESSMENT  |                                             |          |
| (AA)**      |                                             |          |
+-------------+---------------------------------------------+----------+
| Accuracy    |                                             |          |
| assessment  |                                             |          |
| is          |                                             |          |
| conducted   |                                             |          |
| for the     |                                             |          |
| draft final |                                             |          |
| digital     |                                             |          |
| vegetation  |                                             |          |
| map.        |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Task**                     | **Who is |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ## Select   | Follow national NPS/USGS Veg Map protocol   | NPS or   |
|  AA Points  | in selecting random points for AA field     | co       |
|             | data collection.                            | operator |
|             |                                             | GIS      |
|             |                                             | staff    |
+-------------+---------------------------------------------+----------+
| ##          | AA field data collection protocols and      | NPS      |
|             | field forms are documented in overall veg   | Staff    |
| ## Fie      | map project field manual (see Step 3        |          |
| ld Sampling | above).                                     | and/or   |
|  Protocols  |                                             |          |
| & Database  | Project database is designed to house AA    | Coo      |
| Development | field data (see Step 3 above)               | perators |
+-------------+---------------------------------------------+----------+
| ##          | Conduct pre-field season planning with      | NPS      |
|             | parks and vegmap project staff; secure      | Staff    |
| **AA Point  | necessary research permits, backcountry     |          |
| Field Data  | permits, campsites, etc.                    | and/or   |
| C           |                                             |          |
| ollection** | Assemble and copy field manuals, field      | Coo      |
|             | forms, maps, photography and equipment to   | perators |
|             | conduct field work. Load AA points in GPS   |          |
|             | units for navigation.                       |          |
|             |                                             |          |
|             | Hire field crew (can be NPS and/or          |          |
|             | cooperator crews)                           |          |
|             |                                             |          |
|             | Provide field based training for all crew   |          |
|             | members in the protocols (the more emphasis |          |
|             | put on this step the higher quality the     |          |
|             | data and products).                         |          |
|             |                                             |          |
|             | Oversee and manage AA point field data      |          |
|             | collection                                  |          |
+-------------+---------------------------------------------+----------+
| ##          | Enter field data into the project database  | NPS      |
|             | either electronically (e.g. downloads of    | Staff    |
| **AA Data   | GPS or data logger units) and/or manually.  |          |
| Entry and   |                                             | and/or   |
| QA/QC**     | Develop and implement a thorough QA/QC      |          |
|             | procedure for ensuring that electronic data | Coo      |
|             | field data are complete and accurate.       | perators |
|             |                                             |          |
|             | Ensure proper storage of original AA field  |          |
|             | forms.                                      |          |
|             |                                             |          |
|             | Process all AA related photography, ensure  |          |
|             | that slides or print photos are labeled and |          |
|             | archived and that digital photos are        |          |
|             | documented with associated information      |          |
|             | (e.g. plot number, photographer, caption,   |          |
|             | etc.)                                       |          |
+-------------+---------------------------------------------+----------+
| ##          | Follow national protocol in conducting      | NPS      |
|             | accuracy assessment analysis. Results are   | Staff    |
| **AA        | presented in a contingency table indicating |          |
| Analysis**  | user and producer accuracy levels for each  | and/or   |
|             | sampled map class.                          |          |
|             |                                             | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+
| **AA        | Review AA results and prepare               | NPS      |
| Meeting**   | recommendations on how to address problems  | Staff    |
|             | of low accuracy (e.g. combination of map    |          |
|             | classes).                                   | and/or   |
|             |                                             |          |
|             | Hold meeting with park staff and project    | Coo      |
|             | cooperators to review the AA results,       | perators |
|             | discuss suggested 'fixes' to accuracy       |          |
|             | problems, and make decisions on map classes |          |
|             | for the final vegetation map.               |          |
+-------------+---------------------------------------------+----------+
| **Final Map | Make changes to the final map class legend  | NPS      |
| Adjustment  | and spatial map layer based on decisions    | Staff    |
| based on    | from the AA meeting. Conduct QA/QC          |          |
| AA**        | procedure.                                  | and/or   |
|             |                                             |          |
|             |                                             | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+

+-------------+---------------------------------------------+----------+
| # STE       |                                             |          |
| P 7: FINAL  |                                             |          |
| REPORT, SPA |                                             |          |
| TIAL DATA A |                                             |          |
| ND METADATA |                                             |          |
+-------------+---------------------------------------------+----------+
| The last    |                                             |          |
| step is to  |                                             |          |
| assemble a  |                                             |          |
| set of      |                                             |          |
| d           |                                             |          |
| eliverables |                                             |          |
| documenting |                                             |          |
| the entire  |                                             |          |
| project     |                                             |          |
| start to    |                                             |          |
| finish and  |                                             |          |
| delivering  |                                             |          |
| the         |                                             |          |
| information |                                             |          |
| is useful   |                                             |          |
| formats.    |                                             |          |
| FGDC        |                                             |          |
| compliant   |                                             |          |
| metadata    |                                             |          |
| are         |                                             |          |
| compiled.   |                                             |          |
|             |                                             |          |
| Final       |                                             |          |
| products    |                                             |          |
| need to be  |                                             |          |
| distributed |                                             |          |
| in user     |                                             |          |
| friendly    |                                             |          |
| interfaces. |                                             |          |
| All final   |                                             |          |
| products    |                                             |          |
| will be     |                                             |          |
| posted to   |                                             |          |
| the         |                                             |          |
| NPS/USGS    |                                             |          |
| Veg Map     |                                             |          |
| Program     |                                             |          |
| website     |                                             |          |
| (<h         |                                             |          |
| ttp://biolo |                                             |          |
| gy.usgs.gov |                                             |          |
| /npsveg/>). |                                             |          |
| Geodatabase |                                             |          |
| a           |                                             |          |
| pplications |                                             |          |
| show        |                                             |          |
| excellent   |                                             |          |
| promise for |                                             |          |
| delivering  |                                             |          |
| veg map     |                                             |          |
| products in |                                             |          |
| a more user |                                             |          |
| friendly    |                                             |          |
| interface.  |                                             |          |
| The WASO    |                                             |          |
| I&M Program |                                             |          |
| is          |                                             |          |
| conducting  |                                             |          |
| a pilot veg |                                             |          |
| map         |                                             |          |
| geodatabase |                                             |          |
| project.    |                                             |          |
+-------------+---------------------------------------------+----------+
| **Tasks**   | **Description of Final Deliverables**       | **Who is |
|             |                                             | inv      |
|             |                                             | olved?** |
+-------------+---------------------------------------------+----------+
| ##          | [A typical vegetation mapping report will   | NPS      |
|             | include the following chapters documenting  | Staff    |
| ## Fi       | methods and results]{.underline}:           |          |
| nal Report  |                                             | and/or   |
|             | > Introduction & Background                 |          |
| ##          | >                                           | Coo      |
|             | > Vegetation Classification                 | perators |
|             | >                                           |          |
|             | > Vegetation Mapping                        |          |
|             | >                                           |          |
|             | > Accuracy Assessment & Recommendations     |          |
|             | >                                           |          |
|             | > References                                |          |
|             |                                             |          |
|             | [Appendices may include]{.underline}:       |          |
|             |                                             |          |
|             | > Ecological System Descriptions            |          |
|             | >                                           |          |
|             | > Field Data Collection Instructions &      |          |
|             | > Forms                                     |          |
|             | >                                           |          |
|             | > Description of Project Database           |          |
|             | >                                           |          |
|             | > Project Plant Species List (crosswalked   |          |
|             | > to ITIS)                                  |          |
|             | >                                           |          |
|             | > Final Plant Association Classification    |          |
|             | >                                           |          |
|             | > Local & Global Plant Association          |          |
|             | > Descriptons                               |          |
|             | >                                           |          |
|             | > Plant Association Key (Illustrated)       |          |
|             | >                                           |          |
|             | > Map Class Descriptions (Illustrated)      |          |
|             | >                                           |          |
|             | > Accuracy Assessment Matrix                |          |
|             | >                                           |          |
|             | > \*See Effigy Mounds VegMap Report for a   |          |
|             | > good example.                             |          |
+-------------+---------------------------------------------+----------+
| ##          | Final spatial database (line work with      | NPS      |
|             | attributes per mapping protocol).           | Staff    |
| **Final Map |                                             |          |
| and Spatial | Printed map to include with final report.   | and/or   |
| Database**  |                                             |          |
|             | Project metadata.                           | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+
| ##          | Access database with all field data (plots, | NPS      |
|             | fuels, observation points, AA points etc.)  | Staff    |
| **Field     |                                             |          |
| Database**  | Hard copies of field datasheets.            | and/or   |
|             |                                             |          |
|             |                                             | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+
| ##          | Database with all digital photographs       | NPS      |
|             | and/or digital movies.                      | Staff    |
| **Ph        |                                             |          |
| otographs** | If applicable, labeled slides for           | and/or   |
|             | archiving.                                  |          |
|             |                                             | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+
| ##          | Digital orthophotography or other imagery   | NPS      |
|             | used for the project.                       | Staff    |
| **Aerial    |                                             |          |
| Photography | If applicable, stereo photography in hard   | and/or   |
| or other    | copy and/or digital form.                   |          |
| Imagery**   |                                             | Coo      |
|             | Aerial photo indices.                       | perators |
+-------------+---------------------------------------------+----------+
| **Other     | Plots, observation point and AA point       | NPS      |
| Spatial     | location coverages.                         | Staff    |
| Data**      |                                             |          |
|             |                                             | and/or   |
|             |                                             |          |
|             |                                             | Coo      |
|             |                                             | perators |
+-------------+---------------------------------------------+----------+