Software Requirements
Specification
for the
Spatial Intersection Tool (SIT)
DRAFT
8/20/10
Software Requirements Specification for FSVeg Spatial
Page ii
Table of Contents
Table of Contents .......................................................................................................................... ii
1. Introduction ..............................................................................................................................1
1.1
1.2
1.3
1.4
1.5
Purpose ........................................................................................................................................ 1
Document Conventions ............................................................................................................... 1
Intended Audience and Reading Suggestions.............................................................................. 2
Project Scope ............................................................................................................................... 2
Project Documentation ................................................................................................................ 3
2. Overall Description ..................................................................................................................4
2.1
2.2
2.3
2.4
2.5
2.6
2.7
Product Perspective ..................................................................................................................... 4
Product Features .......................................................................................................................... 4
User Classes and Characteristics ................................................................................................. 4
Operating Environment ............................................................................................................... 5
Design and Implementation Constraints...................................................................................... 6
User Documentation .................................................................................................................... 6
Assumptions and Dependencies .................................................................................................. 6
3. System Features .......................................................................................................................7
4. External Interface Requirements .........................................................................................15
4.1
User Interfaces ........................................................................................................................... 15
5. Other Requirements ..............................................................................................................15
5.1
5.2
5.3
5.4
Performance Requirements........................................................................................................ 15
Safety Requirements .................................................................................................................. 15
Security Requirements............................................................................................................... 15
Software Quality Attributes ....................................................................................................... 16
6. Citations ..................................................................................................................................16
Appendix A: Acronyms ...............................................................................................................17
Appendix B. Glossary ..................................................................................................................19
Appendix C: Analysis Models .....................................................................................................28
ii
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
1. Introduction
1.1 Purpose
This document contains the software requirements for the Spatial Intersection Tool (SIT), which
is part of the Analytical Tool for Inventory and Monitoring (ATIM). Although the tool will be
accessible to the public, this project is focused on helping Forests and Regions improve
inventory and monitoring data storage and analyses by developing a nationally consistent tool for
NFS. Initially work will focus on vegetation monitoring, but also allow for future monitoring of
other resources collected from plot-based natural resource samples. Statistically sound estimates
of the current status and trends of the vegetation and its associated attributes are fundamental to:
developing Forest Plan components, Forest Plan monitoring associated with vegetation;
monitoring of broad-level incidence and spread of invasive plant species; monitoring and
management of wildlife habitat including cumulative effects analysis for project level planning;
and, monitoring and management of fuels. Adaptive approaches are needed to address emerging
monitoring requirements at the forest and landscape levels, which may be associated with issues
such as climate change, carbon, biofuels and forest certification.
In order to successfully monitor key components of vegetation diversity over time, the inventory
system used to derive current estimates must have the same attributes, at the same sample
locations, remeasured over a meaningful time period. Forest Inventory and Analysis (FIA) data
on forest and nonforest National Forest lands, where available, and data from similar National
Forest inventories can provide statistically-based inventories appropriate to use for broad-level
planning and analysis. Unbiased estimates and confidence intervals may be derived for large
landscapes, such as for a National Forest. In addition, since the inventories are a spatially
balanced sample across all lands, they can be associated with various spatial datasets such as
ecological section or existing vegetation layers to describe vegetation characteristics within each
map strata.
SIT and ATIM would enable the National Forest System (NFS) to analyze inventory data to
derive estimates of spatially identified populations and display the results using map attributes.
These estimates of current condition and trends for attributes associated with vegetation will help
meet information needs for National Forests and the surrounding landscapes.
Software development work is expected to progress iteratively to ensure that SIT is being built as
designed, to be adaptive to both changing needs and technology, and to minimize investment
risk. This software requirement documentation describes the functionality desired in SIT. Based
on user feedback from early releases of SIT and continued user engagement, additional
specifications may be defined as appropriate and as requested.
1.2 Document Conventions
Requirements are numbered REQ-#.# (e.g. REQ-1.3) where the first number represents the
implementation phase and the second number is a sequential number.
1
Page 1
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
1.3 Intended Audience and Reading Suggestions
This document is intended for developers, project managers, team members, testers,
documentation writers, and all interested stakeholders. All acronyms are explained in the text
and included in the list of acronyms in the appendix. The glossary (see appendix) includes a
description of some technical terms to accommodate a diverse audience.
Detailed Use Cases are stored in a separate document. To obtain additional detail on a particular
requirement, refer to the Use Case document, accessible via a link similar to the following:
http://sforge.fs.fed.us/sf/go/doc4518?nav=1
1.4 Project Scope
The intent of ATIM is to provide National Forest Systems with a consistent application that can
read, compile, query, and analyze statistically-based vegetative inventory data such as FIA and
other regional inventories. ATIM will link to spatial data using the Spatial Intersection Tool so
that they can be used in the compiling and analysis of data as well as produce map products
directly or via ArcGIS or the NRIS Geospatial Interface. SIT will be able to use FACTS (Forest
Service Activities Tracking System) to identify changes that occurred since the time of
inventory. SIT will be developed as an ArcGIS extension, and it will run within the Forest
Service computing environment. The scope does not include the gathering or loading of data –
just the specified tools to load and analyze data.
The application will need to access the data features of both FSVeg (Field Sampled Vegetation)
and FIADB databases (current versions of both). Since not all attributes/requirements currently
exist in either FSVeg or FIADB, discussions will be held to accommodate the necessary changes.
A later phase will include the ability to link to other Regional and Corporate datasets such as
those in NRIS (National Resource Information System) where co-located inventory data may be
found. A schematic of ATIM is given below. A more detailed version is shown in the
Appendix.
2
Page 2
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
Schematic of ATIM:
1.5 Project Documentation
All documents related to this project are stored in Source Forge and can be accessed via the
following link:
http://sforge.fs.fed.us/sf/docman/do/listDocuments/projects.nris_fsveg_spatial/docman.root
3
Page 3
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
2. Overall Description
2.1 Product Perspective
ATIM provides a tool for all NFS Regions to consistently analyze their vegetation inventory
data. Currently NFS has no national application to address that need. SIT is a way to integrate
spatial datasets with spatially balanced plot-based inventories and derive the acres associated
with the various strata., and produce estimates with confidence intervals, and display associated
map-based products. Some Regions and FIA have developed spatial tools to meet their specific
needs. In creating a national application, SIT may incorporate features of those applications to
best meet the needs of all Regions.
2.2 Product Features









