Difference between revisions of "Version 2.5.1"

From Heureka Wiki
Jump to navigation Jump to search
Line 14: Line 14:
  
 
<startFeed />
 
<startFeed />
==Import of large shape-files ten times faster==
+
==Bug fix: Average values in reports when there are report-level conditions ==
The import routine for forest maps (shape-files) has been optimized for better speed. Importing a large map of 35000 stands tooks more than 20 minutes in version 2.5.0, but takes only about 2 minutes in version 2.5.1.
+
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>
 
<feedDate>2016-05-24</feedDate>
 
<endFeed />
 
<endFeed />
  
 
<startFeed />
 
<startFeed />
==Faster display of maps after selecting an area node==
+
==Bug fix: When calculating spatial neighborhoods an exception occurred for large problem  ==
The code for displaying a map after selecting a new area node has been improved and is now considerably faster.
+
An error has been fixed that could lead to an error when calculating treatment unit neghborhoods (in PlanWise optimization model).  
 
<feedDate>2016-05-24</feedDate>
 
<feedDate>2016-05-24</feedDate>
 
<endFeed />
 
<endFeed />
  
 
<startFeed />
 
<startFeed />
==DotSpatial GIS module updated==
+
==Import of large shape-files ten times faster==
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 speed improvmenet when dispplaying maps.
+
The import routine for forest maps (shape-files) has been optimized for better speed. Importing a large map of 35000 stands tooks more than 20 minutes in version 2.5.0, but takes only about 2 minutes in version 2.5.1.
 
<feedDate>2016-05-24</feedDate>
 
<feedDate>2016-05-24</feedDate>
 
<endFeed />
 
<endFeed />
  
 
<startFeed />
 
<startFeed />
==Bug fix: When calculating spatial neighborhoods an exception occurred for large problem  ==
+
==Faster display of maps after selecting an area node==
An error has been fixed that could lead to an error when calculating treatment unit neghborhoods (in PlanWise optimization model).  
+
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>
 
<feedDate>2016-05-24</feedDate>
 
<endFeed />
 
<endFeed />
  
 
<startFeed />
 
<startFeed />
 
+
==DotSpatial GIS module updated==
==Bug fix: Average values in reports when there are report-level conditions ==
+
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 speed improvmenet when dispplaying maps.
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>
 
<feedDate>2016-05-24</feedDate>
 
<endFeed />
 
<endFeed />

Revision as of 16:55, 24 May 2016

Version 2.5.1


About update 2.5.1

Version 2.5.1 contains preformance improvements for the GIS-module, and some bug fixes. One bug was quite seriouos 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.

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.

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 neghborhoods (in PlanWise optimization model).

Import of large shape-files ten times faster

The import routine for forest maps (shape-files) has been optimized for better speed. Importing a large map of 35000 stands tooks more than 20 minutes in version 2.5.0, but takes only about 2 minutes in version 2.5.1.

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.

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 speed improvmenet when dispplaying maps.

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.