Page Comparison

...

2.6.8.9

Released 2024-10-04

Enhancements

• Support SQLServer 2022

  • Updated the GeoTools SQLServer driver to support SQLServer 2022.

2.6.9.7

Released 2024-09-24

Fixes

...

• Can not handle CQL filters with apostrophes in some situations

  • If a filter contains ' it needs to be changed to '' before being parsed.

• Redline stops working if polygon tool is active when map is resized

  • If the redline polygon tool is active and the map is resized the redline tools stop working.

• Not all metric are being reported

  • A change in the caching of metrics has resulted in some metrics not being exposed.

• Reset button is hidden on search panel when only one search is available

  • Because of a change to the layout of the search panel toolbar if there is only one search available the entire toolbar is hidden, which includes hiding the reset button.

• Audit Edit Configuration checkbox parameter reference returns wrong value

  • Writing a checkbox value to an audit table does not take care of converting the boolean value to a value supported by the underlying table column type.

• ToC description overwritten by map engine description

  • Setting the layer description in the toc model should override what the map engine provides.

• XSS issue in login page

  • If you're using the obsolete Acegi security login plugin there's a possible cross site scripting vulnerability.

• Fix handling of invalid geometry with raster functions

  • If a user generates invalid geometry raster functions should report an error rather than trying to process the geometry.

2.6.9

Released 2023-11-17

Enhancements

• Application integration for TechnologyOne ECM

  • Implement a document management system plugin that works with TechnologyOne ECM.

• Some document api bundles are not using declarative services

  • There are some document api related bundled that should be updated to DS to make them easier to debug.

• Updated metrics to support client metrics

  • Metrics have been updated to support client side metrics, i.e. recording what tools are used and how long users are using the client.

• Allow setting default roles for keycloak

  • It should be possible in keycloak.properties to set a defaultRoles property to a list of roles that a user should be given if the SAML server does not provide any roles.

• Selection collector does not provide a way to specify a limit

  • The SelectionCollector API (when using a spatial mapping to collect keys) does not provide a way for the caller to specify what limit to use when collecting keys, it will always use the limit set in the spatial mapping.

• Progress monitoring not always using the correct methodology

  • When using the ProgressMonitor API some code is not using the API in the correct manner.

• Create a Select All map context menu item

  • Enhancement request for context menu item to allow selecting all entities.

• Allow removal of email domain for keycloak users

  • Rather than making people configure their SAML id provider correctly I'm providing an option, stripDomain, that when set to true in the keycloak.properties file will remove anything after the last @ in the username returned from SAML.

• Client Geometry API does not support named selections

  • The API allows you to retrieve geometry for a selection, but only the default selection, it should be updated to allow the caller to specify the named selection to use.

• Add support for retrieving features via the rest geometry api

  • The geometry api can retrieve geometry but it would be useful for it to be able to return features, with properties (obtained from a data definition).

• Ctrl-S should save editor content in admin ui

  • When editing a file in the admin us pressing Ctrl-S brings up the browser save window, it should just save the file content.

• Support caching of WMS image format mapping

  • It can take a while to fetch the images to correctly determine the actual image format for a format that a WMS server says that it supports, this becomes a major issue if there are a lot of map services which can make the startup time of the server very long. This update will cache the format mappings per WMS server removing the need to query the same back end multiple times to verify the same information.

• Support map engines providing a description for a layer

  • Some map engines, like WMS, support a "description" for a layer, it should exposed so a ToC model can reference the text rather than requiring the description to be explicitly set in the toc model entry.

• Add default toolbar and context menu to ToC panel

  • Out of the box the ToC panel has no toolbar and the no context menu, so I'm going to set a default toolbar and context menu that contains elements that are suitable for all clients, i.e. are not dependant upon something specific being configured on the server. A toolbar or contextmenu tag in the client will override the defaults, so site that have already customised these won't see any change. And they can be removed completely by setting an empty toolbar and/or contextmenu tag in the panel config.

