Change History WSMS 3.0.4.Rev - (WSMS3040)

Added Features
(SCR965) Matrix format for transfer of terrain calculation results "Composite"
(SCR1043) New wsms-widget-map operation to return closest series to scale
(SCR1046) Add option to generate WIF's in Regrid
(SCR1049) Display decimal accuracy in series with accuracy less than 1m
(SCR1050) Add ability to generate composite matrix dataset from matrix and vector
(SCR1052) Add ability to perform mixed matrix and vector path calculations
(SCR1053) Apply file name to BMP+WIF datasets when name field in WIF is blank
(SCR1061) Provide ability to resample matrix datasets when generating composite
(SCR1068) Added refine flag to all Pick() operations for more accurate selection
Bug Fixes
(SCR1035) Font reverting back to default or vanishing related to SCR1065
(SCR1044) Corrected GCC 4.0.0 compiler errors
(SCR1045) Corrected GCC 4.0.0 compiler warnings
(SCR1047) Corrected GCC 4.0.0 style warnings
(SCR1048) Corrected missing SCCS tags
(SCR1062) Mixed path calculation sometimes drops a location
(SCR1063) Map raster tiles vanish in multi session display
(SCR1064) Incorrect scenario loading of overlays with widgets of the same name
(SCR1065) Symbol raster tile vanishes
(SCR1067) C++ Interface to WSMS.Widget.Manger.Find crashes for not found
Special Notes
(SCR1043) WSMS.Widget.Map now contains an operation Get_Closest_Series() which returns the closest series to for the map closest to the specified scale. It first ensures only series that match the specified content are possible and then finds the closest accuracy value. When two series have the same accuracy the one matching the maps current series name is preferred. A user applied series filter can also be used to further sub-set the possible selections.

(SCR1049) When a map is less than 1m accuracy the accuracy within the series will reflect its accuracy to 2 decimal places.

(SCR1050) There is a new terrain component wsms-terrain-composite that exports operations to build composite (Matrix) datasets derived from Matrix and Vector datasets. Current operation allows a base Matrix dataset to be enhanced by overlaying No-Go areas sourced from vector polygons and Networks sourced from vector lines. The No-Go areas force the result composite dataset to have maximum elevation while the Network lines force the elevation to a level 0 elevation. This is useful in the route planner for a combined road/off-road solution using a single Composite dataset. The planner will be blocked from any No-Go area due to the high elevation and will prefer the Network area due to its level 0 elevation.

(SCR1052) The route planner wsms-terrain-path now has additional methods that allow for combined road/off-road solutions. There are two possible approaches to this one is described in SCR1050 using a composite matrix dataset that has No-Go and Networks applied, the other is a mix of the current Matrix solutions (Least_Time, Least_Distance and Least_Slope) and the Vector solution (Follow_Vectors). This second method is accessed using the Methods (Mixed_Time, Mixed_Distance or Mixed_Slope). First a Vector solution is determined as normal but each of the end points from the vector solution if not already on a road is calculated using a Matrix solution and the results merged to form the final returned result.

(SCR1061) The composite operation also provides the ability to re-sample either up or down the source Matrix dataset to return a composite dataset of specified meters accuracy. The re-sampling is applied when a non-zero value is applied to the Accuracy parameter in the Calculate() operation.

(SCR1068) All pick operations in WSMS.Widget.Overlay and WSMS.Widget.Manager now have an additional WSMS::States Flag called "Refine". When set False the Pick() operations perform as they currently do using a very fast bounding box check to determine when a widget is within the specified Area or Extent. When set True an additional test is performed after the bounding box test to check more accurately if a widget is within the selection Area or Extent. This only applies to multi-point symbol widgets. If the widget is a non-closed shape it is considered a line object and any point on the line within the specified Area or Extent will be considered an intersection. If the widget is a closed shape or filled shape it is considered a polygon and when the center of the Area or Extent is within the polygon it is considered an intersection.