Page Comparison

...

• Interop launcher update

  • The launch.html page used to launch Weave from another website has been updated to support Weave Hub if it is installed

• Redline management tool

  • A new tool to allow you to re-order redline items has been added

• Single image slider

  • The image slider/chooser component is now part of the core Weave product rather than a separately installable component

• Allow static content to be served by Weave

  • If you have basic resources, images, HTML pages, etc, that you need to make available to the client you can copy them to the ...\workspace\static directory and the content will then be available at http://...../weave/static/. It also supports .htaccess files for access control.

• Pan select tool update

  • You can now use the alt and control keys with the PanSelect tool to add and remove from the selection

• New select neighbours tool

  • A new tool to allow you to quickly select the neighbours of the current selection has been added. By default it will select the touching neighbours but it can be configured to perform a buffer operation instead

• New splash screen

  • A new plugin to allow you to display a splash screen when the client starts has been added

• Rotate control point moved in redline

  • The rotate redline control would be covered by the corner coordinate in some redline objects so it’s been moved out further from the redline item

• Updated logging

  • The logging framework has been updated from Log4j to Logback and the logging configuration mode from logging.properties to logging.xml

• Data definitions registered in the background

  • The startup of the server will no longer wait until each data definition is connected/registered before continuing to process the configuration, which should speed up startup

• More metrics

  • Additional metrics for tracking data source connections have been added

• Cascade field support for non-spatial editing

  • Support for cascade fields has been added to the non-spatial editing

• Non-spatial editing combo update

  • The drop-down list of available edits can have its size configured

• GeoPackage export

  • The exported geopackage now supports more native column types

• Tags for ToC entries

  • ToC models now support adding tags to ToC entries, to allow for things like filtering based on tags associated with an entry

• Improved token support for ArcGIS server

  • The tokens generated when connecting to an ArcGIS server that requires authentication are now refreshed more frequently to reduce the possibility of the user losing access while using Weave

• Metrics update

  • By setting the system property weave.metrics.includeuser the search, report, map and data metrics will also include the user that generated the request in the generated metric

• Map resolution update

  • When using a map panel with fixed scales, the calculations to determine which zoom level to use from the underlying map engine is now smarter about how it chooses the tile cache level

• New security API

  • A new API is available to allow for custom authentication providers, for example using JWT

• Names selections

  • Internally Weave now has the concept of Named Selections which, in the future, will allow for more advanced selection handling operations

• Configuration file update

  • You can now set ignore="true" for a top level configuration item to have it completely ignored by Weave, this is quicker/easier than commenting out the config item

• And more metrics

  • Connections to database based spatial engines now produce metrics

• More information in Support Dump

  • The Support Dump now includes additional information and better tracking of log file output

• Spatial edit import

  • The importing of geometry with spatial editing has been improved

• Spatial upload

  • Added support for uploading Excel spreadsheets

• Admin UI file explorer

  • The file explorer has been updated to better handle files that have been edited by two people at the same time

...

• Fix for redline coordinate editing tool

  • The tool would not work unless the editing bundles were also installed, this has been fixed so that the tool now works without the editing bundles being installed

• Map resolution update

  • When using a map panel with fixed scales, the calculations to determine which zoom level to use from the underlying map engine is now smarter about how it chooses the tile cache level

• Grid filter not working in IE 11

  • Using the filter in a grid panel when using Internet Explorer as the browser was not working

• Spatial and selection identify

  • These tools were not clearing their content at the correct time and could present out of date information to the user

• Image slider

  • At startup the slider could turn on layers that were not supposed to be visible

• Redline styles

  • Redline objects were losing their style after being saved and loaded a couple of times

2.6.4.14

Released 20 January 2022

Fixes

• Map resolution update

  • When using a map panel with fixed scales, the calculations to determine which zoom level to use from the underlying map engine is now smarter about how it chooses the tile cache level

• Map alias fix

  • A small fix for aliases for map engines was implemented

2.6.6.3

Released 7 January 2022

Fixes

• Fix for redline coordinate editing tool

  • The tool would not work unless the editing bundles were also installed, this has been fixed so that the tool now works without the editing bundles being installed.

2.6.6.2

Release 10 December 2021

