Release Notes 2.6.5

Weave 2.6.5 includes a number of bug fixes and enhancements.

The enhancements increase the flexibility and usability of some of Weave’s standard tools. In particular there are a few editing related enhancements that increase the capability of Weave's Editing functions making it a viable alternative for a range of editing scenarios.

This release also completes the work required to make Weave GDA2020 compliant.

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

You will not be able to use the runtime installed with Weave to start the updater because this release contains an update to that underlying Java Runtime.

If you need to update Weave on a server that does not have another Java Runtime available use the weave-updater ISO file which contains Java Runtime along with the updater.

The main enhancements in 2.6.5 are:

Non-Spatial Editing - Editing Options

You can now specify if an edit config is creatable, updatable and/or deletable at the edit level. This allows the editing options to be tailored to your unique editing requirements.
If you want all your edits to have the same options, set them at the panel level like this:
 <view id="editor.panel.simplegrid"> <label>Edit - Non-spatial</label> <location>west</location> <enableCreate>false</enableCreate> <enableDelete>false</enableDelete> </view>
But if you want your edits to have different editing options then don’t set them at the edit level, set them at the edit level like this:
<editor:table id="nse.plans_document"> <label>Plans Document</label> <creatable>true</creatable> <deletable>false</deletable> <updatable>true</updatable> <datasource>gis</datasource> <table>docs.plans_document</table> <key>objectid</key> <parameter id="url" label="URL" column="url"/> <parameter id="planno" label="Plan Number" column="planno"/> </editor:table>
For more details on editing refer to the Non-spatial Editing page.

Non-Spatial Editing - Combined Editor View

The Combined Editor View builds on the functionality provided in the Simple Edit View. The Combined Editor View displays all related records while allowing one record to be edited.
For more details on editing refer to the Non-spatial Editing page.

Table of Contents - Favourites
Users can now set layers as favourites so they can easily find layers they regularly use.
Layers are marked as favourites in the ToC View Context Menu by adding this to the client config:
<item action="weave.toc.favourite"/>
Favourite layers are listed in the Favourite toolbar item with this client config:
<item action="weave.toc.favourites"/>
A full example of this in a client file is on the Client Views ToC page.

Data Grid Export

The export options allowed in a Data Grid now include GeoPackage. So your Data Grid can export to CSV, HTML, Excel and GeoPackage.
A sample of this in a client configuration is given below. For more details on exporting refer to the Client Actions Grid export page.

<item action="com.cohga.html.client.actions.gridWindowAction">
	<textSelect>true</textSelect>
	<pageSize>50</pageSize>
		<toolbar>
			<item action="com.cohga.html.client.grid.panAction" />
			<item action="com.cohga.html.client.grid.zoomAction" />
			<item action="weave.grid.remove" />
			<item action="weave.grid.refine" />
			<item action="com.cohga.client.actions.menuAction">
			<text>Export</text>
			<iconCls>icon-database_go</iconCls>
			<item action="com.cohga.html.client.grid.exportAction">
				<text>HTML</text>
				<format>html</format>
				<iconCls>icon-page_white_code</iconCls>
			</item>
			<item action="com.cohga.html.client.grid.exportAction">
				<text>Excel</text>
				<format>excel</format>
				<iconCls>icon-page_white_excel</iconCls>
			</item>
			<item action="com.cohga.html.client.grid.exportAction">
				<text>GeoPackage</text>
				<format>gpkg</format>
				<iconCls>icon-page_white_world</iconCls>
			</item>
		</item>
	</toolbar>
</item>

Setting a Projection for Redlines

Redlines created before Weave version 2.6.5 (and 2.6.4.8) did not record the projection of the stored coordinates. This would cause a problem if the client map projection was changed or if a bookmark/redline created in a client with one map projection was opened in a client with a different map projection.
The 2.6.5 Weave release includes two changes. It:
1. Ensures that the CRS for any new redlines is stored with the redline, and
2. It provides an OSGi command to add the projection information to existing redlines.
After you have run this upgrade, we strongly recommend you:
- Set a coordinate system for redlines that are missing a CRS value using:
  redline setcrs <crs>
  where <crs> is the CRS to set, e.g. EPSG:3857
  e.g. redline setcrs EPSG:3857
  This command will update the bookmarks and redlines to store what CRS was used when they were created. This will not alter the stored coordinates.
- If you need to alter the coordinates for redlines, use the following command to change the stored CRS:
  redline transform <from> <to>
  e.g. redline transform EPSG:28355 EPSG:7855
  Only redlines that have a CRS matching the <from> CRS will be converted to the <to> CRS. This command will alter the stored coordinates.
It is recommended that you backup your redlines and bookmarks with the storage and ustorage commands before using the transform or setcrs commands.
Note, it is not mandatory to transform your redlines into the projection of the Weave client. If these two projections are different then the coordinates of the redlines will be transformed each time the users load the client.

The redline setcrs <crs> command will set the CRS value for all redlines to the CRS provided in the command, but it won’t update any redlines that already have a CRS value set. However, you should note that it assumes that all the redlines that it will update were created using the CRS provided in the command.

If you only use a single client, or all of your clients use the same CRS for the map view, then this will not be a problem and the command will just update all the stored redlines to indicate the CRS that the client/clients used.

If, however, you use multiple clients and they have different CRS values for the map view, then it could be that you have bookmarks stored with coordinates that were generated with the different projections (if the bookmarks and/or redline saving is enabled for the client) and you won’t know which CRS was used to create which redlines. We do not believe this to be a common occurrence but if you do fall into the category please contact Cohga Support for help.