Interface to intersect I&M data with spatial data to subset the data for analysis and for
creating mapped products. These queries will be based on spatial polygons or other
geospatial parameters, e.g., distance from linear features.
Ability to transmit the intersection results to ATIM for analysis, such as creating tables of
estimates for the selected area. Note that the ATIM results could then be used by DTIM.
DTIM is the Design Tool for Inventory and Monitoring
Ability to store and share the results of the intersection (e.g., the plot list) with others.
Ability to display ATIM results summarized by map polygons in order to create mapped
products based on the estimates.
Ability to intersect with all geospatial features, including polygons, linear features, and raster
data sets.
Ability to integrate with other applications using the Geospatial Interface to summarize those
data to the same polygons that ATIM uses SIT to summarize to. For example, use the NRIS
Water module to summarize watershed condition to HUC5s and then use SIT to have ATIM
summarize vegetation data to the same HUCs.
Supporting documentation and training materials.
In a subsequent Phase, consider including editing features to correctly identify plots near
polygon boundaries, since there are potential locational errors in both I&M data and spatial
data layers.
Ability to intersect plot locations with FACTs and Fire History Layers to identify plots that
may have been affected by disturbances such as fire and harvest.
2.3 User Classes and Characteristics
There will be five different scenarios for the use of SIT. As is indicated in the graphic in section
1.4, SIT will be used during the Compilation phase by the data processor to determine acres that
each plot represents given the spatial coverage of interest and to perform intersections for
standard attributes, such as Congressional District and EcoSubsection.
Regional Geospatial Processors: Process spatial features that will be used by SIT. Ensure that
Feature Datasets meet minimum specification in order to be used by SIT.
•
•
QA/QC plot locations that have associated data in ATIM to ensure that locations agree
with geographic area of inference, i.e. Forest boundary.
Perform spatial intersections to populate standard attributes within ATIM.
4
Page 4
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
•
Use SIT to create Estimation Units and delineate the plots associated with each
estimation unit and, optionally, strata within estimation units. For National Forests, all
estimation units will tie back to the National Forest boundary itself (based upon ALPS)
and stored in a standard way nationally within Oracle SDE. This information, the
geographic area of inference, and associated plot weights, will be stored in tables used by
DATIM.
Resource Specialists, Forest Planners and Analysts: Use SIT to query plots based on spatial
databases. Planners and analysts should coordinate with the designated inventory and geospatial
specialist to ensure specific information needs are met.
Geographic Information System (GIS) Specialists: Uses SIT to integrate broad and mid-level
existing vegetation spatial databases with spatially balanced inventory data and process data as
per classification standards. Use SIT to understand where current plot-based data is located prior
to using grid intensification software.
Forest Service Cooperators: Use ATIM and SIT to query, interpret, analyze and understand the
vegetation data as it relates to specific resource issues
Interested Public: Use ATIM and SIT to query, interpret, analyze and understand the vegetation
data as it relates to specific resource issues addressed in forest planning and project level NEPA .
In addition, there are maintenance and support roles and responsibilities:
FIA Geospatial Specialist: Provide point locations in a standard format to NFS Regional
specialist on an annual basis. Ensure that associated data in NIMS is complete and meet data
quality standards.
Regional Specialists: Maintain the point spatial layer associated with FIA and intensified grid
locations, as well as Regional spatial layer(s) in Oracle SDE that are associated with the
inventory point layer in order for SIT to subset the data for analysis by ATIM and for creating
map products using ATIM results. Other Regional Inventory Specialist responsibilities include:
•
•
•
•
•
•
Work with FIA on an annual basis to update point locations in regards to FIA plots;
Work with FIA, ensure that all new data needed is in ATIM.
Ensuring that all employees within the Region who have access to FIA plot locations
have confidentiality agreements signed on an annual basis;
Reviewing data for accuracy; archiving information that is no longer from current
inventory, modifying ownership status as needed, and informing FIA Regional contact of
any changes;
Providing technical expertise on inventory data available in Region and appropriate uses
thereof;
Providing training and technical transfer, as needed.
Forest Specialists: Work with Forest and Regional Geospatial specialists to ensure that needed
spatial datasets are available within Oracle SDE and the GI for use by SIT.
2.4 Operating Environment

Operate in a Data Center environment (Enterprise Data Center – EDC)
5
Page 5
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring







Back end Oracle servers (Linux or similar Operating System)
Serve data to the DataMart
Citrix farm to serve the client interface
PC Windows operating system on the client
Wide area network (WAN)
ArcGIS (9.3x to 10.0+)
Other Forest Service Natural Resource Applications (FSNRAs) will coexist in this
environment
2.5 Design and Implementation Constraints












