Version 2.5.1/sv
Version 2.5.1
2016-04-11
<startFeed />
About update 2.5.1
Version 2.5.1 contains performance improvements for the GIS-module, and some bug fixes. One bug was quite seriuos and resulted in that average values in reports were faulty, if the report template had a report-level condition that excluded one or more treatment units. <feedDate>2016-05-24</feedDate> <endFeed />
<startFeed />
Bug fix: Average values in reports when there are report-level conditions
An SQL query error resulted in that average values in reports were faulty, if a report had a report-level condition that excluded one or more treatment units. <feedDate>2016-05-24</feedDate> <endFeed />
<startFeed />
Bug fix: When calculating spatial neighborhoods an exception occurred for large problem
An error has been fixed that could lead to an error when calculating treatment unit neighborhoods (in PlanWise optimization model). <feedDate>2016-05-24</feedDate> <endFeed />
<startFeed />
Import of large shape-files ten times faster
The import routine for forest maps (shape-files) has been optimized for better speed. A test with 35 000 stand polygons took more than 20 minutes in version 2.5.0, but only about 2 minutes in version 2.5.1. <feedDate>2016-05-24</feedDate> <endFeed />
<startFeed />
Faster display of maps after selecting an area node
The code for displaying a map after selecting a new area node has been improved and is now considerably faster. <feedDate>2016-05-24</feedDate> <endFeed />
<startFeed />
DotSpatial GIS module updated
Version 2.5.0.0-4 used DotSpatial version 1.7 (32-bit), which has been upgraded to DotSpatial version 1.9 (64 bit). This has resulted in faster displaying of maps. <feedDate>2016-05-24</feedDate> <endFeed />
<startFeed />
Other fixes
- If an area with many treatment units (say 10000 or more) was deselected and the project closed, the map would occasionally persist in memory even after closing the project.
- The stem density of young stands with a mean height between 2 and 6 meters were not corrected for impediement proportion when importing data from a stand register. The magnitude of the error was about proportional to the impediement percentage. For example, with a 5% impediment, the number of stems was overstimated by about 5%.
<feedDate>2016-05-24</feedDate> <endFeed />