• BIRT log files are not cleaned up

  • If logging is enabled for BIRT the log files are not removed and can generate a lot of files. During startup old log files should be removed. At the moment I'll keep 10MB of the most recent. I don't want to keep too much because they're now included in a support dump.

• BIRT log files should be included in a support dump

  • The platform\workspace\.birt\logs directory content should be included in a support dump, if BIRT logging has been enabled then it should be included.

• JDBC Helper class should support sequences in SQL Server

  • The sequenceExists function currently only support Oracle and Postgres, apparently SQL Server also supports sequences so it should be added to the JDBCHelper class.

• Support editing features in SQL Server that use a sequence for key generation

  • It's possible in SQL Server to have a table where the key for a new row is generated from a sequence, but GeoTools does not currently recognise this, this update attempts to remedy that.

• Update YAJSW

  • The YAJSW library use to provide support for running Weave as a service/daemon should be updated to a newly available release.

• Remove final references to scripting on server

  • Originally the Weave server was able to implement operations written in JavaScript, but that functionality was removed. There are still a small number of places where that can be seen and they will be updated to remove the code.

• Display more key bindings in the Admin UI editors

  • At the moment only three shortcut keys are displayed in the editors, this will be expanded to display other useful shortcuts keys.

• Tidy up JSON support library

• JdbcHelper class should look for column with different case when adjusting column name

• Keycloak logging warning about insecure SAML request

  • Keycloack security is logging a message saying that authentication is occurring over an insecure connection when all communication should be secure.

• Client context is too limited in what can be expressed

  • When setting a context for a client it currently only supports a comma separated list of the name of the contexts that items should be included from, along with any item that are not assigned to a context, and this is not flexible enough.

• Include date/time in generated map image file name

  • The action weave.mapimageexport has been updated to change the default file name from map.png to map.png.

• Weave Map Engine help page needs a Namespace, Tags / Properties section like the other map engines help topics

  • The Weave Map Engine page needs a Namespace, Tags /Properties  section like the other map engines help topics (eg. Map Engine WMS, as shown in attached image).  .

• Add support for where clauses in related and table edits in non-spatial editing

  • It needs to be possible to add additional where clauses to non-spatial edits for related and table configs, so the rows available to the user can be filtered if required, for example to only show the rows the user should have access to.

• Add selection centroid function to REST geometry API

  • Add support for fetching the centroid from the server for the current selection.

• Improve support for Accept header when generating a map

  • The server should accept a wildcard image type when the client requests a map image and does not care what format it gets back.

• Fix typos in REST storage API Swagger documentation

  • The Swagger annotations for the REST storage API have a typo.

• Search panel selector combo does not autosize

  • The combo box in the search panel that is used to select which search to perform always has a fixed width, 250px by default but can be configured, but it should resize to fit the available space if the size has not explicitly been set in the config.

• GeoJSON output does not always include projection information

  • Even though the newest GeoJSON spec has removed the projection tag in the world of web clients and grid shifts it's still useful, unfortunately in some situations GeoJSON returned by Weave that is not in CRS:84 does not include the projection information.

• OSM map layer in client was causing a local variable to be a gloval variable

  • Because of a missing var keyword a variable defined when creating a OSM map layer in the client was created as a global variable, not a local one.

• Add client function API and implementation

  • To support creating and calling custom functions a new API must be added allowing plugins to define and implement code that can be called remotely.

• Editing redline geometry with a lot of vertices is too slow

  • If you create/import a redline geometry that has thousands of points then it can cause the browser to have problems trying to handle all the vertices when modifying the geometry, so now anything over 1000 vertices will only allow you to move/rotate the geometry and not modify individual vertices. Setting maxVertices to 0 or false for the Modify tool will disable this, setting it to a number will change the default from 1000.

• Only SLD files that define a StyledLayerDescriptor are recognised

  • Only SLD files that defined a style using THE StyledLayerDescriptor tag were recognised as SLD files but some SLD files don't include that tag so this update will ensure that more SLD files are recognised as such.