Fixes

• Grid filter not working in IE 11

  • Using the filter in a grid panel when using Internet Explorer as the browser was not working.

2.6.6.1

Release 8 December 2021

Fixes

• Spatial and selection identify

  • These tools were not clearing their content at the correct time and could present out of date information to the user

• Image slider

  • At startup the slider could turn on layers that were not supposed to be visible

• Redline styles

  • Redline objects were losing their style after being saved and loaded a couple of times

...

• New Redline tool

  • A weave.redline.spatialSelect tool was added to the redline toolbar to allow selecting entities based on redline geometry

• Coordinate input change

  • The two coordinate input panels, redline and spatial editing were changed to default to latitude, longitude rather than longitude, latitude

• New export action

  • A new weave.grid.exportgriddata action can be added to the grid panels to export data

• activateEntity flag added to ToC panel

  • a flag when set to true will change the active entity, to the one associated with the toc entry, when that entry is turned on

• ArcGIS Server token support

  • Support for tile caches that require authentication has been improved

• Grid panel Copy operation

  • A right-click Copy menu has been added to the grid to support copying the information from the grid to the clipboard (if you have set textSelect to true for the grid panel the system menu will display instead)

• Nearmap update

  • There is a new Nearmap panel available to work around issues in the existing Nearmap panel

• Geocode API update

  • The Geocode API now supports providing the centre of the client map to help improve search results (for Geocoding engines that support it)

• JSON Converter API update

  • The JSON Converter API now supports classes implementing the JSONString interface, allowing an object to provide its own JSON representation to the client

• Update to caching settings

  • The weave.cache.default flag will now disable caching for data definitions as well as search results

• Non-spatial editing update

  • Support for “calculating” a column value based on another table has been added to non-spatial editing, i.e. populate a column from a separate table

• Excel export update

  • The grid panel export to Excel now exports to a newer version of Excel, i.e. .xlsx format

• ArcGIS tile update

  • Support for local compressed ArcGIS map tile caches was added

• SLD file resource improvement

  • SLD files are more forgiving of references to external resources, i.e. images can just be referenced using the file name if they’re in the same directory as the SLD file itself

• WMS server type guessing improvement

  • In situations where the type of WMS server needs to be known there have been improvements made to the code that determines the server type

• Spring Security configuration update

  • The Spring Security validation code no longer needs access to the internet to download the schema files

• Selection API update

  • Some internal selection code was updated to obtain the current selections earlier in the process

• Runtime properties file updated

  • The runtime.properties file now sorts the properties by name

• New storage commands

  • There is now a flush option available for the storage and ustorage commands, which ensure that any outstanding writes are written to the storage provider

• New logout button in Admin UI

  • The Admin UI now has a Logout button

• Tile update

  • When generating a single map image from a tiled map engine some optimisation has been made to improve performance

• Edit panel update

  • It is now possible to configure the edit combo box width in the spatial edit panel, by setting comboWidth and comboListWidth in the panel config

• A new Spring Security helper class is available

  • A com.cohga.weave.security.userdetails.DelegateUserDetailsService class is available for use in a Spring Security security.xml file to allow you to use multiple user details services to get user details, i.e. multiple LDAP servers

• Various API updates

  • A number of internal API’s have been updated along the path to a Weave 3.0 release

Fixes

• Bookmarks

  • Clarified handling of publish, publisher, published and share flags in the bookmark action button

• Details panels

  • Fixed data/time handing on the entity details panels

• Legend panel fix

  • Fixed issue that was stopping the legend from being updated when first exposed

• List fix

  • List entries that contained carriage returns and/or line feeds would stop the list from working

• Internal database corruption fix

  • An update that should help avoid corruption of the system data source has been implemented. This is not an issue for sites that use an external database as the system data source

• ArcGIS map engine reset fix

  • The “memd reset” command wasn’t clearing all information related to an ArcGIS map engine

• Map alias fix

  • A small fix for aliases for map engines was implemented

• Database OSGi command fix

  • The ‘dbmd sql’ command has been updated to fix an issue when displaying binary column types

• Keycloak fix

  • An issue determining the URL to redirect to after login/logout was fixed

