The block attribute table calculates and displays account values for individual polygons. This table is helpful to explore the amounts that individual stand polygons contribute to the overall solution. The block attribute table is a convenient data source for custom reporting and mapping because records may be selected and summarized by multiple criteria.
A big internal change has been made to the way that the block attribute table calculates and presents account values. The previous algorithm was only able to present simple accounts, usually only simple summary accounts. The new method also shows complex summary accounts as well as Destination accounts, Route haul accounts, Exclusive and Exclusive Dependent accounts, MultiplyTarget accounts and the various flavours of Meta accounts (MetaTargets, Ratio accounts, flow accounts). The main Patch account is presented, but not the sub-accounts because these do not make sense when presented with single polygon values. Route construction and maintenance accounts are similarly not presented because these values derive from aggregates of blocks.
A consequence of this change is that complex models may see many more account columns in the block attribute table. The values in these columns are only materialized when required, so these added benefits are provided at virtually no additional cost.
A change was made to help the Query Builder and table export tools properly handled data base columns with non-standard special characters.
When tables are accessed the column names are automatically available as variable names in the Patchworks Query Language. Patchworks variable names usually only contain alphanumeric characters and the underscore symbol. If additional symbol characters such as '-' and '+' are embedded in the column name they will interpreted by the expression parser as math operators rather than part of the column name.
There can be circumstances where additional special characters exist in external data bases or even within Patchworks account names. An example of this situation are the VQO (Visual Quality Objectives) columns in the sample dataset, where the VQO zone names have hyphenated names. These non-standard column names can be safely referenced using the column function.
The fix provided in this update will insert the correctly formatted
column function in to the Query Builder and table
export scripts as required.
Minor changes and fixes:
Added a method to the Horizon class to obtain the product of two sets of factors.
Increase the maximum record length and number of fields when reading CSV files.
Add hypertext links to targets from the scenario description page.
Fixed a problem with the DitherTheme editor not correctly initializing a set of colours.
Add a new method to the ScenarioDescription class to activate an array of TargetDescription objects. Additional documentation of the ScenarioChangeListener and other classes involved with scenario automation.