Release Notes 2.5.26

Weave 2.5.26 includes a number of bug fixes and enhancements.

This release is mostly focused on enhancements and corrections to some of Weave’s most recent tools. The enhancements expand on the functions provided by these tools and also increase the flexibility and usability of some of Weave’s standard tools.

A full list of changes can be found at the Weave What's New page. 

The main enhancements in 2.5.26 are:

 Map Tips

• Showing Geometry
  • Map Tips will now show the geometry of the related feature in the default highlight style. 
  • This is turned on by default and can be turned off by setting showGeometry to false in the Map Tip tool configuration.
  • If you want to set a different highlight style, use the highlight tags as per other parts in the client configuration. 
• Visibility Flags
  • A new visibleOnly flag has been added to the tool and individual map tips, to specify that the tips should only be displayed if the layer is turned on in the ToC. The default value is false. 
  • There is also visibleOnlyMenu, which if set to true, adds a new menu item to the Map Tips menu to allow the user to turn the visible only setting on or off. The default is false.
• Groupings
  • Map Tips can be grouped in the Map Tips menu by setting a group attribute for the tip. All tips with the same value for the group attribute will be included in the same sub-menu, and tips without a group attribute will appear in the main menu.

The XML required to implement the four changes shown above (geometry display, visibility flag, visible-only menu and groupings), are shown in the client XML extract below. Also included is an example of setting a different highlight style for Map Tips. 

<item action="weave.maptips">
	<radius>3</radius>
	<multipleMaximum>3</multipleMaximum>
	<visibleOnly>true</visibleOnly>
	<visibleOnlyMenu>true</visibleOnlyMenu>
	<!--showGeometry>false</showGeometry-->
	<highlight>
		<marker>
			<icon>resources/images/markers/w-marker-green.png</icon>
			<width>24</width>
			<height>30</height>
			<offsetx>-8</offsetx>
			<offsety>-28</offsety>
		</marker>
		<vector>
			<strokeWidth>3</strokeWidth>
			<strokeColor>green</strokeColor>
			<strokeOpacity>0.75</strokeOpacity>
			<fillColor>green</fillColor>
			<fillOpacity>0.25</fillOpacity>
		</vector>
		<autoClear>false</autoClear>
		<autoClearDelay>2000</autoClearDelay>
	</highlight>					
	<tip>
		<data>property_details</data>
	</tip>
   <tip>
		<datadefinition>dd_zone.maptips</datadefinition>
		<entity>planningzones</entity>
		<label>Planning Zones</label>
		<group>Group A</group>
	</tip>
	<tip>
		<data>counciltrees</data>
		<entity>counciltrees</entity>
		<label>Council Trees</label>
		<radius>5</radius>
		<group>Group B</group>
	</tip>
	<tip>
		<datadefinition>dd_busstops.maptips</datadefinition>
		<entity>busstops</entity>
		<label>Bus Stops</label>
		<radius>5</radius>
		<group>Group B</group>
	</tip>
</item>

 Table of Contents (ToC)

• Context Menu enhancement for checkAll and uncheckAll
  • These two items now allow you to set includeParent to true or false to change the behaviour of the option with respect to also turning on or off any parent ToC entries. The default setting for checkAll is true and for uncheckAll it's false as these would be the most common required behaviours. 
• Automatically turn on a layer when an entity is selected
  • By setting turnOnActive to true in the ToC panel Weave will turn on the layer related to the active entity if it's not already turned on.
• Index enhancement
  • An index search can now be set to turn on the layer with the entity (via the ToC model) by setting doTurnOnLayer to true for the index combo in your client configuration. 

 Selection Identify

• There is much more flexibility with this tool now as you can:
  • Set it to just search visible layers, by setting useVisibleEntities to true in the tool configuration. 
  • Specify a buffer to use when selecting entities that intersect the selection, by setting bufferDistance, bufferUnits and bufferCrs in the tool configuration.
    • Setting a small negative buffer distance can help report on the correct records when there is a slight spatial overlap between the selected feature and its neighbours as it will stop (or at least reduce) the features being found as overlapping the selected feature. 
  • Specify a spatial operation to use when selecting entities that "intersect" the selection, by setting spatialOperation to one of intersect, contains, or overlaps.
  • Specify if the active entity should be included in the search, by setting includeActive to true in the tools configuration. 

 Spatial Editing

• You can now specify a table directly in the edit configuration that should be edited, rather than relying on what's in the spatial mapping for the entity. This should help with editing entities that are spatially backed by a database view.

 BIRT

• BIRT includes a new North Arrow component that can be added to a report. Add it as you would any other component in a BIRT report.

• This is a standard north arrow but means you don't have to load in your own image if you want an north arrow in a report. 

 Upload File

• KML Files
  
  • The KML parser is now more forgiving of invalid KML files that are uploaded so you should be able to load up a broader range of KML files. 
  • Files that contain label points are supported and will display labels on the Weave Map. 

 NearMap and Street View Integration

• Reduction of resources used
  • The NearMap and Street View panels will not try and retrieve map tiles when the panel is not visible. 
  • This should reduce your NearMap and Street View data usage significantly. 

 Database Timeouts

• Timeouts added to data definitions
  • Database related data definitions now have a server-side timeout, with a default of 120 seconds, to ensure that long-running queries do not keep running.
  • You can set the timeout, in milliseconds, in the options for the data definition, or globally as a default, or turn it off completely, using the timeout tag. 
  • Further details and an example can be found on this wiki page.

 Administration

• Map Engine Refresh
  • It is now possible to refresh a Map Engine using memd reset at the OSGi console or via the Map Engine tool of the Admin Tool. This tells Weave to clear any cached information it may have on a back-end map service and is useful when you change the service and need Weave to take note of the update. 
• Map Engine Health Checks
• Health checks have been added for more Map Engine types.
• These can be viewed in the Server Health tool of the Admin Tool.
• Spatial Metadata
  • The spmd command (at the OSGi console or via the Console Tool of the Admin Tool) had been updated so that it outputs the count of records when describing a table.