Decision Support Systems for Ecosystem Management: An Evaluation of Existing Systems
Presents the results of a questionnaire that was designed to evaluate existing decision support systems in an ecosystem management context. The questionnaire was distributed to developers of 24 decision support systems in the government, academic, & private sectors. This evaluation is intended to assist current & potential users of decision support systems in determining which existing system most closely fulfills their needs. It is also intended to encourage cooperation among developers of decision support systems to more effectively unify & fulfill these criteria in future systems.
What people are saying - Write a review
We haven't found any reviews in the usual places.
activity log aggregated allocative analyze alternatives spatially Arc/Info and Oracle ArcForest ArcView ASCII clean data coefficients or knowledge corporate data structures cover type CRBSUM current status data input data lineage data required data sets data transformed database Default coefficients designed Desired Future Conditions differences among prescriptive different scales disk storage documentation economic ecosystem ESRI evaluate examples or choices expected values files Fire-BGC Forest Service fuzzy logic graphs habitat IMPLAN incomplete data inductive reasoning INFORMS landscape levels linear programming Loki maintenance costs minimum CPU Minnesota IMPLAN Group monitoring National Forest NEPA Criteria operating systems planning predict future conditions provide examples reports rulebases run with incomplete Scope and Capabilities self-training is feasible sensitivity analysis simulation Spatial scale specific stochastic system run Terra Vision tool typical applications Unix USDA-FS user manuals User Support users required vegetation visualization Woodstock X X X
Page 39 - USDA Forest Service, Intermountain Research Station, Intermountain Fire Sciences Laboratory, Missoula, MT.
Page 38 - Ecological processes that act at a landscape level, such as lire and seed dispersal, are simulated annually from stand and topographic Information. Stand-level processes, such as tree establishment, growth and mortality, organic matter accumulation and decomposition, and undergrowth plant dynamics are simulated both daily and annually. Tree growth is mechanistically modeled...
Page 38 - FIRE-BGC is an individual tree model created by merging the gap-phase, process-based model FIRESUM with the mechanistic ecosystem biogeochemical model FOREST-BGC. It has mixed spatial and temporal resolution in the simulation architecture.
Page 29 - The next line has information on the first PVT where the first cover type might occur. The PVT ID, name and number of structural stages found in this cover type and PVT combination are then entered on this record in that order. This next set of records contains information on all structural stages that can occur in this PVT/cover type.
Page 30 - These maps are imported to Loki from GIS software prior to CRBSUM execution (Bevins and Andrews 1994, USA CERL 1990). The first map is the Management Region Map (Loki map Mgtregion) that delineates those areas that will receive different sets of disturbance probabilities. CRBSUM uses the Management Region Map to define the effective simulation area.
Page 28 - ID numbers) specified in each file must be consistent across and within files. For instance, if the Dry Douglas-fir PVT in the Succession File is assigned an ID number of 12, then the Dry Douglas-fir PVT in the Scenario File must also have an ID of 12. Simulation File — The first line in the Succession File is a title line used for file documentation and is skipped by CRBSUM.
Page 93 - Model (NED) uses an original prescription design system to incorporate management goals for multiple objectives, analyze current forest conditions, produce recommendations for management alternatives, and predict future conditions under different alternatives. NED...
Page 29 - Geographical regional information is entered on the next record with region ID entered first, region name entered next, then number of LandUnits involved in the management action. LandUnit information is entered on the next line with PVT ID number entered first, then the PVT name, the Succession Class number, and lastly, the number of possible disturbances involved at this level.