Difference between revisions of "Esc"
(Created page with 'General System description System name: Ecological Site Classification Acronym: ESC [edit] Brief overview The system enables the appropriate choice of tree species or NVC wood...') |
|||
Line 1: | Line 1: | ||
− | General System description | + | '''General System description''' |
− | System name: Ecological Site Classification Acronym: ESC | + | |
+ | '''System name: Ecological Site Classification ''' | ||
+ | |||
+ | '''Acronym: ESC''' | ||
+ | |||
+ | '''Brief overview''' | ||
− | |||
The system enables the appropriate choice of tree species or NVC woodland type on the basis of site climate and soil quality. Built into the tool are methods to assess soil quality from soil type and indicator plants. | The system enables the appropriate choice of tree species or NVC woodland type on the basis of site climate and soil quality. Built into the tool are methods to assess soil quality from soil type and indicator plants. | ||
− | Contents | + | '''Contents''' |
− | 1 General System description | + | |
− | 1.1 Brief overview | + | '''1 General System description''' |
− | 1.2 Scope of the system | + | |
+ | '''1.1 Brief overview''' | ||
+ | |||
+ | '''1.2 Scope of the system''' | ||
+ | |||
+ | '''1.3 System origin''' | ||
− | |||
The system was developed in the 1990s but the origins can be traced to a publication by Anderson in the 1950s and earlier works that identified relationships between site quality and vegetation. | The system was developed in the 1990s but the origins can be traced to a publication by Anderson in the 1950s and earlier works that identified relationships between site quality and vegetation. | ||
− | 1.4 Support for specific issues | + | '''1.4 Support for specific issues''' |
− | 1.5 Support for specific thematic areas of a problem type | + | '''1.5 Support for specific thematic areas of a problem type''' |
− | 1.6 Capability to support decision making phases | + | '''1.6 Capability to support decision making phases ''' |
− | 1.7 Related systems | + | '''1.7 Related systems''' |
+ | |||
Establishment management information system (EMIS) | Establishment management information system (EMIS) | ||
− | 2 Data and data models | + | '''2 Data and data models''' |
− | 2.1 Typical spatial extent of application | + | '''2.1 Typical spatial extent of application''' |
− | ESC can be applied at stand level via a web interface or landscape scape via a GIS batch tool, assuming suitable data exist. | + | |
+ | ESC can be applied at stand level (1 hectare) via a web interface or landscape scape via a GIS batch tool, assuming suitable data exist. | ||
+ | |||
+ | '''2.2 Forest data input''' | ||
− | |||
The inputs are site location, which derives climate data from a database (and very coarse resolution soil data). | The inputs are site location, which derives climate data from a database (and very coarse resolution soil data). | ||
− | 2.3 Type of information input from user (via GUI) | + | '''2.3 Type of information input from user (via GUI)''' |
+ | |||
Ideally the user supplies the results of a soil survey and on site vegetation. | Ideally the user supplies the results of a soil survey and on site vegetation. | ||
− | 3 Models | + | '''3 Models''' |
− | 3.1 Forest models | + | |
+ | '''3.1 Forest models''' | ||
+ | |||
Uses species suitability models and various tools to calculate soil properties from plants and/or soil profile information. | Uses species suitability models and various tools to calculate soil properties from plants and/or soil profile information. | ||
− | 3.2 Social models | + | '''3.2 Social models''' |
+ | |||
n/a | n/a | ||
− | 4 Decision Support | + | '''4 Decision Support''' |
− | 4.1 Typical temporal scale of application | + | |
+ | '''4.1 Typical temporal scale of application ''' | ||
+ | |||
Has limited capability to project suitability indexes into future climates to 2080. | Has limited capability to project suitability indexes into future climates to 2080. | ||
− | 4.2 Types of decisions supported | + | '''4.2 Types of decisions supported''' |
+ | |||
+ | Planning decisions eg | ||
+ | |||
Tree species to plant on site. | Tree species to plant on site. | ||
Site type/quality assessments. | Site type/quality assessments. | ||
− | 4.3 Decision-making processes and models | + | '''4.3 Decision-making processes and models''' |
+ | |||
+ | '''5 Output''' | ||
− | 5 | + | '''5.1 Types of outputs''' |
− | |||
Species suitability responses against climate and soil factors. | Species suitability responses against climate and soil factors. | ||
− | 5.2 Spatial analysis capabilities | + | '''5.2 Spatial analysis capabilities''' |
+ | |||
GIS visualisation available via offline batch tool. | GIS visualisation available via offline batch tool. | ||
− | 5.3 Abilities to address interdisciplinary, multi-scaled, and political issues | + | '''5.3 Abilities to address interdisciplinary, multi-scaled, and political issues''' |
+ | |||
Can identify sites for restoration to pre afforestation status. | Can identify sites for restoration to pre afforestation status. | ||
− | 6 System | + | '''6 System''' |
− | 6.1 System requirements | + | '''6.1 System requirements ''' |
+ | |||
Stand tool - user requires web browser ( tested on IE6 and Firefox ) | Stand tool - user requires web browser ( tested on IE6 and Firefox ) | ||
− | 6.2 Architecture and major DSS components | + | '''6.2 Architecture and major DSS components''' |
− | Three tier architecture facilitating desktop or server deployment. Key components are web UI, model codes and data. | + | |
+ | Three tier architecture facilitating desktop or server deployment. Key components are web UI, batch UI, model codes and data. | ||
− | 6.3 Usage | + | '''6.3 Usage''' |
+ | |||
Utilised by forest planners in public/private sector, students and researchers. | Utilised by forest planners in public/private sector, students and researchers. | ||
− | 6.4 Computational limitations | + | '''6.4 Computational limitations''' |
+ | |||
Very light to run, but can take sometime to process large quantites of data. | Very light to run, but can take sometime to process large quantites of data. | ||
− | 6.5 User interface | + | '''6.5 User interface''' |
− | + | ||
− | 6.6 Documentation and support | + | Stand tool uses HTML/CSS. Command line batch mode to generate GIS results and GIS extension to ArcView. |
+ | |||
+ | '''6.6 Documentation and support''' | ||
+ | |||
In development, support via FC training courses and bulletin. | In development, support via FC training courses and bulletin. | ||
− | 6.7 Installation | + | '''6.7 Installation''' |
+ | |||
Web browser for stand version. GIS batch tool requires Java 1.4, Grass and related ESC datasets. | Web browser for stand version. GIS batch tool requires Java 1.4, Grass and related ESC datasets. | ||
Server installation requires J2EE server such as Tomcat or Oracle Application Server and an oracle database. | Server installation requires J2EE server such as Tomcat or Oracle Application Server and an oracle database. | ||
− | 7 References | + | '''7 References''' |
− | 7.1 Cited references | + | |
− | 7.2 External resources | + | '''7.1 Cited references''' |
+ | |||
+ | '''7.2 External resources''' | ||
Revision as of 11:30, 10 July 2009
General System description
System name: Ecological Site Classification
Acronym: ESC
Brief overview
The system enables the appropriate choice of tree species or NVC woodland type on the basis of site climate and soil quality. Built into the tool are methods to assess soil quality from soil type and indicator plants.
Contents
1 General System description
1.1 Brief overview
1.2 Scope of the system
1.3 System origin
The system was developed in the 1990s but the origins can be traced to a publication by Anderson in the 1950s and earlier works that identified relationships between site quality and vegetation.
1.4 Support for specific issues
1.5 Support for specific thematic areas of a problem type
1.6 Capability to support decision making phases
1.7 Related systems
Establishment management information system (EMIS)
2 Data and data models
2.1 Typical spatial extent of application
ESC can be applied at stand level (1 hectare) via a web interface or landscape scape via a GIS batch tool, assuming suitable data exist.
2.2 Forest data input
The inputs are site location, which derives climate data from a database (and very coarse resolution soil data).
2.3 Type of information input from user (via GUI)
Ideally the user supplies the results of a soil survey and on site vegetation.
3 Models
3.1 Forest models
Uses species suitability models and various tools to calculate soil properties from plants and/or soil profile information.
3.2 Social models
n/a
4 Decision Support
4.1 Typical temporal scale of application
Has limited capability to project suitability indexes into future climates to 2080.
4.2 Types of decisions supported
Planning decisions eg
Tree species to plant on site. Site type/quality assessments.
4.3 Decision-making processes and models
5 Output
5.1 Types of outputs
Species suitability responses against climate and soil factors.
5.2 Spatial analysis capabilities
GIS visualisation available via offline batch tool.
5.3 Abilities to address interdisciplinary, multi-scaled, and political issues
Can identify sites for restoration to pre afforestation status.
6 System 6.1 System requirements
Stand tool - user requires web browser ( tested on IE6 and Firefox )
6.2 Architecture and major DSS components
Three tier architecture facilitating desktop or server deployment. Key components are web UI, batch UI, model codes and data.
6.3 Usage
Utilised by forest planners in public/private sector, students and researchers.
6.4 Computational limitations
Very light to run, but can take sometime to process large quantites of data.
6.5 User interface
Stand tool uses HTML/CSS. Command line batch mode to generate GIS results and GIS extension to ArcView.
6.6 Documentation and support
In development, support via FC training courses and bulletin.
6.7 Installation
Web browser for stand version. GIS batch tool requires Java 1.4, Grass and related ESC datasets.
Server installation requires J2EE server such as Tomcat or Oracle Application Server and an oracle database.
7 References
7.1 Cited references
7.2 External resources
[edit] Scope of the system tool encourages decision maker to discover new problems or opportunities by exposing to new information or results tool helps decision makers in recognizing upcoming problems for which solutions have been developed previously tool allows decision maker to actively create new knowledge when faced with a new problem and to develop novel solutions tool allows decision maker to capture knowledge, making it available to decision makers who are seeking solutions from previously solved problems [edit] System origin Who and when was it developed is it a commercial product does it have real-life application cases [edit] Support for specific issues Is the system designed to take into account specific uses? E.g. guidance on ways to characterize biodiversity, economic-biodiversity tradeoff analysis methods, risk assessment methods, landscape analysis methods, timber harvest effects, climate change effects, biological effects (pests, pathogens, invasives), fire,...
[edit] Support for specific thematic areas of a problem type Silvicultural Certification Conservation Restoration Transportation Development choices / land use zoning Policy/intervention alternatives Sustainability impact assessment (SIA) [edit] Capability to support decision making phases (NOTE I do not quite know what to do with this, as I do not understand it myself, although it seems related to system use)
Intelligence (+ explicit description of the support given by the DSS) Design (+ explicit description of the support given by the DSS) Choice (+ explicit description of the support given by the DSS) Monitor (+ explicit description of the support given by the DSS) [edit] Related systems Describe (and/or link to) other systems related
[edit] Data and data models [edit] Typical spatial extent of application Define the scale of use for the application (user defined, regional, multi-owner forest single ownership forest, Multiple scale interaction)
[edit] Forest data input Describe the basic forest input (forest level, stand level, or individual tree level), and appropriate meta-data, such as data provenance (Areal coverage, Sample of plots, stands, Contiguous forest cover). GIS information is to be considered here, namely include cover tyes and type of information (raster or vectorial, necessity of topological information) If necessary describe surrogate sources of information
If necessary describe other types of required data (economic, social)
[edit] Type of information input from user (via GUI) Describe what is the information that the user directly inputs in the system if any): expert knowledge, opinion, goals and production objectives, preferences, stand/site information....
[edit] Models [edit] Forest models Growth, Yield, Carbon, Wood quality, biodiversity and habitat suitability, environmental and external effects (fire, storms, pests, diseases, climate change, etc)
[edit] Social models historical and cultural values of sites, values due to peace and quiet, esthetic values, values due to recreational activities, ethical values): E. g. Recreation, Health, Game
[edit] Decision Support
=== Definition of management interventions Define what is available for the manager to intervene in the forest: time of harvest, plantations, thinnings, reconversions... Existence of prescription writer, simple enumeration of all possibilities, scenario simulation , etc.
[edit] Typical temporal scale of application Define the temporal scale of the application: E.g., operational and immediate level, Tactical planning (short term) and strategic level.
[edit] Types of decisions supported Management level strategic decisions administrative decisions operating control decisions Management function planning decisions organizing decisions command decisions control decisions coordination decisions decision making situation unilateral collegial Bargaining / participative decision making [edit] Decision-making processes and models Logic modeling Operations research modeling Direct approaches Heuristic manipulation of simulation models Business modeling Simulation (with and without stochasticity) Multiple criteria/ranking Other [edit] Output [edit] Types of outputs Types of outputs produced (tables, maps, 3-D visualizations, pre-programmed summaries, etc)
[edit] Spatial analysis capabilities integrated capabilities facilitates links to GIS (wizards, etc.) provides standard data import/export formats allows spatial analysis (e.g. topology overlays (e.g. multi layering of different maps, selection of objects based on selection criteria, aggregation by attributes (e.g. areas of similar characteristics), Linking by logical means, Statistics by area, analysis with digital terrain model) [edit] Abilities to address interdisciplinary, multi-scaled, and political issues Evaluate interactions between different basic information types (biophysical, economic, social). Produce coordinated results for decision makers operating at different spatial scales facilitate social negotiation and learning
[edit] System [edit] System requirements Operating Systems: (Windows, Macintosh, Linux/UNIX, Web-based, Others) Other software needed (GIS, MIP packages, etc...) Development status [edit] Architecture and major DSS components Describe the basic architecture of the system in software and hardware. Desktop client-server, web based, as well as the integration with available systems. Basic data flow, focusing on retrieval of required input and propagation and implementations of decisions. Mention its modular and scalability capabilities.
[edit] Usage Describe the level of use: Research level use, Industry use, Government use
[edit] Computational limitations Describe the system limitations: e.g. number of management units, number of vehicles, time horizon
[edit] User interface Describe the quality of user interface and the Prerequisite knowledge for using the system
[edit] Documentation and support Describe the connection to Help-system and possibilities for assistance, as well as the required training and user support levels
[edit] Installation Prerequisite knowledge: Level of effort to become functional Cost: (purchase price, development costs, demonstrated return on investment, cost of use, training costs, licence and maintenance costs) Demo: allows the download/utilization of a trial version. If yes, where is it available and what are the trial conditions. [edit] References [edit] Cited references
[edit] External resources