• User storage fix

  • A fix for user storage when sessions are not used has been implemented

• Spatial edit fix

  • An issue relating to creating a new spatial edit was fixed

• Runtime property parser fix

  • When parsing a runtime property that represents a file variations in the way the operating system and Java version present the “path” can result in the value not being interpreted as a path correctly. i.e. sometime the path is given as file://<path> and sometimes file:<path>

• Admin UI console timeout

  • The default timeout for the Admin UI OSGi console was too short, sometimes giving the incorrect perception that the command did not work

• PostGIS compatibility fix

  • The GeoTools 13.x PostGIS driver has been updated to fix compatibility issues with newer versions of PostGIS

• EPSG:7899 support on client

  • A projection definition for VicGrid GDA2020 has been added to the client

• Possible XSS fixed

  • A possible, but very unlikely, vector for an XSS issue we removed. An error response contained the id of the request that generated the error. While it’s not clear how or if this could be used as a vulnerability but we’re removing all instances of client request parameters being returned in responses to try and minimise any possibility of this being used

• Client IP

  • If the server was behind a reverse proxy Weave might not guess the correct IP address of the client

• Default style

  • The client would not be able to determine the default style to choose for a layer in some circumstances

• KML export fix

  • Exporting to KML fixed an issue if it could not determine the projection of the source data

• Zipnship fixes

  • The Zipnship export menu has some fixes for problems when there was more than one menu in a client

2.6.5.5

Release 23 June 2021

Fixes

• ArcGIS Tiles

  • Added fix for serving ArcGIS tiles that are served from a secure ArcGIS service

2.6.5.4

Released 27 May 2021

Fixes

• Legend panel

  • If a legend panel was in a region of the layout that was initially collapsed it would not update its content when initially exposed by the user

• ToC panel

  • The enable/disabled state of ToC groups wasn’t reflecting the scale ranges of the included layers

• Oracle edit

  • A fix for the non-spatial editing has been applied to work around an issue with Oracle returning invalid metadata for decimal columns

• Map alias

  • If multiple plugins were included in the map view the server would not process map aliases correctly

2.6.5.3

Released 31 March 2021

Fixes

• Client IP

  • If the server was behind a reverse proxy Weave might not guess the correct IP address of the client

• Default style

  • The client would not be able to determine the default style to choose for a layer in some circumstances

2.6.5.2

Released 26 March 2021

Fixes

• Restore ToC functionality removed in 2.6.5

  • The ability to turn off all children in an exclusive toc group or to configure an exclusive toc group with no children initially checked was removed in 2.6.5, you can now re-enable that by setting allowExclusiveOff to true in the toc panel config

• Excel export fix

  • If a data definition has a URL parameter that generated an empty value you could not re-save the exported XLS file

• Internet Explorer incompatibility in non-spatial editing

  • 2.6.5.1 introduced an extra comma that would stop the client from starting if the non-spatial editing extension is installed and the users browser is Internet Explorer

• Spatial editing fix

  • The CreateNew button would sometimes override the default values in the input form

  • The CreateNew button would not always switch to the edit input form panel if it was hidden when the button was pressed

2.6.5.1

Released 23 March 2021

Fixes

• Session cookie fix

  • This fix ensures that session cookies have the correct flags set so that third party authentication works correctly after recent changes to browser behaviour

• PostGIS fix

  • The GeoTools PostGIS driver was updated to work with newer versions of PostGIS

• Added missing GDA2020 projection

  • The VicGrid GDA2020 client projection definition was missing

• Changes to exclusive groups in ToC panel weren’t reflected in the map

  • 2.6.5 changes exclusive groups so that it would turn on the first child if no items were checked initially, but the change was not being reflected in the map

• XSS fix

  • An invalid request from the client included the request id in the response error, which theoretically could be a security issue (but isn’t)

...

• Redline coordinate entry

  • Support tabs as a separator in the input text

• Updated to login/logout

  • Login and logout handing has been updated to better support multiple authentication mechanisms

• Min/Max scale display update

  • The ToC panel has been improved for the displays of the scale ranges for a layer

• Oracle Time update

  • A workaround for the Oracle JDBC driver not being compliant with the JDBC specification when it comes to dates and time has been implemented

