Version 2.5.1

From Heureka Wiki
Revision as of 15:48, 24 May 2016 by Peder (talk | contribs) (Created page with "<noinclude> Version 2.5.1 {{Languages|Version 2.5.1}} <!--Category:Release newsdate::2016-05-24 --> </noinclude> <startFeed /> ==Update 2.5.1== Ve...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Version 2.5.1


<startFeed />

Update 2.5.1

Version 2.5.1 contains preformance improvements for the GIS-module, and two important bug fixes. One bug resulted in that average values in reports were faulty, when the report temaplate had a report-level condition that excluded one or more treatment units. Another bu <feedDate>2016-05-24</feedDate> <endFeed />

<startFeed />

<startFeed />

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. <feedDate>2016-05-24</feedDate> <endFeed />

<startFeed />

Displaying of maps after selecting are also faster

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 speed improvmenet when dispplaying maps. <feedDate>2016-05-24</feedDate> <endFeed />

<startFeed />

Bug fix: When calculating spatial neighborhoods an exception occurred for large problemS

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> <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: 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 />