• Coordinate reference system lookup should check already uses projection first

  • When looking up the EPSG code for a projection all available projections are searched one by one until a match is found, this update will search the list of already used projections first.

• Add retry to ArcGIS REST spatial engine

  • A flaky ArcGIS REST service can cause issues if it has temporary timeout issues, so we have added a retry parameter to the config to tell Weave to retry the request a number of times, the default is 1, for a single retry.

• Added support for parsing Weave GeoJSON extensions

  • While the REST API parser has support for the Circle and Envelope GeoJSON extensions the general GeoJSON parser class does not, so this update will add it.

• Add additional logging to report generation

  • The steps being taken when performing BIRT related operations when generating a report and not logged to a level that can show where delays in report generation are occurring.

• Add support for javascript url's when opening a link

  • Adding support for javascript: url's, along side http:, https: and file:, when opening links in data definition provides additional opportunities to automate Weave functionality.

• Add new event for changing selected data in grid panel

  • Add support for firing a global event, active.data.change, that tells Weave to change the current data displayed in a data panel based on the data/data definition id passed with the event.

• Updated handing of paths when processing keycloak SAML requests

  • A number of places within the Keycloak code that were determining the path of incoming requests have been updated to use common code to ensure the paths are consistent.

• Add support for copying content to clipboard in Admin UI

  • It would be useful for some of the admin tools to be able to copy content to the clipboard so this update will add a right click context menu to some places to allow copying to the clipboard.

• Mime utility library is copied to two bundles

  • A mime utility bundle is used by both the Admin UI bundle and the client upload API bundle but at the moment is part of each bundle, the library should be moved out into its own bundle.

• Add more options to script tag in client

  • At the moment the script tag in the Weave 2 client config is limited to just providing the script source or a link to it, it does not support any of the additional attributes that a full html script tag supports, like async, defer, etc.

• Remove stop words from index search

  • Lucene, the technology behind the Weave index search, has a default set of stop words configured which are not really suitable for use with Weave so they will be removed. They can be added back, or a custom set provided, via Weave configuration.

• More detail is required for the log output in the Admin UI

  • There is additional information recorded in the weave log that is not available in the log viewer in the Admin UI so it should be updated to allow the user to access this additional information.

• Provide a way to clear matadata that's cached for a spatial engine

  • Add a reset option to the spatial engine Admin UI and osgi console spmd command to reset a spatial engine to force it to reload the metadata it has cached from the back end service.

• Support changing coordinate order when editing redline or spatial edit points via text

  • When you create geometry by entering the coordinates textually you're able to specify the ordering of the coordinates and if north is positive, but you can not change those settings if you try and update geometry, which seems like a pointless restriction.

• Implement new service tracking API

  • There a lots of places in the Weave code base where some functionality depends upon the availability of another service, and OSGi provides various methods to do that dependency handling, but for the simple case of a service depending upon one other service that's configured at runtime, e.g. something waiting for a database to become available before it can register it's own functionality, the OSGi coding can become cumbersome. This update is intended to encapsulate the existing OSGi dependency handling into a simple modern API that makes it easy to code the tracking of the availability of a service.

• Admin UI file explorer should allow uploading of more than one file at once

  • Currently you can only select a single file to upload when using the File Explorer tool in the Admin UI, this should be updated to allow more than one file to be selected and uploaded.

• Allow filtering of legend entries in map engine config

  • Add the ability to configure a map engine to tell it to always remove a layer when generating a legend.

• Add support for legend aliases to WMS map engine

  • The ArcGIS map engine has the ability to alter the labels used in a legend, via the aliases tag, this should also be added to the WMS map engine.

• ArcGIS SOAP map engine generating large log output

  • The ArcGIS SOAP map engine is logging the URL's it creates to generate images and in some cases those URL's can be thousands of characters long, making log files very large. This update will truncate the output of those messages.

• Admin UI Log tool not handling errors well

  • When the log messages are not available the client is not useful in helping to resolve the problem.

• Include JDBC drivers in installation

  • Update Weave to include a set of default JDBC drivers. Including Oracle, SQL Server, Postgres, MySQL, HSQLDB and SQLite.

