Version 2.5.1 - Revision history

Peder at 15:22, 24 May 2016

2016-05-24T15:22:57Z

Peder: /* Other fixes */

2016-05-24T15:17:05Z

Other fixes

Peder at 15:07, 24 May 2016

2016-05-24T15:07:50Z

Peder at 14:55, 24 May 2016

2016-05-24T14:55:00Z

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

2016-05-24T14:54:25Z

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

Peder at 14:54, 24 May 2016

2016-05-24T14:54:02Z

Peder at 14:53, 24 May 2016

2016-05-24T14:53:24Z

Peder: Created page with " Version 2.5.1 {{Languages|Version 2.5.1}} ==Update 2.5.1== Ve..."

2016-05-24T14:48:38Z

Created page with "<noinclude> Version 2.5.1 {{Languages|Version 2.5.1}}  </noinclude> <startFeed /> ==Update 2.5.1== Ve..."

New page

<noinclude>
Version 2.5.1
{{Languages|Version 2.5.1}}

</noinclude>

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

@@ Line 46: / Line 46: @@
 ==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.
 <feedDate>2016-05-24</feedDate>
 <endFeed />

@@ Line 2: / Line 2: @@
 Version 2.5.1
 {{Languages|Version 2.5.1}}
-<!--[[Category:Release]]
+[[Category:Release]]
 [[newsdate::2016-05-24]]  [[language::en| ]]
 </noinclude>

@@ Line 9: / Line 9: @@
 <startFeed />
 ==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.
+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 />
@@ Line 21: / Line 21: @@
 <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 neghborhoods (in PlanWise optimization model).
+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 />
@@ Line 27: / Line 27: @@
 <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.
+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 />
@@ Line 39: / Line 39: @@
 <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.
+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 />