Internal and external (out side of the Firewall) access to a development and testing
environment as specified in 2.4 above Difficulty in implementing national architectural
standards (e.g. look and feel, shared components)
Difficulty in implementing security standards (Certification and Accreditation)
Data access constraints
Network performance
E-Authentication difficulties
Software versions of key commercial products (e.g. Oracle, Access, Java, .Net) are not
available
Migration and customization issues of existing Regional systems
National data and software policies
Unknown issues with the backup and server management procedures
Regional or local inventory and monitoring data and spatial data practices that do not fit well
with this project
Full understanding of the limitations and/or capabilities of NITC (e.g. commercial software
updates and ATIM updates)
Integrate with other FSNRAs (and other National Forest System applications), such as
FSVeg, FSVeg Spatial, FACTS, and Geospatial Interface Tool.
2.6 User Documentation
User Guide instructions will be available for SIT as part of ATIM. On-line help, if used, will be
implemented via Robo Help. In addition, training materials will be available for use in Forest
Service training sessions.
All user documentation components will comply with FSNRA documentation standards.
Documentation includes a User Guide and training materials. Documentation and training
materials will be made available on the FSWeb as well as the WWW for the Forest Service.
Documentation will include instructions on how to obtain and install client software. This will
include a list of all software and/or hardware prerequisites and instructions on how to obtain
missing prerequisites. It will also include instructions on obtaining, installing, and quick
checking the new software.
2.7 Assumptions and Dependencies
Assumptions that have direct impact on the requirements are:
1. The Enterprise Data Center is established and reliably maintained (e.g. backups, adequate
capacity, contain version management, tuned for top performance).
6
Page 6
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
2. ArcMap performs adequately in the Data Center/Citrix environment.
3. Spatial data are stored in a geodatabase (Spatial Data Engine – SDE) with appropriate
connections to ATIM’s database (FSVeg or FIADB).
4. Geospatial Interface (GI) or other tool is available or can be readily developed to connect
the spatial datasets needed for inventory and monitoring analysis.
5. SIT will be integrated with NRIS GI Tools within the Forest Service. If possible, SIT will
be an ArcMap Extension freely available to the Public.
6. User interface design complies with FSNRA interface standards.
7. All I&M data are stored in FSVeg or FIADB (preferably just one).
8. US Forest Service Standards for Data and Tool design will be followed. Examples are:
http://cdb.fs.usda.gov/content/dav/fs/Reference/FSWeb/BusOps/CIO/EGIS/
documents/GDBDesignStandards_v1_0.pdf
3. System Features
REQ-1.1: Data Processing Rules
REQ-1.2: Geodatabases Created and Maintained for SIT
REQ-1.3: Data Selection Capability
REQ-1.4: Process New or Selected Polygons
REQ-1.5: SIT Data Selection Passed Directly to ATIM(s)
REQ-1.6 : Process Data
REQ-1.7: Administrator Management Capabilities
REQ-1.1 Data Processing Rules
Requirements:
•
Rules are created and agree upon by the Core Team in order to set National Standards on
how the work must be done.
Specifications: These are rules that need to be discussed and decisions made.
•
USFS will have one National Geodatabase for FIA Data.
•
When doing spatial queries with Plots that have subplots, do we use the single, central
plot location for the intersect? Or do we use all 4 subplot (assume FIA plot) locations.
How should the data be processed when one or more of the subplots are not selected?
When looking at the subplot or its condition, how are the subplots selected by individuall
Featureclass – ie. Ownership, Evaluation Unit, Watershed Boundary, etc.
•
•
Allow user the ability to query data to identify any plots outside the polygon that might
belong to the area of interest, such as using the Administrative Forest Code, to identify
NFS plots with coordinates outside the ALP NFS boundary or ALP Ownership layer. This
process will be repeated for each layer being used for plot selection
When doing a spatial query on Actual FIA plot locations, the minimum polygon size
allowed is XXX acres? Or ???
7
Page 7
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
•
Plot Intensification procedures for FIA plots on grid and off grid.
•
Plot Intensification procedures for Non FIA Inventories.
•
How close can FIA plots be to another FIA or FIA like Plot?
•
Data map scale, accuracy and standards for Gis data. 1) Plots should be represented on
the 1:24,000 scale or +- 40 feet of true ground location. Or 2) Plots should be
represented on +- 10 feet (3 meters) of true ground location…. Or..???
•
Allow user the ability to optionally subset the data based on existing attributes
• determine the specifications that NFS wants if a polygon has a small number of plots.
•
Allow user the ability to optionally subset data based on attributes observed, such as P2
vs. P3, remeasured vs. new, or accessed vs. non-sampled, and to create separate estimates
for each.
REQ-1.2 Geodatabases Created and Maintained for SIT
Requirements:
•
New Geodatabases are needed in order to create National Standard for several Inventory
and Monitoring Datasets. These Geodatabases are needed to provide national
consistency for attribute and feature class naming.
Specifications: Do we need these Geodatabases? What attributes are needed?
Geodatabases for SIT (will need to describe for FS GIS Data Dictionary )
•
Fuzzed FIA Plot Locations
•
Real FIA Plot Locations NFS Other ownerships?
•
Intensified FIA Plots on Grid
•
Intensifies FIA Plots off Grid
•
FSVeg Inventory Plots (Not FIA, Not Stand Based)
•
Estimation Unit Polygons
•
Forest-Non-Forest stratification grid
Geodatabase Maintenance:
•
Role based editing of the FIA on Grid plot Data, must have permission.
•
Update FIA plot locations at least yearly base location on that years plot measurement of
GPS location. Edit other plot locations as needed. MetaData will track reason(s) for
change
•
Intensification of FIA Grid is governed by rule documented in REQ 1.1 above.
8
Page 8
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
•
FIA Base Grid is maintained by FIA. FIA Intensification is a discussion and decision
between FIA and the Region
•
Intensification of the FIA grid with plots that are NOT part of the FIA dataset needs to be
coordinated between the Region and FIA. Plots not part of the FIA grid are maintained
by the Region.
•
Editing and basic attribute editing of PLOT and COND tables should be integrated with
FSVeg Spatial tools.
•
Estimation Unit creation and editing should be integrated with FSVeg Spatial tools.
REQ-1.3: Data Selection Capability
Requirement:
• Access different design-based inventory datasets which meet SIT criteria. Plot locations
must be in a geodatabase with an area of inference (Project Boundary and/or Estimation
Unit) and plot locations defined. Information is stored in password-protected Oracle SDE.
• Access spatial datasets, which are used for selecting an area of interest and for determining
its area, categories (spatial attributes), and/or post-stratification.
• Document how to access data using the SIT tool
Specifications:
•
SIT will be work with data in ATIM and their corresponding spatial location stored in
password protected Oracle SDE. In addition:,
o SIT can access temporally overlapping datasets. For example, if an area is selected
that has multiple cycles (remeasurements) of an inventory, SIT must be able to allow
the user to specify an attribute query and select which Subcycle(s) (or Measurement
Years) to use.
o SIT can access spatially overlapping datasets. For example, an independent inventory
of the same area could be used to improve population estimates. SIT would need to
be able to identify the source dataset (e.g., FIA and a Regional dataset) and the
sample dates of any plots selected. The two sources could be treated as a single
sample if the plot designs and sampling intensities are compatible. Alternatively, they
should be treated as two Estimation Units which can be combined using weights
specified by the user.
o
o SIT can access mid-cycle remeasurements. For example, SIT should be able to select
by attribute values a subset of plots that are remeasured 5 years into a 10-year cycle.
The population estimates would be based on that subset alone.
9
Page 9
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
•
•
SIT will access spatial datasets, which are used for selecting an area of interest and for
determining its area, categories (spatial attributes), and/or for post-stratification.
o SIT will be able to access pre-defined layers, such as those available through the
Geospatial Interface, including FIA Estimation Unit boundaries, FIA stratification
layers, or National Forest boundaries. Furthermore, plots that have had disturbance
since inventory data, based on information in the FACTS activity layer and MTBS
can be flagged and left out of analysis, if needed..
o SIT will allow user-defined polygons to be incorporated. Validation checks regarding
content and geospatial standards will be run against these polygons as part of its error
trapping routine.
o SIT will adhere to the law and policies relating to the use of confidential data
regarding plot ownership and location (coordinates). Work with FIA and NFS to
develop standards for storing FIA and intensified grid coordinates in a nationally
defined standard for use by SIT. Determine how FIA will distribute and update plot
locations over time.
Document the locations of the databases and their sources of documentation – for
example, see the FIADB documentation (http://fia.fs.fed.us/library/databasedocumentation/) ; for FSVeg
(http://fsweb.nris.fs.fed.us/products/FSVeg/documentation.shtml); or for FSVeg Spatial
(http://fsweb.nris.fs.fed.us/products/FSVeg_Spatial/documentation.shtml).
PREQ-1.4: Process New or Selected Polygons.
Requirement:
•
Allow user the ability to select plots based on user-created polygon(s) or a selected set of
existing polygons. A set of polygons may be selected on the screen, or based on a query
of their map attributes.
• Allow the user to intersect plots (and optionally mapped subplots) with standard spatial
layers to store spatial attributes, strata, and estimation units.
• Allow the user to buffer plots, then allow the user to check all plots manually that include
multiple conditions within the buffer. Need to repeat this check for each major layer,
such as ownership (Estimation Units), intensified strata, and Existing Veg layer.
Provide instructions on how to manage this process. Refer to Rules in section REQ-1.1
• In an attempt to capture spatial accuracy issues, allow the user to buffer plot locations by
some distance, then select those plots that do not fall within a single category (ownership,
etc), and then allow the user to select any of these flagged plots and individually select
which candidate attribute value to use in the analysis… Note that this process has a
potential of being very user-intensive, depending on the avg size of the polygon layer.
• Allow user the ability to add the selection polygon’s attributes to the selected plots. Eg.
Allow the selected watershed’s number to be attached to the selected plots.Allow user the
ability to optionally create new Estimation Unit(s) from a selected set of polygons or a
newly created polygon, and compute the area of each Estimation Unit. This process will
also create the POP tables needed for the new Estimation Unit.
• Allow user the ability to optionally specify a polygon or raster layers as Strata within
each Estimation Unit. These Strata will become part of the Estimation Unit and update
the POP tables
• Identify plots within each Estimation Unit and Stratum combination, Check for
minimum sample size and count plots that fall within each unit/stratum combination.
10
Page 10
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
•
Allow user the ability to optionally subset the data based on existing attributes.
Specifications:
• Using FSVeg Spatial ArcMap tools, select or create one or more polygons, then identify
all plots within the selection. Allow the user to select plots based on their map attributes,
such as Soil Series. Pass this list of plots to ATIM as a filter on the plots to use in
estimation (see REQ-1.6).
• Integrate with other applications (e.g., FSVeg Spatial, GI) to link the plot coordinates
with standard layers to store spatial attributes in the database.
o Access spatial datasets which are used temporarily for selecting an area of interest
and for determining its area, categories (spatial attributes), and/or post-stratification.
 Accept pre-defined, corporate layers, such as FACTS and ALP that are in
Oracle SDE.
 Accept user-defined polygons as long as they use corporate content and
geospatial standards.
 Intersect plots with standard layers, select one or more spatial attributes,
strata, and estimation units and store with the plots as a select description.
• SIT will be able to buffer plots, then allow the user to manually check all
plots that include multiple subplot conditions within the buffer. See
appendix XX
• Allow user the ability to query data to identify any plots outside the
polygon that might belong to the area of interest, such as using the
Administrative Forest Code, to identify NFS plots with coordinates
outside the ALP NFS boundary or ALP Ownership layer.
• This process will be repeated for each layer being used for plot selection.
• The FS will provide instructions on how to manage this process to the
software developers. See rules in REQ-1.1
o Link plots spatially and temporally with spatial layers, such as FACTS, ALP and
MTBS, to assist in assessing change.
 Identify those plots that may have changed since the time of inventory due to
disturbance (harvest, fire, hurricane, tornado, land exchange, insect and
disease infestation). Attribute the plot with a FACTS activity code and date
 Need to be able to synchronize a plot with a specific image date. Mostly this
would be on the fly, but also want to be able to update data based on known
change, such as land exchange. Else can add new field indicating the change,
such as burn year.
o Be able to integrate work processes with FSVeg Spatial. Pass plot information to
Watershed and other analysis tools.
• Allow user the ability to intersect plot locations with other corporate or user-provided
map layers not in the GI. Then allow the user to specify which, if any, of the polygon
attributes should be attached to the plots and passed to ATIM.Save the plot selection and
attributesUsing the polygons selected above, allow the user to create one or more
Estimation Units, which are defined as units of known. SIT will compute the Estimation
Unit area (in acres) and store in the feature class.
• If Estimation Units are defined above, then allow the user to further specify Strata, which
are map-based subdivisions of the Estimation Unit. Strata are used as a statistical tool to
subdivide the population into homogeneous groups to reduce variance of estimates for
11
Page 11
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
the Estimation Unit as a whole. For example, FIA may post-stratify the plots based on
classified satellite imagery. Also allow the user to select other classified raster or
polygon layers as strata. In either case, compute the area (in acres) of each Stratum
within each Estimation Unit, and create a list of plots within each combination.
• Need the ability to select the Sampling method for the selected plots. Such as Simple
Random Sampling, Stratified Random Sampling, Double Sampling for Stratification and
Post-stratification.
• Work with Core team to determine the specifications that NFS wants if a polygon has a
small number of plots. Allow user the ability to optionally subset data based on attributes
observed, such as P2 vs. P3, remeasured vs. new, or accessed vs. non-sampled, and to
create separate estimates for each.
REQ-1.5: SIT information passed directly to ATIM
Requirement:
•
•
After query is completed, pass the results to ATIM.
Allow the user to save, store and re-use the plot selection and the query.
•
Spatial intersection can produce two results:
o Spatial attributes can be associated with plot locations
o Analysis areas of interest, such as estimation units or strata.
Specifications:
•
•
•
•
•
•
•
After spatial intersection is completed, pass the results to query. ATIM. Results may be:
o spatial attributes associated with plot locations
o or estimation units or strata, including weights, to provide ability to derive
estimates associated with spatial datasets
Information passed depends upon user information need. All results will be associated
with the plot using a unique control number.
If the user wants one or more spatial attributes passed, then those attributes associated
with each of the selected plots, are sent to ATIM.
o Ability to store these attributes needs to be developed. These attributes may be
stored at the DataMart, or in NRIS FSVeg table to provide ability to use again.
If the user would like to derive estimates associated with spatial datasets and has created
Estimation Units and/or Strata of interest, then the Estimation Unit and/or Strata are
passed to ATIM to derive the estimates.
o .
The user may have also created multiple subsets based on the spatial resolution of the
plot (P2, P3, etc.) or on year (Subcycle). These results must be exported to ATIM.
The information presented to the analytical tool passed can be handled in at least two
ways. ATIM will use the results to update the FSVeg database, where the results will be
passed to FSVeg directly to create POP tables. All other users will pass the information
available to ATIM. The format of this information will need to be coordinated with the
ATIM developers, but must contain sufficient information for ATIM to optionally add
records with metadata to the POP tables (much as was the case for the Data Processor).
One possible solution is to have temporary table space to store the POP table information
– either on the server or on the user’s PC.
SIT will pass the data directly to the chosen application tool and execute the query.
Once the selections have been made, then the user should be able to click on a SIT
12
Page 12
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
button to open up ATIM and have it execute the query. All the EVALIDs should be
listed for the selection. If only one (the default), then it should be automatically selected.
The user can then customize which tables to create using ATIM.
REQ-1.6: Process Data
Requirements:
• Use FSVeg Spatial to link the plot coordinates with standard layers to store spatial
attributes in the database.
• Using the mapped data from above, store derived variables such as FVS output.
• Store metadata for each of the items above.
• Integrate with FSVeg by providing dataupdates to be stored in FSVeg.
• Document Process and a USER Guide.
Specifications:
• Integrate with other applications (e.g., GI) to link the plot coordinates with standard layers
to store standard spatial attributes in the database, such as Congressional District and
EcoSubsection (see REQ-1.2). Then store them for future (and repeated) use.
• Store additional attributes as needed.
• Identify where population and post-stratification information will be stored. Integrate with
other NFS applications by providing data to them
o Ensure that SIT can export tabular and spatial data in formats that can be used by the
other tools such as Access and Excel.
• Store results of intersections at the plot level (and/or subplot/condition level) for later use,
such as determining burned plots. In addition to passing the query to ATIM, allow the user
to store the final list of selected plots as a layer (e.g., shape file) or in a temporary table on
the server or on their PC
• Calculate and store estimation units and map attributes for each plot. Must be able to store
the results so that the calculations can be validated, and re-used for efficiency.
• Document the process of intersecting plots and spatial layers and storing the spatial
attributes.
o Write users guide including a glossary (such as the one in the Appendix).
o Create metadata for data stored in database, including a data dictionary with the
algorithms and functions used. See FGDC metadata requirements for spatial data.
o Create and keep current an update log.
o Create a log file for each on-the-fly run containing a variety of information, including
the version of the program, database, query and on-the-fly functions.
o Look for means of making similar queries run quickly, such as creating checks to see
if the query is being run under the same conditions.
• Display query results spatially using one of two methods.
o ATIM will send the tabular estimates back to SIT to dfor use in displaying maps such
as Counties or other strata. Allow the user to specify the ranges and colors.
o Display maps directly in ATIM (not part of SIT requirements, other than perhaps to
send the Estimation Unit or Strata shape files).
• Document the process of querying the data to produce estimates and mapped output.
13
Page 13
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
•
o Write users guide.
o Create a log file for each on-the-fly run containing a variety of information, including
the version of the program, database, query and on-the-fly functions. Consider
creating checks to see if the query is being run under the same conditions.
Pass plot selection to the Complier program. Also select the Estimation Unit and Strata to
use in the Compiler program.
REQ-1.7: Administrator Management Capabilities
Requirement:
• Create and maintain profiles to allow access to secure plot locations, compiling data, and
then sending the data to the DataMart
• Develop and enforce rules for each Profile level
• Need to describe the creation, naming and editing processes for the source database, the
summary data, additional data fields, and any temporary files.
• Ensure that the public does not have access to secure information (actual coordinates and
ownership data)
• Manage multiple dataset versions
Specifications:
• Work with NRIS developers to create and maintain user profiles for both applications.
Profiles will be created for various roles (see Use Cases) and for the following categories:
o Public
o Cooperators
o Other Agencies
o Local
o Regional
• Develop and enforce rules for each Profile level
• Need to address data management for the source database, the summary data, additional
data fields, and any temporary files.
• Ensure that the public and most users do not have access to secure information (actual
coordinates and ownership data). See REQ-1.2 for statements on the use of actual
coordinates.
• Manage multiple dataset versions
o Need to be able to create snapshots of databases in time, so it can ensure that a team
involved with project level NEPA or a Forest Plan revision or amendment, are
consistently using the same data (e.g. snapshot).
o Need to address updates to NFS database vs. FIA’s version depending on which
databases are used.
14
Page 14
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
4. External Interface Requirements
4.1 User Interfaces
The application will be developed according to the NRIS User Interface Standards. Detailed
information about these standards can be found at:
http://fsweb.nris.fs.fed.us/Standards_and_References/User_Interface_Standards/index.shtm
l
4.2 Hardware Interfaces
SIT will operate in at least two different hardware configurations. First, SIT will be in the
Geospatial Interface in the Data Center environment (National Information Technology
Center – NITC). As noted in 2.4, it will use back end Oracle servers (Linux or similar
Operating System) and a Citrix farm to serve the client interface. Second, SIT will operate as
an extension in ArcMap in a PC Windows operating system, then link with ATIM.
4.3 Software Interfaces
SIT operate within ArcMap and will interface with ATIM. It will connect with the FSVeg
database via the Geospatial Interface (GI), and user data within ArcMap. SIT and ATIM
should all be stand-alone, but easily linked so that users can invoke one from the other.
4.4 Communication Interfaces
When operating within the Geospatial Interface or on a PC with ArcMap, SIT will
communicate within the Forest Service firewall via intranet and outside the firewall via the
internet, and similarly with ATIM. When using SIT ATIM on a PC, there is no external
communication.
5. Other Requirements
5.1 Performance Requirements
- Ability to operate this system in a reasonable (TBD) amount of time.
Queries for a Forest should take no more than 3 minutes.
5.2 Safety Requirements
There are no known safety requirements
5.3 Security Requirements


Keberos
E-Authorization
15
Page 15
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring


This project does not access or manipulate sensitive data.
This project conforms to the agency Computer Security Rules of Behavior which can be
found at:
http://fsweb.nris.fs.fed.us/rulesofbehavior.shtml
5.4 Software Quality Attributes
There are no additional software quality attributes.
6. Citations
BECHTOLD, W.A. and P.L. PATTERSON. 2005. The enhanced Forest Inventory and Analysis
program--national sampling design and estimation procedures. General Technical Report SRS80. U.S. Department of Agriculture, Forest Service, Southern Research Station, Asheville, NC.
85 p. http://www.srs.fs.usda.gov/pubs/20371.
16
Page 16
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
Appendix A: Acronyms
ALP
Automated Lands Project
ATIM
Analytical Tool for Inventory and Monitoring
COTS
commercial-of-the-shelf
CVS
current vegetation survey
DFC
desired future conditions
DTIM
Design Tool for Inventory and Monitoring
FIA
Forest Inventory and Analysis
FIADB
FIA’s database
FIDO
FIA Forest Inventory Data Online
FGDC
Federal Geographic Data Committee
FSNRAs Forest Service Natural Resource Applications
FVS
Forest Vegetation Simulator
GI
Geospatial Interface, an NRIS application which allows…
GIS
Geographic Information System
I&M
Inventory and Monitoring
MOU
Memorandum of Understanding
NIMS
National Information Management System
NFS
National Forest System
NITC
National Information Technology Center
NRCS
Natural Resource Conservation Service
NRIS
National Resource Information System
OCIO
Office of the Chief Information Officer
R1
Region 1, U.S. Department of Agriculture, Forest Service, Northern Region
R2
Region 2, U.S. Department of Agriculture, Forest Service, Rocky Mountain Region
R3
Region 3, U.S. Department of Agriculture, Forest Service, Southwestern Region
R4
Region 4, U.S. Department of Agriculture, Forest Service, Intermountain Region
R5
Region 5, U.S. Department of Agriculture, Forest Service, Pacific Southwest Region
17
Page 17
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
R6
Region 6, U.S. Department of Agriculture, Forest Service, Pacific Northwest Region
R8
Region 8, U.S. Department of Agriculture, Forest Service, Southern Region
R9
Region 9, U.S. Department of Agriculture, Forest Service, Eastern Region
R10
Region 10, U.S. Department of Agriculture, Forest Service, Alaska Region
NRS
Northern Research Station
SRS
Southern Research Station
RMRS
Rocky Mountain Research Station
PNW
Pacific Northwest Research Station
PSW
Pacific Southwest Research Station
TBD
To be determined
WAN
Wide area network
18
Page 18
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
Appendix B. Glossary
For some terms, one or more definitions are given, and often more than one is in common usage.
accuracy The degree to which a measured quantity approaches the true value of what is being
measured (Lincoln et al. 1998).
analytical (1) Of or relating to analysis or analytics. (2) Separating into elemental parts or
basic principles. (3) Reasoning from a perception of the parts and interrelations of a subject.
(Webster 1984).
association A physiognomically uniform group of existing vegetation stands that share
dominant overstory and understory species. These occur as repeatable patterns across the
landscape (adapted from FGDC 1997).
attribute A discrete or continuous variable, usually associated with the classification or
measurement of area or vegetation (Bechtold, Patterson 2005).
business needs Ongoing tasks related to a particular business or project and the information
and other support contributing to the completion of these tasks (Brohman and Bryant 2005).
basal area/ac The cross-sectional area of a single stem, including the bark, measured at breast
height (4.5 ft or 1.37 m above the ground) per acre (adapted from Helms 1998).
biofuels
The fuel component of biomass (adapted from Helms 1998).
biomass (1) Ecology the total dry organic matter at a given time of living organisms of one or
more species per unit area (species biomass) or of all the species in the community (community
biomass). (2) The living or dead weight of organic matter in a tree, stand, or forest in units such
as living or dead weight, wet or dry weight, ash-free weight, etc. (3) Harvesting the wood
product obtained (usually) from in-woods chipping of all or some portion of trees including
limbs, tops, and unmerchantable stems, usually for energy production (Helms 1998).
buffer (1) A vegetation strip or management zone of varying size, shape, and character
maintained along a stream, lake, road, recreation site, or different vegetative zone to mitigate the
impacts of actions on adjacent lands, to enhance aesthetic values, or as a best management
practice— synonym buffer strip, buffer zone. (2) GIS a zone of a specified distance around
features (Helms 1998).
Citrix Software that enables organizations to securely access Windows-based line-of-business
applications over the Internet with just a Web browser. The software makes centrally maintained
information and applications easy to update and retrieve from just about anywhere.
19
Page 19
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
classification (1) The process of grouping similar entities into named types or classes based on
shared characteristics. (2) The grouping of similar types (in this case, vegetation) according to
criteria (in this case, physiognomic and floristic) that are considered significant for this specific
purpose. The rules for classification must be clarified before the types are identified in the
classification standard. The classification methods should be clear, precise, quantitative where
possible, and based on objective criteria so that the outcome will be the same no matter who
developed the definition (or description). Classification by definition involves definition of class
boundaries (FGDC 1997, citing UN-EP/FAO 1995).
coordinates In mapping, pairs of numbers that express horizontal distances along orthogonal
axes; or, triplets of numbers measuring horizontal and vertical distances (FGDC 1998).
dataset Collection of related data. See also geospatial data (USDA Forest Service 2004).
desired future condition (DFC) A description of the land or resource conditions that are
believed necessary if goals and objectives are fully achieved (Helms 1998)
down woody material Dead pieces of wood > 3.0 inches in diameter. Down woody material
includes downed, dead tree and shrub boles, large limbs, and other woody pieces that are severed
from their original source of growth or are leaning more than 45 degrees from vertical (Bechtold,
Patterson 2005).
dominance The extent to which a given species has a strong influence in a community because
of its size, abundance, or coverage. Strong dominance affects the fitness of associated species
(adapted from Lincoln et al. 1998).
E-Authentication USDA e-Authentication account identification consists of a User ID, a
password, and a customer profile that enables one to access a range of USDA applications. It
provides the convenience of transacting business with USDA online, anytime, anywhere.
ecoregion A contiguous geographic area having a relatively uniform macroclimate, possibly
with several vegetation types, and used as an ecological basis for management or planning
(Helms 1998).
ecosystem A complete interacting system of organisms and their environment (USDA Forest
Service 1991).
evaluation The comparison of dynamic sampling results to management objectives consisting
of predetermined standards, expected norms, threshold values, and/or trigger points (Brohman
and Bryant 2005).
Federal Geographic Data Committee (FGDC) An interagency committee, organized in 1990
under the Office of Management and Budget (OMB) Circular A-16 that promotes the
coordinated use, sharing, and dissemination of geospatial data on a national basis. The FGDC is
20
Page 20
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
composed of representatives from 17 Cabinet-level and independent Federal agencies (USDA
Forest Service 2004).
GeoDB An ArcGIS geodatabase is a collection of geographic datasets of various types held in
a common file system folder, a Microsoft Access database, or a multiuser relational database
(such as Oracle, Microsoft SQL Server, or IBM DB2).
geographic information system (GIS) The term frequently applied to geographically oriented
computer technology. In its broadest sense, GIS is a system for capturing, storing, checking,
manipulating, analyzing, and displaying data that are spatially referenced to the Earth
(Lachowski et al. 1996).
geospatial data Information that identifies the geographic location and characteristics of
natural or constructed features and boundaries on the earth. This information may be derived
from remote sensing, mapping, and surveying technologies (FGDC 1998).
Geospatial Interface (GI) Geospatial Interface (GI) is an ArcMap extension that helps
resource specialist’s work efficiently with ArcMap by providing tools which simplify loading
data and providing various custom products to display and output data.
grid (1) A set of grid cells forming a regular, or nearly regular, tessellation of a surface. (2) Set
of points arrayed in a pattern that forms a regular, or nearly regular, tessellation of a surface. The
tessellation is regular if formed by repeating the pattern of a regular polygon, such as a square,
equilateral triangle, or regular hexagon. The tessellation is nearly regular if formed by repeating
the pattern of an “almost” regular polygon such as a rectangle, nonsquare-parallelogram, or
nonequilateral triangle (FGDC 1998).
interface computers A hardware and software link that connects two computer systems, or a
computer and its peripherals, for data communication (Helms 1998).
invasive species A species that is 1) non-native (or alien) to the ecosystem under consideration
and 2) whose introduction causes or is likely to cause economic or environmental harm or harm
to human health. Invasive species can be plants, animals, and other organisms (e.g., microbes).
Human actions are the primary means of invasive species introductions (NISIC 2006).
inventory The systematic acquisition, analysis, and organization of resource information
needed for planning and implementing land management (adapted from USDA NRCS 1997).
iterative (1) Marked by or involving repetition. (2) math of, relating to, or being a
computational procedure to produce a desired result by replication of a series of operations that
successively better approximates the desired result (Webster 1984).
21
Page 21
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
map (1) A spatial representation, usually graphic on a flat surface, of spatial phenomena
(FGDC 1998). (2) A representation, usually on a plane surface, of a region of the Earth or
heavens (Robinson et al.1978).
map scale The extent of reduction required to display a portion of the Earth’s surface on a
map; defined as a ratio of distances between corresponding points on the map and on the ground
(Robinson et al. 1978). Scale indirectly determines the information content and size of the area
being represented. The mapping scale is determined by the agency’s business needs and the
characteristics of the data obtained for the project area. Maps generated from digital imagery can
appropriately be displayed at a range of scales (Brohman and Bryant 2005).
map unit A collection of features defined and named the same in terms of their vegetation
characteristics (USDA Soil Survey Division Staff 1993). Each map unit differs in some respect
from all others in a geographic extent. Map units are differentiated in map unit design and
defined in a map unit description. Design of map units generalizes the taxonomic units present to
the smallest set that (1) meets the objectives of the map, and (2) is feasible to delineate with
available resources and technology (Brohman and Bryant 2005).
media The physical devices used to record, store, and (or) transmit data (FGDC 1998).
metadata Refers to “data about data”; describes the content, quality, condition, and other
characteristics of a given set of data. Its purpose is to provide information about a dataset or
some larger data holdings to data catalogues, clearinghouses, and users. Metadata is intended to
provide a capability for organizing and maintaining an institution’s investment in data to provide
information for the application and interpretation of data received through a transfer from an
external source (Jennings et al. 2004, as modified from FGDC 1997).
modeling In reference to geospatial data, the process of creating a new GIS layer by
combining or operating on existing layers. Modeling creates images) that contain several types of
information comprising several GIS variables; e.g., a scene may be considered in terms of its
vegetation, elevation, water, and climate at the same time (Lachowski et al. 1996).
monitoring (1) The systematic collection, analysis, and interpretation of resource data to
evaluate progress toward meeting management objectives (adapted from SRM 1989). (2) The
collection and analysis of resource data to measure changes in the amounts, spatial distribution,
or condition of resource types or parameters over time (Brohman and Bryant 2005).
nearest neighbor (neighbour) method A method of plotless sampling of populations in which
the distance is measured from an individual (chosen on the basis of its proximity to a randomly
selected point) to its nearest neighbour, and the procedure repeated; population density estimates
can be based on these measurements as for example, by the formula m=1/4r2 where m is the
22
Page 22
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
mean density per unit area and r is the mean distance between nearest neighbours (Lincoln et el.
1998).
National Information Technology Center (NITC) Is part of the Office of the Chief
Information Officer (OCIO) for the USDA. The mission of NITC is to provide reliable and costeffective Information Technology Solutions to achieve effective mission performance delivery
for the USDA, its agencies, and others.
physiognomic class A level in the classification hierarchy defined by the relative percent
canopy cover of the tree, shrub, dwarf shrub, herb, and nonvascular life-form in the uppermost
strata during the peak of the growing season (FGDC 1997).
post-stratification
(see stratification).
A statistical tool used to sort existing plots into a particular stratification
Robo Help A software program that assists in implementing on-line customer help by linking
directly to the appropriate part of the electronic User Guide.
SDE ESRI interface between RDBMS and the ESRI line of GIS display systems, including
ArcGIS, ArcGIS Engine, ArcGIS Server, and ArcIMS. SDE works with a type of data called
FEATURES and RASTERS contained in GeoDataBases, in comparison with previous ESRI
architectures of COVERAGES or SHAPEFILES that represented points, lines and polygons, and
GRIDS that represented surfaces.
spatial data Data that record the geographic location and shape of geographic features and
their spatial relationships to other features (USDA Forest Service 2004).
species In biological classification, the category below genus and above the level of subspecies
and variety; the basic unit of biological classification (adapted from Lincoln et al. 1998).
strata Nonoverlapping subdivisions of the population such that each primary sampling unit is
assigned to one and only one subdivision (or stratum). The relative sizes of these strata are used
to compute strata weights (Bechtold, Patterson 2005).
stratification A statistical tool used to reduce the variance of the attributes of interest by
partitioning the population into homogenous strata. It may also involve partitioning a highly
variable but small portion of the population (Bechtold, Patterson 2005).
stratum In general, one of a series of layers, levels, or gradations in an ordered system. In the
natural environment, the term is used in the sense of (1) a region of sea, atmosphere, or geology
that is distinguished by natural or arbitrary limits, or (2) a layer of vegetation, usually of the
same or similar height (adapted from FGDC 1998).
23
Page 23
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
tabular data Data that describe things using characters and numbers formatted in columns and
rows (USDA Forest Service 2004).
trees Woody plants that generally have a single main stem and have more or less definite
crowns. In instances where life form cannot be determined, woody plants at least 5 meters in
height are considered trees (FGDC 1997).
understory All forest vegetation growing under an overstory (Helms 1998).
Use Case Descriptions of the major functions that the system will perform for external actors,
and also the goals that the system achieves for those actors along the way.
vegetated Areas having at least 1 percent or more of the land or water surface with live
vegetation cover at the peak of the growing season (FGDC 1997).
vegetation The total plant life or cover in an area; also used as a general term for plant life; the
assemblage of plant species in a given area; cf. faunation (Lincoln et al. 1998).
volume table A listing showing, for one or more species, the average cubic or merchantable
contents of trees or logs according to easily measured tree dimensions, such as tree diameter or
height—note such tables are constructed from samples of felled trees or from detailed thee
dimensional data, and are used for estimating the timber contents of either individual trees or
stands (Helms 1998).
Glossary References
Bechtold, W.A.; Patterson, P.L. eds. 2005. The enhanced forest inventory and analysis
program—national sampling design and estimation procedures. Gen. Tech. Rep. SRS-80.
Asheville, NC: U.S. Department of Agriculture Forest Service, Southern Research Station. 85 p.
Brohman, R.; Bryant, L. eds. 2005. Existing Vegetation Classification and Mapping Technical
Guide. Gen. Tech. Rep. WO–67. Washington, CD: U.S Department of Agriculture Forest
Service, Ecosystem Management Coordination Staff. 305 p.
Federal Geographic Data Committee (FGDC)—Vegetation Subcommittee. 1997. Vegetation
classification standard. FGDC-STD-005. Reston, VA: Federal Geographic Data Committee, U.S.
Geological Survey [online]. Available: http://www.fgdc.gov/standards/projects/FGDCstandards-projects/vegetation/vegclass.pdf [February 2, 2009].
Federal Geographic Data Committee (FGDC). 1998. Content standard for digital geospatial
metadata. FFGDC-STD-001-1998. Reston, VA: Federal Geographic Data Committee. U.S.
Geological Survey [online]. Available: http://www.fgdc.gov/standards/projects/FGDCstandards-projects/metadata/base-metadata/v2_0698.pdf. [February 2, 2009].
24
Page 24
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
Helms, J.A., editor. 1998. The dictionary of forestry. Bethesda, MD: Society of American
Foresters.
Jennings, M.; Faber-Iangendoen, D.; Peet, R.; et al. 2004. Guidelines for describing associations
and alliances of the U.S. national vegetation classification. Version 3.0. Vegetation Classification
Panel. Washington, DC: Ecological Society of America.
Lachowski, H.J.; Powell, T.; Wirth, P.; et al. 1996. Monitoring aspen decline using remote
sensing and GIS: Gravelly mountain landscape, southwestern Montana. Dillon, MT: U.S.
Department of Agriculture, Forest Service, Beaverhead-Deerlodge National Forest.
Lincoln, R.J.; Boxshall, G.A.; Clark, P.F. 1998. A dictionary of ecology, evolution and
systematics. 2nd ed. New York: Cambridge University Press, USA.
National Invasive Species Information Center (NISIC) 2006. U.S. Department of Agriculture,
National Agricultural Library. Definition submitted by the definitions subcommittee of the
Invasive Species Advisory Committee (ISAC). Aproved by ISAC April 27, 2006 [online].
Available: http://www.invasivespeciesinfo.gov/whatis.shtml [February 3, 2009].
Robinson, A.H.; Sale, R.; Morrison, J.L. 1978. Elements of cartography. 4th ed. New York: John
Wiley & Sons.
U.S. Department of Agriculture (USDA), Forest Service. 1991a. FSH 2090.11—Ecological
classification and inventory handbook. Missoula, MT: Department of Agriculture, Forest
Service, Northern Region.
U.S. Department of Agriculture (USDA), Forest Service. 1991b. FSM 2060—Ecosystem
Classification, Interpretation, and Application. Washington, DC: Department of Agriculture,
Forest Service.
U.S. Department of Agriculture (USDA), Natural Resource Conservation Service (NRCS). 1997.
National range and pasture handbook. Washington, DC: U.S. Department of Agriculture, Natural
Resources Conservation Service.
U.S. Department of Agriculture (USDA), Forest Service. 2004. Forest Service metadata users
guide—metadata terms and definitions. Washington, DC: U.S. Department of Agriculture, Forest
Service, Geospatial Advisory Committee [online]. Available:
http://www.fs.fed.us/gac/metadata/glossary.html [February 3, 2009].
Webster’s II new Riverside university dictionary. 1984. Boston, MA: The Riverside Publishing
Company. 1536 p.
25
Page 25
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
Appendix C
Need to add the FIA plot layout and difference in condition classes
26
Page 26
Software Requirements Specification for the Analytical Tool for Inventory & Monitoring
Page 28
Appendix D: Analysis Models
Analysis Tool for Inventory and Monitoring
(2)
Summarization
Process
(1)
“Raw” Inventory
Data - Tree lists
coming from FIA,
R1, CVS, R5,
etc.
(8)
Spatially intersect
(9)
“Corporate” (i.e.,
Standard) Spatial
Data Layers - Raster
or Polygon - e.g.,
State, HUCs, etc
(4)
“Compiled”
Inventory Data
- Summarized
at plot / subplot
level - e.g. BA,
Vol., TPA
(3)
Classification
Algorithms
(5)
“Classified”
Inventory Data Summarized at
plot / subplot level
- e.g., Forest
Type, Dom. Type,
Old Growth,
Wildlife Habitat
(23)
Spatial output of
standar errors for
each of the
Areas of Interest
and Total Area
(10)
“Raw”
Inventory Data
with / attributes
from spatial
layer
(12)
User-defined
Spatial Data
Layers - Raster or
Polygon
(11)
Summary
Database w /
attributes from
spatial layers
(13)
Spatially intersect Other spatial output
(15)
Subset of the “Raw”
Inventory data Attributed with userdefined Area of
Interest code
(14)
Spatial Data
Output - Point or
Polygon
(20)
Spatial output of
estimates for
each of the
Areas of Interest
and Total Area
(7)
“Summary
Database” plot / subplot
(6)
Merge Tables
(16)
Table of Area
for each
user-defined
area of
interest
(18)
Estimation Process
(22)
Estimates and
Standard Errors
for each of the
Areas of Interest
and Total Area
(21)
Join tabular
estimaes with
spatial data
28
(17)
Subset of the
Summary Database
- Attributed with
user-defined Area
of Interest code
(19)
Spatial Data
Output - Point or
Polygon