• Handle multiple metrics registry providers better

  • If there are multiple registry providers, e.g. Datadog, Prometheus, InfluxDB or JAMon, installed only one, at random, will work. Only one provider should be installed at a time so now the Weave server will report the situation and shutdown the server.

• ToC model should map scale ranges from server information

  • When building the ToC model the scale ranges for the layers should be fetched from the server and use for the entry if they're available, unless they've been overwritten in the toc entry itself.

• Support multi-select field in cascade set in non-spatial edit

  • Update non-spatial editing to allow the last field in a cascade field set to allow multiple selections.

• Updated metrics to be able to report all available metrics

  • It would be handy to know what metrics are available so this update will enable collection and display of the currently registered metrics.

• Add support for flag to trust server certificate for SQL Server spatial engine

  • SQL Server has started complaining about server certificates, which requires the connection URL to include TrustServerCertificate=true so the SQL Server GeoTools driver is going to be updated to include that flag.

• Whole cell is clickable for URL parameters in grid panels

  • When a URL parameter is rendered in a grid panel the entire cell is clickable and will open the linked URL, rather than just the link being the clickable part.

• SQLite sourced data definition unable to use parameter type of 'url'

  • The SQLite JDBC driver does not support the JDBC \{fn ...} escape functionality which is used by Weave to generate the required content for a URL parameter, so you can't create a data definition that has a URL parameter with an SQLite database.

• No support for searching on date columns in SQLite

  • Since the SQLite JDBC driver does not support the JDBC date/time escape syntax, which is used when inserting dates into SQL statements to make them database agnostic, creating an attribute search that uses dates and times does not work with an SQLite database.

• Data definition timeout isn't accurate

  • Because the timeout used in a datasource data definition is applied per-query and the generation process can occur across multiple queries the timeout set for a data definition can be inaccurate.

• Redline toolbar window is resizeable

  • The redline toolbar window can be resized vertically but it provide no useful benefit and can be disabled.

• Disable mouse selection of items in a multiselect list

  • The mouse can be used to "select" the text in a multiselect list field, rather than selecting the items in the list, this update will disable the ability of the mouse to select the text.

• Enable disabling of zoom on refine and remove buttons in grid panel

  • Add the ability to set zoom='false' for the refine and remove button in the grid panel to stop the buttons from automatically zooming to the selection after they have been used.

• Add delete option to redline management tool

  • Update the redline management window to include a delete button.

• Validate XML files saved in the Admin UI File System tool

  • When editing XML files via the Admin UI Config tool the files are validated when they're saved, but this does not happen when you edit an XML file opened via the File System tool.

• Unable to set a spatial edit list parameter to null

  • Even if you set allowNull to true for a list field in a spatial edit parameter the list will not contain the option to set the value to null.

• Add test sub-command to memd osgi command

  • Having a test command that tries to generate a map image from a registered map engine is a useful addition to help resolve issues with map engines.

...

2.6.8.5

Released 2023-06-14

Enhancements

• Allow setting default roles for keycloak

  • It should be possible in keycloak.properties to set a defaultRoles property to a list of roles that a user should be given if the SAML server does not provide any roles.

• Allow removal of email domain for keycloak users

  • Rather than making people configure their SAML id provider correctly I'm providing an option, stripDomain, that when set to true in the keycloak.properties file will remove anything after the last @ in the username returned from SAML.

• Updated handing of paths when processing keycloak SAML requests

  • A number of places within the Keycloak code that were determining the path of incoming requests have been updated to use common code to ensure the paths are consistent.

...

Released 22 December 2022

Enhancements

• Enhanced HTTP request/response logging

  • To help with troubleshooting you can now set the system property weave.http.log to true to get very detailed log output for HTTP requests

• Improved support on Azure

  • Added support for custom Azure HTTP headers when using an Azure Reverse proxy in front of Weave

• Added timeout setting to DMS requests

  • It’s now possible to set a timeout for the document management system get and get all actions