• Updated non-spatial editing

  • You can now specify if an edit config has create, update and/or delete capabilities

• Encryption key update

  • The private key used to encrypt items in Weave config files can be specified by an environment variable or system property, rather than just the private.key file

• Data export API

  • A new API for exporting data has been implemented

• GeoPackage as a data export format

  • Along with CSV, HTML and Excel, there is now a GeoPackage option for exporting data from a data grid

• List provider API update

  • The API for generating lists for the client has been updated to improve support for filtering the values

• Tile cache update

  • You can now set the system property tile.cache.disable to true to disable caching of tiles fetched from external servers

• WMS Legend generation config update

  • It's now possible to specify additional tokens that need to be included in the URL sent to a WMS server just for GetLegend requests. Previously you could only specify one set of tokens and they were sent on every request.

• SAML Authentication

  • Support for authenticating using SAML has been added. This provides support for Microsoft AD FS and Azure AD amongst others.

• New whoami request

  • You can open the URL /weave/whoami to get information about who the server thinks you are, which is useful to debug login, role and ACL related issues

• Dynamic configuration variables

  • Variables in config files set by using the "set" instruction are now dynamic (i.e. their value can be changed when the config files are being processed). Previously the values were fixed, with the last value set when processing the config files, being the one that was used. You can set the system property "weave.config.variables.dynamic" to false to restore the previous static variable handling.

• Updated Geometry Simplification API

  • An internal API used for simplifying geometry has been enhanced to provide more control over the simplification process

• Geometry REST API update

  • The /geometry/transform/point endpoint has been updated to be more lenient with missing parameters and more strict with required parameters

• Support dump update

  • The support dump has been updated to include additional information

• Client IP address update

  • The server determining the user's actual IP address, taking into account proxies, has been improved

• Runtime Property API update

  • The internal API for getting system properties has been updated to allow a function to provide the default value

• Admin UI Spatial Engines Tool update

  • The tool now provides filtering for spatial engine layers based on their name

• Data API update

  • The Java Data API now allows some formatting to be provided as functions, not just from a pre-defined set of options. This includes dates and times, URL's and boolean values.

• EPSG update

  • The EPSG database has been updated to version 9.9, from 9.7

• SQL Server spatial engine update

  • The SQL Server config now accepts a "URL" parameter, to allow specifying the full connection URL, rather than having the URL constructed from other config parameters

• Third-party library updates

  • A number of third-party libraries have been updated to newer versions

• Bookmark improvements when switching projections

  • The bookmarks are smarter about reprojecting redlines and extents when a bookmark is saved in one projection but loaded on a client in another projection.

• User attributes in client config

  • It’s now possible to reference users attributes in a client config to customise a client for individual users

  • For example: <initial minx=”${user.extent.initial.minx}” miny=”${user.extent.initial.miny}” maxx=”${user.extent.initial.maxx}” maxy=”${user.extent.initial.maxy}” crs=”${user.extent.initial.crs}”/>

  • You need to create and configure user attributes separately (the example above will not work out of the box)

• Buffer display update

  • The buffer polygons displayed on the client are "simplified" to reduce the number of points in the polygon. The default number of points is 1000. To change this you can set the system property weave.client.buffer.maxpoints to a larger (or smaller) value. Note, changing this property doesn't affect the buffer operation itself, just the polygon displayed to the user (since these polygons can contain 10's or 100's of thousands of points and can take a long time to download).

• Jetty updated

  • Jetty has been updated to version 9.4.38

• Java updated

  • Java has been updated to 1.8.0_282

Fixes

• Redline coordinate entry

  • Fixed typo in help text

• Redline shapefile/kml export

  • Stop "invalid" geometries from aborting the export

• Export filename fix

  • An export generated from a grid didn't always set the filename correctly

• Metric name typo

  • The name of the metric "datasource,available" was corrected to "datasource.available"

• ArcGIS REST API fixes

  • The code has been updated to better handle the vagaries of the responses sent from ArcGIS

• WMS Map logging fix

  • Recording of map and layer timings has been added back after accidentally being removed in release 2.6.4

• Buffer generation inconsistency fixed

  • Previously different code used different methods to generate buffers around geometry which would sometimes give inconsistent results. Now all code that generates a buffer uses the same code and settings.

