|
 Printer Friendly |
Enforcing harvest delays spatially - About the STANLOCK field
Access locks are used in Woodstock models to restrict access to forest classes/development types for a specified number of periods. You may apply locks to new forest classes that arise following an action (e.g., to ensure that thinned classes remain unharvested for a set number of years), or on existing forest classes in the Areas section (e.g., to enforce harvest delays on forest classes that are proximate to tracts in greenup). However, to ensure that Stanley respects access locks, you must also apply them to the member forest polygons in the shapefile. The purpose of this tech tip is to describe how to implement and enforce access locks in Stanley.
The Remsoft Spatial Planning System includes tools for assigning access locks to existing forest classes directly in the shapefile. This is particularly useful if access locks/harvest delays relate in any way relate to the juxtaposition of classes in the forest (e.g., apply access locks to polygons that are within some distance of selected polygons). You store the lock values in a shapefile field and make Woodstock aware of these locks when you build the Areas section.
To make Stanley aware of these locks, you must store the lock values in a shapefile field named STANLOCK (see Chapter 9 of the Stanley User Guide, Managing Spatial Planning Data for a description of the STANLOCK field). If you store the access lock values in any other shapefile field, Stanley will ignore the lock values.
To add the STANLOCK field to the shapefile attribute table, do the following:
1. Right-click the Maps view to display the context menu.
2. Mouse-over Attribute data and select Modify structure from the submenu. This displays the Modify struture dialog.
3. Click Add fields on the Modify structure dialog main menu.
4. Mouse-over Optional system fields and select Stanlock from the submenu.
If an entire forest class is placed under an access lock, then Stanley de facto respects them. However, if only a portion of the forest class is subject to a lock, it is critical to store the lock values in the STANLOCK field, otherwise Stanley may inadvertently preempt the harvest delay on those specific forest polygons.
|
|
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...
|
 |
|
|
|