• Updates to the quick search panel, com.cohga.view.quicksearch

  • The panel now has a clear button to reset the search text

  • You can set the emptyText value to show text in the input box before the user starts typing

• Quicker response to config file changes

  • Changes to xml configuration files trigger an update immediately

• Support toc model entry without an associated map entry

  • You can now create a toc model entry that just links to an entity and does not have any map related content, allowing for a combined ToC/Entity panel

• Added connection timeout for ArcGIS SOAP map engine

  • You can now set a connection timeout value for the ArcGIS SOAP map engines

• Reduced logging on long running processes

  • Some processes that take a while to perform were outputting a lot of log output which could obscure log out that was needed to troubleshoot

• Weave WMS server update

  • When using Weave as a WMS server it’s now possible for the client to specify an error message to be displayed by the server if an image can not be generated

• Improved index information output to console

  • The OSGi index related commands have been updated to improve the output they generate

• Additional content can be added to the About box

  • If the about button is included in a client it can now be configured to include additional information

• ToC panel updated to show selection size

  • If a toc entry is associated with an entity the ToC panel can display the size of the current selection for that entity to the right of the ToC panel. It can be disabled by setting showEntitySize to false for the panel.

• WhoAmI improvements

  • The /weave/whoami endpoint now displays more information and can be extended with verbose and pretty flags to provide even more info or format the output. e.g. /weave/whoami?verbose, /weave/whoami?pretty or /weave/whoami?verbose&pretty

• Admin UI File System tool

  • The file system browser now provides a right click menu and has re-arranged the buttons

• Add support for BLOB and CLOB columns

  • It’s now possible to expose BLOB and CLOB columns from a database table which can then be used in a data definition to display the content

• Scalebar switch of units

  • The scalebar will now switch between metres and kilometres when zooming in and out

• Config file include works with directories

  • You can now use the <?include?> directive in a config xml file to include a directory, not just a file. All .xml files in the directory and any sub-directories will be processed

• Non-spatial editing improvement

  • Determining the “key” of a newly created record is now a little smarter

• WMS capabilities display in Admin UI

  • A new button has been added to the Map Engines to to open the capabilities document for any WMS map engines

• Improved validation of spatial mappers

  • Spatial mapping configuration will now validate that only one spatial engine is set at the top level

• Layer filter change

  • Applying a layer filter now turns on the layer

• Attribute search update

  • Attribute searches now support a join tag, at the top level only, not for individual parameter/combinations

• Projection directory removed

  • The projections directory, in the workspace, has had its content moved into its own separate bundle

• WFS Updated

  • Improvements in the handling of non-default namespaces

• Index geometry update

  • Simple indexes work better with non-unique geometry

• Shutdown improvement

  • The speed for shutting down the server when it is still trying to connect to external services has been improved

• Added support for GML spatial engines on WIndows

  • The OGR driver on Windows did not support referencing GML based data

• Add support for Ext.js extension bundles

  • It’s now possible to create a bundle the adds support for Ext.js extensions, e.g. charting

• Support URL parameter type for spatial data definition

  • A spatial data definition can now include a URL type parameter

• Overriding log level with system properties

  • It’s now possible to set a log level via system properties, e.g. -Dweave.logger.debug=com.cohga.server.security.keycloak,org.keycloak will change the log level to DEBUG for the two Keycloak related loggers, -Dweave.logger.off=com.cohga.server.security.keycloak,org.keycloak will disable logging for the same two loggers

• Add support for callbacks on client and map load

  • A new client API was added allowing components to register to be notified when the client has loaded and/or when the map has been loaded. This means that a bunch of components no longer have to track that themselves

• Added ability to specify default connection timeout in client

  • There’s a new client API that allows code to change the default timeout for requests sent to the server

• DMS output format

  • There’s a new server API that allows a bundle to apply custom formatting to the default document management system document list page

• Spatial engine metadata improvements

  • The spmd conf command output has been tidied up