• Report generation issue

  • A missing map engine would sometimes stop a report from generating if it referenced the missing map engine

• NTLM Authentication fix

  • Once a user has authenticated via NTLM they will not be required to authenticate again during the current session.

• Null identifier fix

  • Updates have been put in place to handle records that use null as a key value

• Runtime Property API fix

  • The internal API for getting system properties has been updated to better handle file-based URL's for file and path type properties. Recent updates to Java and Windows meant that these value were being handled differently between Windows and Linux.

• Admin UI data explorer fix

  • The tool was returning the wrong number of records when paging

• Admin UI spatial engine fix

  • The tool was failing with ArcGIS layers that were empty

• PRJ file handling

  • Updates have been made to handle differences between OGC and Esri PRJ files when uploading spatial data.

• Redline fix

  • Redlines created before 2.6.5 and 2.6.4.8 did not record the projection of the stored coordinates which could cause issues if a client config changed the map projection or if a bookmark/redline created in a client with one map projection was opened in a client with a different map projection. This update a) includes the crs in any new redlines, and b) provides a “redline setcrs <crs>” osgi command to add the projection information to existing redlines.

• Coordinate display panel

  • If the panel was visible at startup it wouldn’t update when the mouse was moved

• Client support for EPSG:7899 projection

  • The client did not know about the GDA2020 VicGrid projection

• Bookmark update fix

  • Replacing a bookmark would not update the stored content

• ToC panel fix

  • It was possible to turn off all layers in a group marked as exclusive when this should not have been possible

• Buffer display fix

  • Sometimes the buffer displayed to the user, not the one used to perform the buffer operation itself, did not display correctly

2.6.4.13

Release 18 Feb 2021

Fixes

• ToC panel fix

  • It was possible to turn off all layers in a group marked as exclusive when it should not be

2.6.4.12

Released 17 Feb 2021

Fixes

• Bookmark update fix

  • Replacing a bookmark would not update the stored content

2.6.4.11

Released 16 Feb 2021

Fixes

• Fixed redline transform command

  • The redline transform command did not handle invalid geometries well, it will now remove any invalid geometries stored in a redline (not remove the whole redline)

2.6.4.10

Released 15 Feb 2021

Fixes

• Fixed redline transform command

  • There was a problem when transforming saved bookmark that also included and extent

...

• New bookmark commands

  • New bookmark management commands have been added to allow you to retroactively set the CRS for redlines stored in bookmarks.

  • The new “bm setcrs <crs>” command should be run after you upgrade to 2.6.4.8 (or 2.6.5) to update all existing bookmarks to include the CRS that was in use when the bookmarks were created.

Fixes

• Multi-select field fix

  • A multi-select field would not always display its initial values (if it was configured with an initial value)

• Data export fix

  • When exporting data from a grid the name of the file was not always set correctly

• Bookmark redline fix

  • Previously bookmarks did not store the CRS of the redlines and relied upon their coordinates being in the same projection as the map

2.6.4.7

Released 11 Feb 2021

Fixes

• Spatial upload projection issue

  • Fixed an issue where uploaded data would not project correctly if an included PRJ file was not understood by Weave

2.6.4.6

Released 29 Jan 2021

Fixes

• Map logging restored

  • The 2.6.4 update accidentally removed the map engine/layer logging from the Admin UI, it’s now been added back

2.6.4.5

Released 28 Jan 2021

Fixes

• Windows integrated authentication fix

  • NTLM authentication, via Acegi Security, was updated to fix an issue causing some client functions to not work

2.6.4.4

Released 17 Nov 2020

Fixes

• Quick search data panel fix

  • Fixed a minor issue when updating the quick search data panel

• Redline export fixes

  • The export to KML and Shapefile tools have been fixed to ignore invalid geometry

• Metric name fix

  • The name for the JDBC connection monitor metric was incorrect

• Map export fix

  • Exporting a map was ignoring the "labels visible" flag for layers

• Report map fix

  • Fixed an issue that could cause a report map to be out of sync with the clients' view

• Spatial search fix

  • Fixed an issue that didn't always apply all the required filters

2.6.4.3

