|
 Printer Friendly |
Importing yield table data into the Remsoft Spatial Planning System
Importing yield data into the Remsoft spatial planning system
Data format requirements and options
Applies to: Remsoft Spatial Planning System version 2006.8
Date: November 15, 2006
In the Remsoft Spatial Planning System, the Yields section is where you associate dynamic attributes—attributes that change with time or age—with development types in the model. Yield attributes range anywhere from traditional growth and yield measures such as stand volumes, basal area, density, etc., to prices and costs. You can even represent categorical data such a seral stages or fuel types for fire modeling. The system includes an import utility for translating yield data stored in a database file (DBF) into the Remsoft ASCII yield format.
The purpose of this tech tip is to describe the database format required for importing yield data, and some options for declaring yield data. For instructions on how to import yield data, see the online help or the Yields section chapter in the Woodstock User Guide.
At a minimum, the yield import database must contain a field named THEME1 or TH1, a field named AGE and one or more fields storing the yield data. Note that database field names are limited to 10 characters. If you attempt to open a yield database that does not conform to the required format, Spatial Woodstock will halt the import and issue an error.
As a rule, the number of theme fields in the yield database is the same as the number of themes in your model, e.g., if your model has five themes, the yield database will contain five theme fields (i.e., THEME1, THEME2, THEME3, THEME4, THEME5). Note that theme fields must be consecutive in the file. If the number of themes or their order does not match the number or the order of themes in your model, translated yield declarations will contain incomplete or invalid development type masks.
You may populate theme fields in the yield database with any of the three thematic attribute types: basic, aggregate or global (the formidable question mark character!). For example, if yield data is differentiated only by the first theme, you can populate all remaining theme values with a question mark character. This tends to keep the yield database small and compact by eliminating redundant data.
Lastly, if you wish to import time-dependent yields, you will need to portray them in the database as age-dependent. The AGE column in this case is really the time period. Once you import the yield data, simply search and replace the *Y keyword with *YT, and replace the _AGE keyword with _CP (the keyword that is used to reference the current planning period).
|
|
Stora Enso Predicts a 2.5% Savings
“We asked, ‘If we had made the decision and optimized the problems, how much money would we have saved?’” The answer was approximately 2.5 percent.”
- Continue reading...
- View all case studies...
|
 |
|
|
|