• Runtime properties can be set in config xml file

  • Runtime properties that are used by Weave bundles can be set via the <?set?> instruction in a config xml file, rather than needing to be set via system properties or Jetty .ini files. Note this is a work in progress and not all properties may work

• Improved handling of blank/null values when editing

  • Handling of blank and null values has been improved when submitting an edit

• Updated search config to be consistent with data definitions

  • It’s now possible (but the old format is still supported) to configure a search in a style similar to a data definition, that is having a generic <search:search> top level tag wrapping a specific search type, rather than having different top level search specific tags. This is similar to the way data definitions are configured.

• Support id filtering for searches

  • An id filter can be attached to a search to convert/translate the id’s returned from a search, similar to what can be done for a data definition. Particularly useful for searches in a different database than the spatially enabled table.

• Improved handling of CR/LF in lists (again)

  • Another attempt has been made to ensure that drop down lists that have labels that contains carriage returns or line feeds work correctly (why do people do this to me)

• Added support for “context”

  • You can now assign configuration items to a context and then tell a client to only use the configuration items from that context

• Removed requirement for “toc.” prefix on toc models

  • Previously a top level toc mode required its id to always start with “toc.”, this is no longer a requirement

• Snapping to redline layer

  • It’s now possible to specify the redline layer as a snapping target

• Support for search without any parameters

  • You can now have a search that does not have any parameters, this can be used for a search that operates the same all the time and does not require user input, for example, select all the properties that have a light pole on them

• GeoJSON encoding update

  • The encoding of geometry to GeoJSON by the client tries to ensure that features include the id’s that’s been assigned to them

• alwaysRefresh option added to client map engine config

  • You can set the alwaysRefresh option to true for a client map engine to ensure that it does not use a browser cached image, meaning each redraw of the layer will result in an updated image, useful for dynamic map content

• New BundlePath API

  • A new class for finding resources in a bundle has been added, specifically it improves support beyond the basic OSGi API of finding resources that are provided in fragment bundles

• Initial support for data parameters in layer filters

  • Layer filters can be defined with a date filter, this is a work in progress and map engine support could be spotty

• A new startup monitor is available

  • A new bundle that will record when the server shuts down and starts up has been added, and more importantly it records if the startup occurred after a clean shutdown

• Spatial engine and database metadata conf commands updates

  • The dbmd conf and spmd conf commands work better when provided with just a spatial engine or datasource, providing example output for the entire system, and tries harder to guess the correct values

• Parameters can use name or id

  • Previously different configuration objects that contain a list of parameters were not consistent with respect to the parameters using the name or id attribute to identify the individual parameters, now you can use either

• Keycloak library update

  • The internal Keycloak library, for interacting with SAML id providers, has been updated

• Admin UI functionality

  • Added additional filtering and refresh options to various Admin UI tools

• Revision control support in Weave updates

  • When running a Weave update on a Weave directory (or sub-directory) that is under the controls of Subversion or Git the changes made during the updated will be recorded with the revision control system ready to be committed. Note that the update won’t be applied if there are outstanding changes pending, you will need to commit, stash, undo, etc, the pending changes before you can apply the update, or you can pass a command line parameter to the update to force the update.

...

2.6.7

Released 17 March 2022

Enhancements

• 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

• 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

...

2.6.6

Release 13 July 2021

Enhancements

• 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

...

2.6.5

Released 15 March 2021

Enhancements

• 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

...

2.6.4.9

Released 11 Feb 2021

Enhancements

• New redline commands

  • The new bookmark commands added in 2.6.4.8 to help fix issues with pre-2.6.4.8 bookmarks have been replaced with the equivalent “redline” commands.

  • The newer version of the command works with all saved redlines, not just those saved as part of a bookmark as the bookmark version of the commands did.

2.6.4.8

Released 11 Feb 2021

Enhancements

• 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.

...

2.6.4

Released 30 July 2020

Enhancements

• 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

...

2.6.0

Released 8 November 2019

Enhancements

• Updated Java and Jetty, which requires a re-install, other than that this release has exactly the same functionality as 2.5.30