Released 20 Aug 2020

Fixes

• Missing CRS parameter in intersect requests

  • A crs parameter was missing when sending an intersect operation request to the server, so if the data is stored in a different projection the "highlight" geometry would not display on the client

• Unnecessary errors in log

  • An unsupported request from the client was logged as an error when it should be a warning, and no information was recorded about what the request was

• Startup performance issue

  • There was a problem that could result in delays when the server was starting up

• Invalid metadata in an API bundle

  • An API related bundle included some incorrect metadata in the source relating to the version of Java it required. This shouldn't effect the server but required a bump in the version number to update the bundle.

2.6.4.2

Release 13 Aug 2020

Fixes

• Selection identify fix

  • If you try to export data from the selection identify tool and have no records selected then you would get no data, rather than all records

• Id mapping fix

  • If a null id makes it into the system it can cause problems, this fix should ensure that null id's are no longer possible

• Missing entries in config.ini file

  • The installer for 2.6.4 moved some bundles from optional extras to always being included, but did not add the config.ini entries to ensure those bundles were started. Updating from previous versions did not have this issue, just installing a clean 2.6.4 version.

2.6.4.1

Release 4 Aug 2020

Fixes

• ArcGIS Server certificate issue

  • Weave may complain about the certificates presented by ArcGIS Server.

...

• Weave Hub

  • A new third party application integration library to replace Weave Link and provide integration in browsers other than Internet Explorer. Currently supports Authority, Pathway, Proclaim and Trim integration.

• New Redline Tools

  • Edit coordinates of geometry

  • Upload geometry from a file

• New Spatial Edit tools

  • Edit coordinate of geometry

  • Upload geometry from a file

• GDA2020

  • Initial support for using the GDA2020 projection

• Metrics

  • Added metrics support so Weave can be monitored externally, currently supports Prometheus, InfluxDB and Datadog.

  • Note this will not be installed/enabled when updating an existing instance, so as not to add the overhead to sites that do not want it. To install it for an existing instance, re-run the 2.6.4 installer pointing it to the newly updated 2.6.4 instance and disable everything but the System Metrics component.

• Help

  • The default help content is now provided as part of the installation.

  • Note this will not be installed when updating an existing instance, so as not to overwrite any customisations that may have been applied. To install it for an existing instance, re-run the 2.6.4 installer pointing it to the newly updated 2.6.4 instance and disable everything but the Help component.

• Zip'n'ship

  • Supports exporting to GeoPackage

  • Data sets can be grouped into folders

• Tiled map engines

  • Tiled map engines can now be configured for performance or quality when re-projecting the tiles and they can be configured to fetch multiple tiles in parallel.

• Stitching dynamic map engine

  • If a back end map service only supports generating images up to a certain width and height (i.e. as with ArcGIS), you can now create a wrapper "stitching" map engine that can be configured with the maximum width and height that the back end map service supports. The stitching map engine will make multiple requests to the back end map service so that it only requests images of the size the map service supports and it will then stitch the images back together to make a single image of the originally requested size. This is particularly important for BIRT reports with large embedded map components. So now you can, for example, generate an A0 size report even if the map service in use only supports generating images of 1000 x 1000 pixels.

• A new group parameters for reports

  • So you can group reports on the client

Fixes

• Various minor bug fixes

2.6.3.1

Released 28 November 2019

Fixes

• Street View panel fix

  • Resolved an issue with moving in the street view panel bouncing back at certain locations which was stopping users from being able to move forward in the street view panel.

...

Released 20 November 2019

Fixes

• List-box/combo-box field issue

  • Some field functionality in 2.5.30 changed the way list-box and combo-boxes worked by default, this update fixes the fields so they work more like they did before 2.5.30.

...

Released 13 November 2019

Fixes

• ToC model parsing issue

  • When generating an id for a toc model group entry that does not have an id set the generation of the id required a map engine to be know which may not always be the case, this would result in the toc model not being available. This update resolves the requirement to have a mapengine specified and will generate the id without one.

...

Released 12 November 2019

Fixes

• Data grid filter fixes

  • Exporting data from the data grid when using a filter would not always work

  • Filtering on a string column was not performing a wildcard search  by default

...